Update rollup 51 for Azure Site Recovery

Applies to: Azure Site Recovery

Introduction


This article describes the issues that are fixedin Update Rollup 51 in the following versions of Microsoft Azure Site Recovery:

Learn about the details of the issues that arefixed and the prerequisites that should be verified before you installthis update.


Prerequisites


Toinstall Microsoft Azure Site Recovery Provider Update Rollup 51, you must haveone of the following installed:

  • Microsoft Azure Site Recovery Provider (version 5.1.6000 or a later version) 
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.34.xxxx.x or a later version)
  • Microsoft Azure Recovery Services Agent (version 2.0.8900.0 or a later version)

Note: Youcan check the installed provider version in the Programs and Features item inControl Panel.


Improvements made and issues fixed in this update


After you install thisupdate, the following issues are fixed, and the following improvements areincluded.

Mobility Service

Linux OS Support

  • Azure to Azure
    • SUSE 15 SP2
    • RHEL 7.9
    • Cent OS 7.9
  • VMware/Physical to Azure
    • SUSE 15 SP2
    • RHEL 7.9
    • Cent OS 7.9
Please note that the support for general availability versions of RHEL 7.9 and Cent OS 7.9 has been added.

Issues fixed

  • Added a fix where health events were not showing up correctly on the portal.
  • Fixed an issue where enable replication was failing due to timeout.
  • Fixed an issue where the setup for scale out process server installation was failing when being installed with private endpoints.
  • Added a fix where consistency tags were failing for Windows multi-VM consistency scenario for Azure machines replicating to Azure.
  • Improved error notification for various time out issues.
  • Added appropriate error handling where enable replication was failing due to a file being corrupt.


Microsoft Azure Site Recovery Unified Setup& Configuration Server Template

No new changes have been introduced.


Microsoft Azure Site Recovery (service) 

No new changes have been introduced.

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 Ifthe VMM is a Highly Available VMM (Clustered VMM), make sure that you installthe 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 aHighly Available VMM (Clustered VMM), make sure that you install the upgrade onall 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 Ifyour Hyper-V is a Host Clustered Hyper-V server, make sure that you install theupgrade 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: If you are updating orprotecting SUSELinux Enterprise Server 11 SP3, RHEL5, CentOS 5, and DEBIAN7 machines, thenmake sure to follow the below steps -

  1. Downloadthe appropriate installer for your machines –
  2. Copy the installer to INSTALL_DIR\home\svsystems\pushinstallsvc\repositoryfolders on Configuration Server and Scale Out Process Servers, before upgradingor protecting your Virtual Machines. For example, below will be the folder namewhen Configuration Server/Process Servers install path is C:\Program Files(x86)\Microsoft Azure Site Recovery
    • C:\ProgramFiles (x86)\Microsoft Azure Site Recovery\home\svsystems\pushinstallsvc\repository
  3. After copying theinstaller, go to services.msc and restart the InMage PushInstallservice.

 

Note: A restart is recommended after every upgrade of the Mobilityagent to make sure that all latest changes are loaded on the source computer.This is not necessarily mandatory. However, a restart ismandatory if the difference between agent versions from the last restartand the target version is greater than four (4) in the last decimal place. Seethe 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)