Update Rollup 40 for Azure Site Recovery

Applies to: Site Recovery

Prerequisites


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

  • Re-protect experience enhancements: For better BCDR management, we now clean up machines in the DR region after failback is complete and when the VMs are re-protected. There is no need to manually delete VMs and NICs.
  • Test Failover static IP settings: Earlier, when customers performed test failover on to actual DR network, we did not use the original IP. This was to ensure that the IP is available for an actual DR. However, customers want to retrieve same IP address during DR drill to validate networking settings. We have addressed this concern and allow customers to pick static IPs during test failover.
  • Validators for improving failover readiness: Validators are added to ensure customers are ready for a failover. Necessary actions along with the issue will be provided in case a failure is suspected.

Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

Improvements

  • Error messages during deployment of configuration server through OVF are enhanced to provide accurate root cause and recommended steps to resolve the issue.


Mobility Service

Improvements

  • New health alerts are added for below scenarios which impacts application consistent recovery points creation
    • When application VSS writers fail on source machine
    • When VSS Provider is disabled or not installed on source machine
  • Existing health alerts are enriched with contextual information for better analysis
    • Disk details, churn rate observed and the amount of data pending per disk are added for 'Sudden high churn rate alert'
    • Disk details and the amount of data pending per disk are added for 'High latency alert'

Issues fixed

  • Servers on Windows 2019 with UEFI secure boot enabled will be blocked during enable replication. This will avoid boot issues after failover as Azure doesn't support UEFI secure boot configuration
  • MSI execution failures were observed during mobility agent installation when multiple products are installed on a server. Alternative approach is designed to handle this issue.

Microsoft Azure Site Recovery (service)

Improvements

  • You can use ACLed storage accounts for protection of Hyper-V servers to Azure 
  • Enhancements are made to the logic used for selecting the best suitable VM SKU during failover. Few corner cases where high configuration SKUs were chosen are now handled.

Issues fixed

  • Stale or unexpected entries in 'device.map' file are handled to avoid failover failures inLinux servers

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

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

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.