Introduction
This article describes the issues that are fixed in Update Rollup 26 for the following versions of Microsoft Azure Site Recovery:
-
Microsoft Azure Site Recovery Provider (version 5.1.3400.0)
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version: 9.17.4897.1.)
-
Microsoft Azure Recovery Services Agent (version 2.0.9122.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 26 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.3000.0)
Update Rollup 26 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.13.0000.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 and Configuration Server Template
Improvements
-
For VMware to Azure scenarios, the "Initial replication" time is reduced by using improved compression technology.
Mobility Service
Improvements
-
Disaster Recovery for Azure virtual machines (between Azure regions): Support for Azure virtual computers that are running SUSE Linux Enterprise Server 12.
Issues fixed
-
Virtual machines sometimes move into "resynchronization" mode after a restart if too many disk writes occurred during the shutdown process.
Microsoft Azure Site Recovery (Service)
Issues fixed
-
Retaining the network interface name on failover of IaaS VMs. In this fix, network interfaces that are created on a target region retain the same name as the source network interface. This fix also removes ASR-created long names, and resolves issues that occur because of long file names when network interfaces are attached to Standard LB back-end pools.
-
When you enable auto-update in replicating Azure virtual machines, the automation account creation fails when there is another vault that has similar first nine characters in the same subscription. The logic of choosing the default name for the automation account is fixed to resolve this issue.
-
If the setting to create managed disks on failover to Azure is specified for failover from on-premises to Azure, blobs that contains the replicated data are not cleaned up after failover as part of disable protection. This is fixed and the blobs are cleaned up after disable protection.
Updating your Azure Site Recovery On-Premises components
|
Scenario |
Steps |
|
Between Azure regions |
|
|
Between two on-premises VMM sites -or- Between two on-premises VMM sites that use SAN array replication |
Note If the VMM is a Highly Available VMM (Clustered VMM), make sure that you install the upgrade on all nodes of the cluster in which 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 in which 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 or physical site and Azure |
|
Update information
To resolve these issues, download and install the following files from the Microsoft Download Center:
-
Download Update Rollup 26 for Microsoft Azure Site Recovery Provider
-
Download Update Rollup 26 for Microsoft Azure Site Recovery Configuration Server OVF
-
Download Update Rollup 26 for Microsoft Azure Site Recovery Unified Setup
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, 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 26 (version 5.1.3400.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.3000 or a later version)
To install Microsoft Azure Site Recovery Unified Setup Update Rollup 26 (version 9.17.xxxx), you must have the following installed:
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.13.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.
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.
