Introduction
This article describes the issues that are fixed in Update Rollup 37 in the following versions of Microsoft Azure Site Recovery:
-
Download Microsoft Azure Site Recovery Provider (version 5.1.4300.0)
-
Download Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.25.5241.1)
-
Download Microsoft Azure Recovery Services Agent (version 2.0.9163.0)
-
Download Microsoft Azure Site Recovery Configuration Server (version 5.1.4300.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 37 (version 5.1.4300.0), you must have one of the following installed:
-
Microsoft Azure Hyper-V Recovery Manager (version 3.4.486 or a later version)
-
Microsoft Azure Site Recovery Hyper-V Provider (version 4.6.660 or a later version)
-
Microsoft Azure Site Recovery Provider (version 5.1.3900 or a later version)
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.21.xxxx.x or a later version)
Note You can check the installed provider version in the Programs and Features item in Control Panel.
Issues that are 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
-
CPU performance improvements.
-
Auto update of certification expiry.
-
Enhanced monitoring support.
-
New failover validators Introduced for Availability Set and Subnet.
Issues fixed
-
Fixed an issue that is related to enabling replication for managed disk failure if the disk ID is invalid.
-
Fixed an extension installation issue.
-
Fixed an error that caused a workflows task to exceed the lock period.
-
Fixed an issue that is related to the cleanup of test failover resources.
-
Fixed an issue that is related to VM creation in the same subnet as an application gateway.
-
Updated the list of supported VM sizes for Accelerated Networking.
-
Fixed an issue that is related to the validity check for target subnets in relation to v1 VM protection.
-
Fixed an issue that is related to test failing over VMs from an availability set to an availability zone.
Microsoft Azure Site Recovery Unified Setup & Configuration Server Template
Improvements
-
Configuration server monitoring
-
Added a health alert for a passphrase change on the Configuration server.
-
Issues fixed
-
The state of a virtual machine (VM) is not cleared because of stale entries on a Configuration server.
-
VM protection is not restored after failover and IP retention does not occur after failback.
Mobility Service
Improvements
-
VM Health alerts are added for a sudden rise in churn rate and slow replication because of bandwidth constraints (Windows only).
-
Support for GPT partitions is extended from four (4) to five (5).
Microsoft Azure Site Recovery (service)
Issues fixed
-
If the Mobility agent installation generates error code EP0965, the job status is marked as "warning."
Microsoft Azure Site Recovery (portal)
Issues fixed
-
When you try to protect Azure VMs for disaster recovery, the "enable replication" step gets stuck at the "validating" operation.
Updating your Azure Site Recovery on-premises components
Between two on-premises VMM sites
-
Download the latest Update Rollup for Microsoft Azure Site Recovery Provider.
-
Install the Update Rollup first on the on-premises VMM server that's managing the recovery site.
-
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
-
Download the Update Rollup for Microsoft Azure Site Recovery Provider.
-
Install the Update Rollup on the on-premises VMM server.
-
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
-
Download the Update Rollup for Microsoft Azure Site Recovery Provider.
-
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
-
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.
-
If you have scale-out process servers, update them next by running Microsoft Azure Site Recovery Provider Unified Setup.
-
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.
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.
