Update Rollup 11 for Azure Site Recovery

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.