Update Rollup 38 for Azure Site Recovery

Applies to: Site Recovery

Prerequisites


To install Microsoft Azure Site Recovery Provider Update Rollup 38 (version 5.1.4300.0), you must have one of the following installed:
  • Microsoft Azure Site Recovery Provider (version 5.1.4100 or a later version)  
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.22.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

  • Improved the "disable replication" experience. When customers disable replication after failing over VMs to the DR region and reprotecting them, the service no longer tries to delete the primary region VM continuously.
  • Introduced several improvements to monitoring in the areas of health error severity and identification.
  • Enhanced the validation logic in regards to Availability Sets and Application Gateway subnets to improve accuracy of Failover Readiness indicators.
     

Issues fixed

Azure to Azure

  • Fixed a bug related to initial replication failures.
  • Added prerequisites to check whether disk inputs (disk IDs, new disk addition after failover) are accurate.
  • Fixed a cross-subscription resource link cleanup issue.
     

Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

Improvements

  • (Not applicable)

Issues fixed

  • (Not applicable)
     

Mobility Service

Improvements

Azure to Azure and VMware to Azure

  • Support for WRITE_SAME IO types in the Linux driver.
  • VM Health alerts are added for a sudden rise in churn rate and slow replication because of bandwidth constraints (for Linux-based VMs).
     

VMware to Azure

  • Protection of large disks is now supported (up to 8 TB). This is applicable only when writing directly to managed disks.
     

Issues fixed

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

  • Reprotect improvement: Disks that customers start using after they disable protection are no longer pruned.
  • Failover improvement: A recovery point (RP) is now marked to prevent it from getting pruned after a workflow is submitted.

Issues fixed

  • If the Mobility agent installation generates error code EP0965, the job status is marked as "warning."
     

Microsoft Azure Site Recovery (portal)

Improvements 

  • General Purpose v2 storage accounts can now be chosen for cache storage or target storage. The earlier restriction to use only General Purpose v1 storage accounts is now lifted.
     

Issues fixed

  • (Not applicable)

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 MARS 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 Provider 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 Provider 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).

Known issues


There are no known issues in this update.

References


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