Update Rollup 11 for Azure Site Recovery

Introduction
This article describes the fixes that are included in Update Rollup 11 for the following:
  • Microsoft Azure Site Recovery Provider (version 5.1.1500)
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.0.4083.1)

Learn about the details of the fixes and the prerequisites that should be validated before you install this update.
Summary
Update Rollup 11 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 Provider for Hyper-V (4.6.x.x)
  • Microsoft Azure Site Recovery Provider (5.1.x.x)

Update Rollup 11 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 installed.

Issues that are fixed or new features that are added in this update
After you apply this update, the following issues are fixed or new features are added:

Microsoft Azure Site Recovery Provider

New features
  • Prerequisite checks have been added before the installation of the DRA server.

Issues fixed

  • An intermittent error in writing proxy details occurs when the SCVMM Service is started. This issue occurs when registration is invoked from the command line.

  • DRA registration fails when it's run from the command line.

Microsoft Azure Site Recovery Unified Setup

  • In a proxy environment, the unified setup installation fails at the "Install configuration server and process server" step because it can't download the MySQL installer from the web.

  • In a proxy environment, container registration fails during unified setup installation. A pop-up window is displayed after you click Finish.

  • The unified setup installer does not honor a proxy address value when it's in FQDN or http://FQDN format. In this situation, the installation fails at the "Install configuration server and process server" step.

  • When you try to re-protect a virtual machine after failback, you receive the following error message:
    Protection could not be enabled.
    Enable protection failed on the master target server CSPSMT-V2 with error code EA0508 while detecting the newly added disks.
    Disable the protection. Restart the master target server CSPSMT-V2 and enable protection again. If the issue persists, please contact the Microsoft support. (Provider error code: 95134)

  • When you re-protect a virtual machine after failback, and vMotion moves the virtual machine from one host to another, you receive the following error message:
    No retention window is available for 'Disk0, Disk2, Disk3' disks on the master target server.
    Error ID:78025

    Possible causes: Resynchronization (or initial replication) may not have completed.

    Recommendation: If the disk is resynchronizing, please wait for it to reach the Ok replication status for the recovery window information to be updated.

  • Proxy settings are not honored when you try to register your configuration server by using the cspsconfigtool.exe utility.

  • Third-party application backups fail for virtual machine replicating to Azure.

  • Failback from Azure to on-premises fails, and you receive the following error message:
    The unplanned failover of the source machine failed. (Error code: 78045)

    Possible causes
    VM Failover failed with Error: 'Failover failed. An internal error occurred with the master target server WIN-RJ-CS during recovery and failed with the error code EA0609.Please contact Microsoft support for guidance on recovering this virtual machine.'.

    Recommendation
    Resolve the issue and try the operation again.

  • vCenter Discovery fails, and you receive the following error message:
    The operation could not be completed. (Error code: 559)
    Provider error: Discovery operation failed.
    Discovery of the vCenter server <IPAddress>:443 failed with error code EC0404. Operation failed with an error from vSphere CLI.
    Refer to the error string Object reference not set to an instance of an object in vSphere CLI 5.5 documentation to fix the issue.

    Disable protection and retry the operation after ensuring that all prerequisites for push installation of the mobility service are complete.

    See http://go.microsoft.com/fwlink/?LinkId=613315 for guidance on discovery. (Provider error code: 95126)

    Possible causes: See the provider errors for more information.

    Recommendation: Resolve the issue and retry the operation.

Microsoft Azure Site Recovery Service (Service Side Fixes)

  • When you try to use the secure shell (SSH) into a Red Hat Enterprise Linux (RHEL) failed over into Azure, you receive the following error message:
    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

  • Hyper-V virtual machines that are "live" migrated after they are protected are not added into a Recovery Plan.

  • When you try to disable protection for a virtual machine, you receive the following error message:
    Errors (1)

    An internal error occurred. (Error code: 499)

    Possible causes The operation failed due to an internal error.

    Recommendation Retry the last action. If the issue persists, contact Support

  • When you migrate protected virtual machines from legacy to the new "VMware to Azure" stack, 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 Timed out.

    Recommendation: Resolve the issue and retry the operation.

  • When you failback a virtual machine from Azure to on-premises, the virtual machine does not start and you receive the following error message:
    The operation could not be completed. Discovery failed as source machine with IP address xxx.xxx.xxx.xxxx (host Id: <guid>) was not able to reach the configuration server. ( Error code : 559)

    Possible Causes: See the provider errors for more information.

    Recommended Actions: Resolve the issue and retry the operation.

  • When you try to perform a test failover of a virtual machine, you receive the following error message:
    Virtual machine 'VMName' could not be created under resource group ‘ResourceGroupName'. Azure error message: 'The value of parameter vmSize is invalid.'.

  • When you try to enable protection for a virtual machine, you receive the following error message:
    An internal error occurred. (Error code: 499)

    Possible causes: The operation failed due to an internal error.

    Recommendation: Retry the last action. If the issue persists, contact Support.

  • Time out intervals for Recovery Plan failover workflows are increased to 2 hours.

  • Optimization fixes are included in this update to reduce failover times for Generation 2 virtual machines.

Updating your Azure Site Recovery On-Premises Components

ScenarioSteps
Between two on-premises VMM Sites

-or-

Between two on-premises VMM sites that use SAN array replication
  1. Download Update Rollup 11 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 11 on your on-premises VMM Server that is managing the Recovery Site first.
  3. After the Recovery Site is updated, install Update Rollup 11 on the VMM Server that is managing your Primary site.

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
  1. Download Update Rollup 11 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 11 on your on-premises VMM Server.

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
  1. Download Update Rollup 11 for Microsoft Azure Site Recovery Provider.
  2. Install the provider on each node of the Hyper-V Servers that you have registered in Azure Site Recovery.
Between an on-premises VMware/Physical Site t Azure
  1. Download Update Rollup 11 for Microsoft Azure Site Recovery Unified Setup.
  2. Install this update first on your on-premises management server, this is the server that contains your Configuration Server and Process server roles installed on it.
  3. If you have scale out process server, update them next.
  4. Next go to the Azure Portal to the Protected Items/Replicated Items pate.
  5. When you select any VM on this page, an Update Agent button appears at the bottom.
  6. Click this button on each VM to update the Mobility Service Agent on all the protected VMs.

Update information

To resolve these issues, install this update from the Microsoft Download Center.

The following files are available for download:
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 Microsoft Azure Site Recovery Provider Update Rollup 11 (version 5.1.1500), 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 Microsoft Azure Site Recovery Unified Setup Update Rollup 11 (version 9.0.4083.1), you must have the following installed:
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.0.4016.1)

Note You can check the installed provider version through 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 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.
Properties

Article ID: 3147169 - Last Review: 04/05/2016 16:11:00 - Revision: 3.0

Microsoft Azure

  • kbqfe kbsurveynew kbfix kbexpertiseinter kbbug KB3147169
Feedback