Update Rollup 41 for Azure Site Recovery

Applies to: Site Recovery

Prerequisites


To install Microsoft Azure Site Recovery Provider Update Rollup 41 (version 5.1.5000.0), you must have one of the following installed:

  • Microsoft Azure Site Recovery Provider (version 5.1.4500 or a later version) 
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.25.xxxx.x or a later version)
  • Microsoft Azure Recovery Services Agent (version 2.0.8700.0 or a later version)

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

Improvements made and issues fixed in this update


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

Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

Improvements

  • Configuration server OVF set up errors have been enhanced with clear root cause & recommended actions for easier resolution.
  • Process Server throughput calculation logic is enhanced to minimize alerts when manual intervention is not required.

Mobility Service

Improvements

  • Introduced new error code to provide root cause & resolution for MSI installation failure
  • Linux OS support improvements
    • Ubuntu 18.04
    • RHEL 7.7

Issues fixed

  • Disk information of Windows machines is made user readable in the Site Recovery logs that are being fed to Log Analytics workspace

Microsoft Azure Site Recovery (service)

Improvements

Azure to Azure

  • Customers now have the ability to configure test failover settings for replicated items from the Compute and Network blade. They can update Vnet, subnets, private IP addresses for test failover and also attach NSG configuration, Internal load balancer and Public IP address.
  • ASR now cleans up the created VM(s), NIC(s), and disk(s) in the DR region after customers fail back to the primary region and then disable replication.
  • Rationalized the creation of tags. Adjusted the information captured in tag key-value pairs to make it easy for customers to filter on the basis of tags.
  • The number of VMs supported in a recovery plan has been capped at 100 in order to ensure failover reliability.
VMware to Azure
  • The number of VMs supported in a recovery plan has been capped at 100 in order to ensure failover reliability.

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  MicrosoftAzure 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.16

9.18

Not mandatory

9.16

9.19

Not mandatory

9.16

9.20

Not mandatory

9.16

9.21

Mandatory

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