Update Rollup 13 for Azure Site Recovery

• Red Hat Enterprise Linux 7.1 (RHEL 7.1)
• Red Hat Enterprise Linux 7.2 (RHEL 7.2)
• CentOS 7.0
• CentOS 7.1
• CentOS 7.2

Microsoft Azure Site Recovery Provider

Improvements

• No improvements included

Issues fixed

• Azure Site Recovery Provider goes into an ERROR connection state after Virtual Machine Manager 2012 Update Rollup 9 is installed.
• Added Bypass list feature for the provider so that it can communicate faster with other components on the local network.

Microsoft Azure Site Recovery Unified Setup

Improvements

• Prerequisites added to make sure Service URLs can be accessed before installation is completed.

Issues fixed

• Reprotection of a virtual machine occurs, and you receive the following error message:
  
  Hit an exception while connecting to vCenter/vSphere.Exception details:
  System.Net.WebException: The request failed with HTTP status 403: Forbidden
• Unified Installer does not request consent from user before a restart.
• VMware vCenter Discovery fails on non-English languages.

Mobility Service

Improvements

• No improvements included

Issues fixed

• You can't use SSH to access an SUSE 11 SP3 virtual machine after failover into Azure.
• Register host by using cdpcli.exe always returns true even if there is a failure.
• Replication for a virtual machine hangs, and you see the following errors in the host log:
  
  VX : Caught exception while getting application settings talwrapper.cpp(98)[TalWrapper::post] CurlWrapper Post failed : server : 172.16.0.218, port : 443, phpUrl : request_handler.php, secure : true, ignoreCurlPartialError : false with error: [at curlwrapper.cpp:CurlWrapper::processCurlResponse:198] server returned error: 500
• Replication for a virtual machine hangs, and you see the following errors in the host log:
  
  Data upload blocked at source

Microsoft Azure Site Recovery (service side fixes)

Improvements

• No improvements included

Issues fixed

• Test failover fails and you receive the following error message:
  
  The failover of the source machine failed. (Error code: 78066)
  Possible causes: Unexpected error while performing failover operation.
  Recommendation: This may be recoverable, contact the support team.
• Failover of a virtual machine fails, and you receive the following error message:
  
  Error Message: The requested action couldn't be performed by the 'VMWare to Azure V2' Replication Provider.
  Possible Causes: The Provider action failed. Check other errors for more information.
  Recommended Action: Resolve the issue and retry the operation.
• Failover of a virtual machine fails, and you receive the following error message:
  
  Error Message: The failover of the source machine failed.
  Possible Causes: Unexpected error while performing failover operation.
  Recommended Action: This may be recoverable, contact the support team.
• Failover of a virtual machine fails, and you receive the following error message:
  
  ERROR ID 78066
  ERROR MESSAGE: The failover of the source machine failed.
  POSSIBLE CAUSES: Unexpected error while performing failover operation.
  RECOMMENDATION: This may be recoverable, contact the support team.
  ERROR ID 539
  ERROR MESSAGE: The requested action couldn't be performed by the 'VMWare to Azure V2' Replication Provider.
  POSSIBLE CAUSES: The Provider action failed. Check other errors for more information.
  RECOMMENDATION: Resolve the issue and retry the operation.
• Disable protection fails, and you receive the following error message:
  
  Disable protection failing.
  Error (1):
  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.
• Initial replication of the VM is in progress, but the virtual machine’s health is listed as Critical. Additionally, you receive the following error message on the portal:
  
  The primary or recovery virtual machine is no longer available. (Error ID: 60013)
  Possible causes: The primary or recovery virtual machine has been deleted from the on-premises site.
  Recommended Actions: If the recovery site virtual machine is available, trigger a failover of the virtual machine or remove the virtual machine from Azure Site Recovery.
• Enable Protection for a virtual machine fails, and you receive the following error message:
  
  Protection could not be enabled (Error Code : EP0856)
  Possible Cause: Push installation of the mobility service to the source machine Source_VM_IP failed with error code EP0856. Either the source machine is not running, or there are network connectivity issues between the process server SERVER_NAME and the source machine.
  Recommended Action:
  1. Ensure the source machine is accessible from the process server Server_NAME.
  2. Allow File and Printer Sharing in the Windows Firewall. Under Windows Firewall settings, select the option.
• Test Failover of a virtual machine fails, and you receive the following error message:
  
  Error Message: The operation was stopped.
  Possible Causes: The operation was stopped because the retry limit was exceeded.
  Recommended Action: Wait a while and retry the action.
• Failover fails if you try to reuse the same IP multiple times, and you receive the following error message:
  
  Error Message: Replica IP address IP_ADDRESS couldn't be updated for the network adapter of virtual machine VM_NAME.
  Possible Causes: IP address IP_ADDRESS in Azure virtual network Azure_Network_Name is already reserved for a network adapter of the virtual machine VM_NAME.
  Recommended Action: Try allocating a different IP address to this network adapter.
• Failover fails if you choose the GatewaySubnet as the subnet into which your virtual machine will fail over, and you receive the following error message:
  
  Cloud exception error - Code: GatewaySubnet, Error Message: Subnet with name 'GatewaySubnet' can be used only for the Gateway resource., Original message : {
  "error": {
  "code": "GatewaySubnet",
  "message": "Subnet with name 'GatewaySubnet' can be used only for the Gateway resource.",
  "details": []
  }
  }, Response body Code.
• Failback of 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.
• Virtual machine replication fails, and error 0x8079ffff occurs.

Updating your Azure Site Recovery on-premises components