Update rollup 52 for Azure Site Recovery

Introduction

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

• Azure to Azure

• • Mobility service (version 9.39.5796.1)

• VMware/Physical to Azure

• • Download Microsoft Azure Site Recovery Configuration Server OVF template (version 5.1.6458.0)

  • • MD5 hash 22865b7362b34f300b92c5e803def5fc

  • Download Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.39.5796.1)
    
    Prerequisite to update or protect SUSE Linux Enterprise Server 11 SP3, RHEL5, CentOS 5 and DEBIAN7 machines: Ensure latest mobility agent installer is downloaded from Microsoft Download Center and placed in push installer repository on configuration server. Refer to Updating your Azure Site Recovery On-Premises components section below, for more information.

  • Mobility service (version 9.39.5796.1)

• HyperV or VMM to Azure

• • Download Microsoft Azure Recovery Services Agent (version 2.0.9196.0)

  • Download Microsoft Azure Site Recovery Provider (version 5.1.6458.0)

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

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 52, you must have one 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.35.xxxx.x or a later version)

• Microsoft Azure Recovery Services Agent (version 2.0.8900.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.

Mobility Service

Linux OS Support

• Azure to Azure

• • RHEL 8.3

  • Oracle Linux 7.9

• VMware/Physical to Azure

• • RHEL 8.3

  • Oracle Linux 7.9

  • Oracle Linux 8.3

Issues fixed

• Added logging enhancements to the Process Server used for protecting VMware and Physical machines.

• Improved error notification for installer time out issue, appearing during enable replication, due to timeout in initrd creation.

• Improved error notification where enable replication was failing due to corrupt RPM database.

• Fixed an issue where if certificate renewal for Configuration Server was triggered from the portal, then Process Server’s certificate were not getting renewed.

Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

No new changes have been introduced.

Microsoft Azure Site Recovery (service)

• Fixed an issue where test failover for a protected Azure VM was failing with the error notifying subnet not available.

• Added a fix where updating recovery plans through PowerShell was breaking the configured pre- and post-actions.

• Fixed an issue where old cloud selection was not getting deleted, resulting in failure of enable replication.

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: If you are updating or protecting SUSE Linux Enterprise Server 11 SP3, RHEL5, CentOS 5, and DEBIAN7 machines, then make sure to follow the below steps -

1. Download the appropriate installer for your machines –

2. • SUSE Linux Enterprise Server 11 SP3

   • RHEL5

   • DEBIAN7

   • CentOS 5

3. Copy the installer to INSTALL_DIR\home\svsystems\pushinstallsvc\repository folders on Configuration Server and Scale Out Process Servers, before upgrading or protecting your Virtual Machines. For example, below will be the folder name when Configuration Server/Process Servers install path is C:\Program Files (x86)\Microsoft Azure Site Recovery –

4. • C:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\pushinstallsvc\repository

5. After copying the installer, go to services.msc and restart the InMage PushInstall service.

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.