Introduction
This article describes the improvements and fixes that are included in Update Rollup 12 for the following components:
-
Microsoft Azure Site Recovery Provider (version 5.1.1600)
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version: 9.1.4139.1)
Learn the details of the improvements and the prerequisites that should be validated before you install this update.
Summary
Update Rollup 12 for Azure Site Recovery Provider applies to all systems that have the 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 Provider for Hyper-V (4.6.x.x)
-
Microsoft Azure Site Recovery Provider (5.1.x.x)
Update Rollup 12 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.
Improvements and fixes that are included in this update
Azure Site Recovery Provider
Issues that are fixed
-
Performance and Reliability fixes are included in Azure Site Recovery Provider for System Center Virtual Machine Manager to handle Virtual Machine migrations.
Azure Site Recovery Unified Setup
Improvements
-
OpenSSL is upgraded from 1.0.1p to 1.0.2g.
Issues that are fixed
-
Setup cannot download the MySQL Setup file. Additionally, you receive the following error message:
Incomplete MySQL Setup file downloaded with MD5SUM AC73541DEC5210161D35F23E16AAE41E
-
The database upgrade for Configuration Server fails, and you receive the following error message:
"Stopping WAS Service""WAS service stopped Successfully.""Database backup file is created successfully.""Unable to execute svsdb_upgrade.php.""Dropping the svsdb1 database and restoring the svsdb1 database with the backup."
Azure Site Recovery (service-side fixes)
-
Enabling Protection for VMware virtual machines (VMs) fails, and you receive the following error message:
An internal error occurred. ( Error code : 499)Possible Causes: The operation failed due to an internal error.Recommended Actions: Retry the last action. If the issue persists, contact Support.
-
Test failover fails, and you receive the following error message:
An Azure Resource Manager operation failed. (Error code : 28040)Possible Causes: Azure error message: 'Deletion of resource group 'resource_group_name' failed because some resources could not be deleted. The tracking Id is 'tracking_ID'. Please check audit logs for more details.'.Recommended Actions: Please resolve the error and try the operation again.The operation was stopped. (Error code : 548)Possible Causes: The operation was stopped because the retry limit was exceeded.Recommended Actions: Wait a while and retry the action.
-
The installation of the Master Target Server fails, and you receive the following error message:
CAQuietExec: C:\Windows\SysWOW64>exit /B 802 CAQuietExec: Error 0x80070322: Command line returned an error.CAQuietExec: Error 0x80070322: CAQuietExec FailedCustomAction Install_VSSProvider returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)MSI (s) (AC:3C) [00:26:17:553]: Note: 1: 2265 2: 3: -2147287035
-
Failback for a virtual machine fails, and you receive the following error message:
Virtual machines couldn't be prepared for failback. (Error code: 25052)Provider error: Failed to create virtual hard disk of VM (E14A3E37-C729-418C-815A-E0FD64D701C8). Exception Message - (Assertion Failure!)Microsoft Azure Site Recovery Service failed to connect to Hyper-V or host does not have enough space.Resolve the host issue and then try the operation again. (Provider error code: 31354)Possible causes: Check the Provider errors for more information.Recommendation: Resolve the issue, and retry the operation.
-
The IP Address of a VM is not deallocated after failback or when you disable protection. Additionally, you receive the following error message:
Could not update the 'IP_address' the replica IP address of the network adapter in the virtual machine 'VM_name'. (Error code: 28019)Possible causes: not available for IP address 'IP_address' subnet virtual network 'drnw' 'drnw-01'.Recommended action: try assigning a different IP address to the network adapter.Could not update the 'IP_address' the replica IP address of the network adapter in the virtual machine 'VM_name'. (Error code: 28019)Possible causes: not available for IP address 'IP_address' subnet virtual network 'drnw' 'drnw-02'.Recommended action: try assigning a different IP address to the network adapter."
-
Test Failover fails, and you receive the following error message:
The virtual machine isn't replicating. (Error code : 25017)Possible Causes: The virtual machine 'VM_name' is in a critical state, or requires resynchronization.Recommended Actions: Resynchronization the virtual machine to fix the state, and retry the operation.An Azure Resource Manager operation failed. (Error code : 28040)Possible Causes: Azure error message: 'The operation 'operation_name' failed: 'The server encountered an internal error. Please retry the request.'.'.Recommended Actions: Please resolve the error and try the operation again.The operation was stopped. (Error code : 548)Possible Causes: The operation was stopped because the retry limit was exceeded.Recommended Actions: Wait a while and retry the action."
-
The failback of VMs fails, and you receive the following error message:
Background disk merge failed to complete: The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk. (0xC03A000E)
-
Your virtual machine goes into the resync required status every time that you take a backup of the VM.
-
Your system slows down because VACP.exe is using all the memory on the server.
Update scenarios for 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 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 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
The following files are available for download from the Microsoft Download Center:
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 Update Rollup 12 for Microsoft Azure Site Recovery Provider (version 5.1.1600), 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 Provider (version 4.6.660 or a later version)
-
Microsoft Azure Site Recovery Provider (version 5.1.1000 or a later version)
To install Update Rollup 12 for Microsoft Azure Site Recovery Unified Setup (version 9.1.4139.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. This update automatically stops the System Center Virtual Machine Manager services.
Update replacement information
This update does not replace any previously released 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.
