Update rollup 45 for Azure Site Recovery

Introduction

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

• Azure to Azure

• • Mobility service (version 9.32.5487.1)

• VMware/Physical to Azure

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

  • Download Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version  9.32.5487.1)

  • Mobility service (version 9.32.5487.1)
    

• HyperV or VMM to Azure

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

  • Download Microsoft Azure Site Recovery Provider (version 5.1.5400.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 45, you must have one of the following installed:

• Microsoft Azure Site Recovery Provider (version 5.1.5000 or a later version)

• Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.28.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.

Mobility Service

Linux OS support

• Azure to Azure

• • SLES 15
    

• VMware/Physical to Azure

• • RHEL 8.1
    

  • Ubuntu 18.04.3 (Kernel v5.3)

  • SLES 15

Issues fixed

• Fixed failures seen in some cases while installing ASR VSS provider caused by WMI path

• Enhanced prerequisite checks to avoid failures during agent upgrade and installation

• Fixed the time out and high CPU utilization issues seen in some cases during enable replication

Microsoft Azure Site Recovery (service)

No new updates are rolled out in this release. Please refer to https://support.microsoft.com/en-us/help/4538187 for details on the last release that contains service updates.

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.