Introduction
This article describes the issues that are fixed in Update Rollup 25 for the following versions of Microsoft Azure Site Recovery:
-
Microsoft Azure Site Recovery Provider (version 5.1.3300.0)
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version: 9.16.4860.1)
-
Microsoft Azure Recovery Services Agent (version 2.0.9121.0)
Learn about the details of the issues that are fixed and the prerequisites that should be validated before you install this update.
Summary
Update Rollup 25 for Microsoft Azure Site Recovery Provider applies to all systems that have Microsoft Azure Site Recovery Service Provider installed. These include the following:
-
Microsoft Azure Site Recovery Provider for System Center Virtual Machine Manager (3.3.x.x)
-
Microsoft Azure Site Recovery Hyper-V Provider (4.6.x.x)
-
Microsoft Azure Site Recovery Provider (5.1.2900.0)
Update Rollup 25 for Microsoft Azure Site Recovery Unified Setup (VMware to Azure) applies to all systems that have Microsoft Azure Site Recovery Services Unified Setup version 9.16.4860.1 or a later version installed.
Issues that are fixed in this update
After you apply this update, the following issues are fixed, and the following improvements are included.
Microsoft Azure Site Recovery Unified Setup & Configuration Server Template
Improvements
-
You can now protect and failback VMware VMs on Virtual Volumes (VVols) datastore.
-
You can now protect and failback VMware VMs on NFS datastore.
-
You can now protect and failback VMware VMs under vApp.
Issues fixed
-
If Disk.Enable UUID is not set for the source VM or if the source VM has RDM physical disk, then while performing original location recovery, Azure Site Recovery creates a new disk instead of reusing the original disk that is attached to the source VM. After this update (Enable replication should be with the agent version 9.16), it will reuse the existing disk.
-
An internal error occurs during failback when virtual machine port group switch is not available on the ESXi host where MT is present.
Mobility Service
Improvements
-
Changes to Windows mobility service event log collection to not collect event parameters other than well-known parameters types such as Machine Name, Disk ID, and so on.
Microsoft Azure Recovery Service Agent
Issues fixed
-
Recovery to an alternate location was not supported for Hyper VMs that are located on a host running Windows Server 2016 if they were protected with Microsoft Azure Recovery Services agent versions before version 2.0.9077.0. That issue is fixed in this rollup. You can now install the latest version and recover to an alternate location. This fix applies to the following scenarios:
-
Between an on-premises VMM site and Azure
-
Between an on-premises Hyper-V site and Azure
-
Microsoft Azure Site Recovery (Service)
Improvements
Automatic update of Mobility Service extension in Azure-to-Azure replication. To avoid the overhead that is associated with manually upgrading Site Recovery components, choose to allow Site Recovery to manage updates of the components. This feature is only applicable for replication of Azure VMs that currently use Azure Site Recovery.
Microsoft Azure Site Recovery (Portal)
Improvements
Adds a new management setting for automatic update of Site Recovery components. You can choose to allow Site Recovery to manage updates in the following ways:
-
As part of the enable replication step
-
By toggling the extension update settings inside the vault
Updating your Azure Site Recovery On-Premises components
|
Scenario |
Steps |
|
Between Azure regions |
|
|
Between two on-premises VMM sites |
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 |
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 |
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/physical site and Azure |
|
Update information
To resolve these issues, download and install the following files from the Microsoft Download Center:
Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.
Prerequisites
To install Microsoft Azure Site Recovery Provider Update Rollup 25 (version 5.1.3300.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.1000 or a later version)
To install Microsoft Azure Site Recovery Unified Setup Update Rollup 25 (version 9.16.xxxx), you must have the following installed:
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.12.xxxx.x or a later version)
Note You can check the installed provider version in the Programs and Features item in Control Panel.
Restart information
You do not have to restart the computer after you apply this update on computer that has a System Center Virtual Machine Manager or a Hyper-V server.
This update automatically stops and then restarts the System Center Virtual Machine Manager services during the update process.
A restart will be required on your Configuration server and protected servers after you apply this update.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
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.
