Introduction
This article describes the issues that are fixed in Update Rollup 17 for the following versions of Microsoft Azure Site Recovery:
-
Microsoft Azure Site Recovery Provider (version 5.1.2250.0)
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version: 9.8.4455.1)
Learn the details about the issues that are fixed and the prerequisites that should be validated before you install this update.
Summary
Update Rollup 17 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.x.x)
Update Rollup 17 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.0.4016.1 or a later version installed.
Fixes and improvements that are included in this update
After you apply this update, the following issues are fixed, and the following improvements are included.
Microsoft Azure Site Recovery Provider
Improvements
-
Improved error messages for protection failures to help in troubleshooting.
Issues that are fixed
-
Not applicable
Microsoft Azure Site Recovery Unified Setup
Improvements
-
Improved prerequisites for operating system locale detection, IIS configurations, and incompatible Group Policy objects.
Issues that are fixed
-
Now handles cases for protection of virtual machines that have USB devices connected to them. Now ASR will filter out USB devices instead of failing the protection of a virtual machine.
Mobility Service
Improvements
-
Support for SUSE Linux Enterprise Server 11 Service Pack 4 is included.
-
Reliability improvements for protection of virtual machines that have multiple network adapters. Agent now intelligently selects the supported IP ranges while filtering out the unsupported one like APIPA address (169.254.0.0 to 169.254.255.255). This increases the success rate of protection of virtual machines having multiple network adapters configuration also removing the dependency of manually disabling the network adapters having unsupported address notation.
-
Improvements in Mobility service diagnostics collection to improve measurement of key performance metrics and serviceability.
Issues that are fixed
-
Fixes Linux scenarios where a modified IP address was incorrectly reported by mobility service. After discovery occurs, in some cases a modified IP address is not sent to the service and instead a stale entry is picked from the cache. This causes protection failures.
-
Fixes an issue for Red Hat Enterprise Linux Server 7.2 running the 3.10.0-514 kernel, where the Mobility Service filter driver does not load. This causes replication to stall. If you run Red Hat Enterprise Server 7.2 with the 3.10.0.514 kernel, you will have to disable protection for the system, and enable protection by upgrading to the Mobility Service version that is part of this update rollup.
-
Installation of the Mobility Service fails. Additionally, you receive the following error message:
MSI (s) (10:50) [time]: Executing op: ActionStart(Name=Invoke_DataPoolSize,,)CAQuietExec: C:\Program Files (x86)\Microsoft Azure Site Recovery\agent>exit /B 0MSI (s) (10:50) [time]: Executing op: CustomActionSchedule(Action=Invoke_DataPoolSize,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\GetDataPoolSize\DataPoolSize.bat" "C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\GetDataPoolSize")MSI (s) (10:88) [time]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB628.tmp, Entrypoint: CAQuietExecCAQuietExec: Error 0x80070003: Command line returned an error.CAQuietExec: Error 0x80070003: CAQuietExec Failed
-
The Mobility Service installation fails if the %ProgramData% folder is not located on your system drive.
-
The Mobility Service upgrade fails and you receive the following error message:
time: Either Installation directory/Agent Role/CSIP/CSPort/GUID vaule is null/invalid. Can't proceed ahead with upgrade.time: registration with Configuration Server has failed.time: Removing InMage Agent registry hive.time: Unable to remove Agent registry hive.time: Exception Occured: System.ArgumentException: Cannot delete a subkey tree because the subkey does not exist. at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(String subkey) at UnifiedAgent.UAInstallActionProcessess.DeleteAgentRegistry()time: installation has failed.time: File C:\Temp\ASRSetup\Passphrase.txt doesn't exist.time: File C:\Temp\ASRSetup\Passphrase.txt doesn't exist.time: Application Endedtime: Exit code returned by unified agent: 0(Successful)
Microsoft Azure Site Recovery (service side fixes)
Improvements
-
Support for availability set for resource manager deployment. Users can now assign availability sets in virtual machine properties before failover. This functionality is a must for protection of all the on-premise applications that use network load balancer.
-
Enable DR can now be retried for VMware scenario. If protection fails, you can now restart the job instead of disabling or enabling protection.
-
Ads a check in the portal that occurs if a user chooses to fail over to an app-consistent recovery point. In this situation, there's now verification that at least one such point exists for the virtual machine.
-
Improved checks for availability of a virtual machine size in a subscription when you change virtual machine settings and when performing a failover.
-
For Hyper-V virtual machines when a planned failover occurs or when the shutdown option is chosen after a failover occurs, source virtual machines will be shut down by force even if they are locked.
-
An unplanned failover is renamed to failover.
Issues that are fixed
-
Adds a check in VM properties that if test failover is in progress, editable VM properties are disabled to avoid any failures caused by an unwanted change.
-
Updates Mobility Service workflow previously failed for a failed-over virtual machine. This behavior has been fixed to make sure the following behaviors occur.
Virtual Machine State
Update Mobility Service Workflow behavior
Protected (On-prem to Azure)
Workflow updates the Mobility Service that is running on the on-premises VM
Failed over into Azure
The portal will block update mobility service for such VMs until they are re-protected
Protected (Azure to On-premises)
Workflow updates the Mobility Service that is running on the VM running in Azure
Failback to On-premises
The portal will block update mobility service for such VMs until they are re-protected
Updating your Azure Site Recovery on-premises components
|
Scenario |
Steps |
|
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 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 to Azure |
|
Update information
To resolve these issues, download and install the following files from the Microsoft Download Center:
Download Update Rollup 17 for Microsoft Azure Site Recovery Provider
Download Update Rollup 17 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. 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 17 (version 5.1.2250.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 17 (version 9.8.4455.1), you must have the following installed:
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.0.4016.1 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.
Known issues
When the test VM is deleted from ASR or VMM after successful verification of test failover for Hyper-V replication, other replicated data and files (which are not related to the VM under test) are also deleted. This causes a critical state indication for the other replicated VMs. This affects only customers on Update Rollup 2.1 for System Center Virtual Machine Manager 2016 and Update Rollup 12 for System Center Virtual Machine Manager 2012 R2.
Note This issue could require the customer to re-perform the initial replication for protected VMs. There is no workaround for this issue.
To resolve this issue, we strongly recommend that you download the following hotfix and update to the latest version.
-
Download and install this hotfix for deployments that run Update Rollup 2.1 for System Center 2016 Virtual Machine Manager
-
Download and install this hotfix for deployments that run Update Rollup 12 for System Center 2012 R2 Virtual Machine Manager
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.
