Update Rollup 39 for Azure Site Recovery

Introduction

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

• Download Microsoft Azure Site Recovery Provider (version 5.1.4600.0)

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

• Download Microsoft Azure Recovery Services Agent (version 2.0.9165.0)

• Download Microsoft Azure Site Recovery Configuration Server (version 5.1.4600.0)

• Download Mobility Service for Windows (version 9.27.5308.1)

• Download Mobility Service for CentOS (version 9.27.5308.1)

• Download Mobility Service for Ubuntu (version 9.27.5308.1)

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 39 (version 5.1.4600.0), you must have one of the following installed:

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

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

Improvements

Azure to Azure

• Enabled support for the latest release of Azure Disk Encryption support (Managed Disk, Windows)

• Support for attaching networking resources (updating NSG, LB, and Public IP) to failover VMs in Azure

Issues fixed

• Enable replication workflow was failing in the 'Create Target Resources' step if an existing target availability set in the format <srouceAVSet>-asr was selected. This has now been fixed.

• Fixed a bug related to migration from unmanaged to managed disks.

• Improved failure handling of VSS writers
  
  
  

VMware to Azure

Improvements

NA

Issues fixed

NA

Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

Improvements

NA

Issues fixed

NA

Process Server Monitoring

Improvements

Warning and Critical alerts have been added based on the throughput achieved by the Process Server. The throughput is measured in terms of the speed of data upload to Azure against the upload pending at the Process Server.

Mobility Service

Improvements

Azure to Azure and VMware to Azure

• You can now protect disks up to 8 TB using Site Recovery

• Support for 20MBps data change rate (data churn) for P20/P30/P40 disks

VMware to Azure

• Enhancements in recommendation when there is a high data churn health event for protected VM.

Issues fixed

Azure to Azure

• Fixed a bug where there was an issue in protecting disks of size between 1 GB and 1.5 GB
  

VMware to Azure

• Optimized installation and upgrading of mobility agent on servers that are running SQL Server.

• Enhancements are made to use only TLS 1.2. Any other lower version connections will be rejected.

• Certificates generated during fresh installations will have 2,048 bit-length Diffie-Hellman key.

Microsoft Azure Site Recovery (service)

Improvements

Hyper-V to Azure

• Improvement in failback performance when express route is used, and reduced throttling errors.

• Failover process enhancements which reduces time of failover and increases reliability.

• Replication performance enhancements while handling large differential log files which will avoid resync issues for VMs.

Issues fixed

• Previously there was an issue where few snapshots used for recovery point generation weren't deleted. This has been fixed.

Microsoft Azure Site Recovery (portal)

Improvements 

NA

Issues fixed

NA

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 Agenton 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 downloadingMicrosoft 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.

More information

Known issues

There are no known issues in this update.

References

Learn about the terminology that Microsoft uses to describe software updates. 

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.