Introduction
This article describes the issues that are fixed in Update Rollup 32 for the following versions of Microsoft Azure Site Recovery:
-
Microsoft Azure Site Recovery Provider (version 5.1.3800.0)
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version: 9.21.5091.1)
-
Microsoft Azure Recovery Services Agent (version 2.0.9144.0)
Note See the "Prerequisites" section before you apply this update.
Summary
Update Rollup 32 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.3400.0) and later versions
Update Rollup 32 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.17.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 made.
Microsoft Azure Site Recovery Provider
Issues fixed
Disaster recovery of Azure VMs
-
Fixes an issue in which a reprotect job fails occasionally while the primary VM is in a Failed/Deleting state.
-
Fixes an issue in which test failover cleanup fails if the test-managed disks are explicitly deleted by the user before the cleanup test failover is initiated.
-
Fixes an issue in which failover failures return a "No recovery point found" error for recovery plan failover scenarios if there's a time lag between virtual machine (VM) shutdown and failover initiation.
Microsoft Azure Site Recovery Unified Setup and Configuration Server Template
Improvements
Disaster recovery of VMware VMs/Physical servers to Azure
-
Health alert improvements for replicated items in cases of shutdown, deletion, and no heartbeat.
Mobility Service
Improvements
Disaster recovery of VMware VMs/Physical servers to Azure
-
Virtual machine on Windows that have boot drivers in the current control set can be protected through Azure Site Recovery. In earlier versions, this check was made across all control sets.
-
Linux OS support improvements:
o Support for RedHat Enterprise Linux 7.6
o Support for RedHat Workstation 6 and 7
o Support for Oracle Linux 6.10 and 7.6
o Support for new kernel versions for Ubuntu, Debian, and SUSE
-
Azure Site Recovery Linux drivers are copied onto the virtual machine during kernel upgrades. In earlier versions, a restart was required to copy the drivers.
-
Enhancements to mitigate a few WMI exceptions/corruption that were earlier observed.
Disaster recovery of Azure VMs
-
Support for Azure VMs that use a Storage Spaced Direct (S2D) configuration
-
Linux OS support improvements
o Support for RedHat Workstation 6 and 7
o Support for new kernel versions for Ubuntu, Debian, and SUSE
Issues fixed
-
Fixes a time-check issue when resynchronization is stuck.
Microsoft Azure Site Recovery (Service)
Improvements
Disaster recovery of VMware VMs/Physical servers to Azure
-
"Blob Storage" account type isn't available when you select Target Storage Account and Target Log Storage Account when you enable protection because this wasn't a supported configuration.
Issues fixed
Disaster recovery of VMware VMs/Physical servers to Azure
-
Fixes an issue that occurs during the completion of Initial Replication because of positive clock skew, even when recovery points are available.
Updating your Azure Site Recovery On-Premises components
-
Go to the Azure portal, and then browse for the Recovery Services vault.
-
In the Replicated Items pane, select your Recovery Services vault.
-
Select the "Click to install" notification at the top of the screen.
-
Select the VMs that you want to apply the update to, and then select OK.
Between two on-premises VMM sites
-
Download Update Rollup 32 for Microsoft Azure Site Recovery Provider.
-
Install this update first on the on-premises VMM server that's managing the recovery site.
-
After the recovery site is updated, install this update on the VMM server that is 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 on which the VMM service is installed.
Between an on-premises VMM site and Azure
-
Download Update Rollup 32 for Microsoft Azure Site Recovery Provider.
-
Install this update 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 on which the VMM service is installed.
Between an on-premises Hyper-V site and Azure
-
Download Update Rollup 32 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/physical site to Azure
-
-
-
Download Update Rollup 32 for Microsoft Azure Site Recovery Unified Setup.
-
Install this update first on your on-premises management server. This is the server that has the Configuration server and Process server roles.
-
If you have scale-out process servers, update them next.
-
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.
Update information
To resolve these issues, download and install the following files from the Microsoft Download Center:
For more information about how to download Microsoft support files, see the following Microsoft Knowledge Base article:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used 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 the file.
Prerequisites
To install Microsoft Azure Site Recovery Provider Update Rollup 32 (version 5.1.3800.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.3400 or a later version)
To install Microsoft Azure Site Recovery Unified Setup Update Rollup 32 (version 9.21.5091.1), you must have the following installed:
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.17.xxxx.x or a later version)
Note You can check the installed provider version in the Programs and Features item in Control Panel.
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. We make no warranty, implied or otherwise, about the performance or reliability of these products.
Microsoft provides third-party contact and website information to help you find technical support. This information may change without notice. We do not guarantee the accuracy of this third-party information.
