Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Update rollup 46 for Azure Site Recovery

Update rollup 46 for Azure Site Recovery

View products that this article applies to.

Introduction

Learn about the details of the issues that are fixed and the prerequisites that should be verified before you install this update.

↑ Back to the top

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 46, you must have one of the following installed:

  • Microsoft Azure Site Recovery Provider (version 5.1.5500 or a later version) 
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.29.xxxx.x or a later version)
  • Microsoft Azure Recovery Services Agent (version 2.0.8800.0 or a later version)

Note: You can check the installed provider version in the Programs and Features item in Control Panel.


↑ Back to the top

Improvements made and issues fixed in this update

After you install this update, the following issues are fixed, and the following improvements are included.

Mobility Service

Linux OS support

  • Azure to Azure
    • RHEL 7.8
    • CentOS 7.8
  • VMware/Physical to Azure
    • RHEL 7.8
    • CentOS 7.8
Issues fixed
  • Added pre-requisite check to ensure VM_PLATFORM value is not missing from drscout.conf file. This will ensure proper error details are shown on failure and avoid issues with mobility agent upgrade for Linux machines at a later point
  • Added a fix to ensure no ASR related writable files are available in the system
  • Removed generation of a certification not used during Azure VM protection to avoid failures from timed-out 
  • Added missing library function to fix issues faced during uninstallation of mobility agent on OEL 6.9 version.
  • Added new health alert if ASR VSS provider fails to register with the VSS.
  • Fixed the logging of various events to improve diagnosis

Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

You can now use Site Recovery to protect VMs managed through vCenter 7.0 


Microsoft Azure Site Recovery (service)

Improvements
  • Site Recovery usage will now reflect in Azure billing within four hours of service consumption
Azure to Azure
  • ASR now supports protection of Azure VMs running in Proximity Placement Groups to another region. Learn more
  • Failover of Azure VMs between 2 zones within a given region (Zone to zone DR) is supported through ASR now. This functionality has been rolled out in Southeast Asia and UK South. Learn more
  • Customization of names of NICs created in target region, via REST API is supported now
HyperV to Azure
  • Alternate Location Recovery for Windows Server 2019 is supported now during failback operations
Issues fixed
  • Fixed a bug related to the name of the availability set created by ASR during test failover.

↑ Back to the top

Updating your Azure Site Recovery On-Premises components

Between two on-premises VMM sites

  1. Download the latest Update Rollup for Microsoft Azure Site Recovery Provider
  2. Install the Update Rollup first on the on-premises VMM server that's managing the recovery site.
  3. After the recovery site is updated, install the Update Rollup on the VMM server that's managing the primary site.

Note If the VMM is a Highly Available VMM (Clustered VMM), make sure that you install the upgrade on all nodes of the cluster where the VMM service is installed.

Between an on-premises VMM site and Azure

  1. Download the Update Rollup for Microsoft Azure Site Recovery Provider.
  2. Install the Update Rollup on the on-premises VMM server.
  3. Install the latest Microsoft Azure Recovery Services Agent on all Hyper-V hosts.

Note If your VMM is a Highly Available VMM (Clustered VMM), make sure that you install the upgrade on all nodes of the cluster where the VMM service is installed.

Between an on-premises Hyper-V site and Azure

  1. Download the Update Rollup for Microsoft Azure Site Recovery Provider.
  2. Install the provider on each node of the Hyper-V servers that you have registered in Azure Site Recovery.

Note If your Hyper-V is a Host Clustered Hyper-V server, make sure that you install the upgrade on all nodes of the cluster.

Between an on-premises VMware or physical site to Azure

  1. Update your on-premises management server by downloading Microsoft Azure Site Recovery Unified Setup. This is the server that has the Configuration server and Process server roles.
  2. If you have scale-out process servers, update them next by running Microsoft Azure Site Recovery Unified Setup.
  3. Go to the Azure portal, and then go to the Protected Items > Replicated Items page. Select a VM on this page. Select the Update Agent button that appears at the bottom of the page for each VM. This updates the Mobility Service Agent on all protected VMs.

Note A restart is recommended after every upgrade of the Mobility agent to make sure that all latest changes are loaded on the source computer. This is not necessarily mandatory. However, a restart is mandatory if the difference between agent versions from the last restart and the target version is greater than four (4) in the last decimal place. See the following table for a detailed explanation.

Agent version during last restart

Upgrading to

Is a restart mandatory?

9.25

9.27

Not mandatory

9.25

9.28

Not mandatory

9.25

9.29

Not mandatory

9.25

9.30

Mandatory

First upgrade to version 9.29, and then restart before you upgrade to version 9.30 (because the difference between the last restart version and the target version is greater than 4)


↑ Back to the top

Keywords: CI119051, kbHotfixAuto

↑ Back to the top

Article Info
Article ID : 4564347
Revision : 11
Created on : 6/10/2020
Published on : 6/10/2020
Exists online : False
Views : 161