Update Rollup 8 for Microsoft Azure Site Recovery Provider

View products that this article applies to.

Introduction

This article describes the fixes that are included in Update Rollup 8 (version 5.1.1256) for Microsoft Azure Site Recovery Provider. Learn about the details of the fixes and the prerequisites that should be validated before you install this update.

↑ Back to the top

Summary

Update Rollup 8 for Microsoft Azure Site Recovery Provider applies to all systems that have Windows Azure Hyper-V Recovery Manager Provider version 5.1.1000 or an earlier version 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)

↑ Back to the top

Issues that are fixed in this update

After you apply this update, the following issues are fixed:

Test failover of a virtual machine that's protected by using Azure Site Recovery on to a Hyper-V 2012 R2 cluster fails, and you receive the following error message even though one or more of the cluster nodes has sufficient resources to start the virtual machine.
The virtual machine 'vmname' could not be started (Error Code: 25005)

Provider Error: The Windows Remote Management(WS-Management) Service cannot process the request. The object was not found on the server (server_name)
Possible causes : This might occur because of low resources on the secondary site.
Recommendation: Verify that the required amount of memory and storage is available on the secondary site.
A Create Protection Group operation fails, and you receive the following error message:

The operation was stopped. (Error code 535)
Possible Cause: The operation timed out. The VMM/Hyper-V/Configuration Server couldn't communicate with the vault, connection to the Hyper-V host was lost, a manual user action was pending for a long time or an action on Microsoft Azure has timed out.
Recommendation: Resolve the issue and retry the operation.
The Refresh Server details job fails, and you receive the following error message:
Cloud/Site information for VMM/Configuration server <server name> couldn't be refreshed. (Error code: 10013)
Provider Error: An internal error occurred in VMM/Hyper-V/Configuration server. Retry the last action. If the issue persists contact Support. (Provider error code: 0)
Possible Causes: Check that the VMM/Configuration Server and hosts are connected.
Recommendation: Resolve the issue and retry the operation.
Azure Site Recovery Agent goes into a "Disconnected" state when you failover your clustered VMM server to one of the passive nodes.

↑ Back to the top

Update information

To resolve these issues, the following file is available for download from the Microsoft Download Center:

Download the Update Rollup 8 package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

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 this update, you must have Microsoft Azure Hyper-V Recovery Manager Provider (version 3.5.468.0 or a later version), Azure Site Recovery (version 4.6.660 or a later version), or Azure Site Recovery (version 5.1.1000 or later) installed.

Note You can check the installed provider version in the Programs and Features item in Control Panel.

Restart information

You don't have to restart the computer after you apply this update. This update automatically stops the System Center Virtual Machine Manager services.

↑ Back to the top