Set up the source environment for VMware to Azure replication

This article describes how to set up your source on-premises environment, to replicate VMware VMs to Azure. It includes steps for selecting your replication scenario, setting up an on-premises machine as the Site Recovery configuration server, and automatically discovering on-premises VMs.

Prerequisites

The article assumes that you have already:

Choose your protection goals

  1. In Recovery Services vaults, select the vault name. We're using ContosoVMVault for this scenario.
  2. In Getting Started, select Site Recovery. Then select Prepare Infrastructure.
  3. In Protection goal > Where are your machines located, select On-premises.
  4. In Where do you want to replicate your machines, select To Azure.
  5. In Are your machines virtualized, select Yes, with VMware vSphere Hypervisor. Then select OK.

Set up the configuration server

You can set up the configuration server as an on-premises VMware VM through an Open Virtualization Application (OVA) template. Learn more about the components that will be installed on the VMware VM.

  1. Learn about the prerequisites for configuration server deployment.
  2. Check capacity numbers for deployment.
  3. Download and import the OVA template to set up an on-premises VMware VM that runs the configuration server. The licence provided with the template is an evaluation licence and is valid for 180 days. Post this period, customer needs to activate the windows with a procured licence.
  4. Turn on the VMware VM, and register it in the Recovery Services vault.

Azure Site Recovery folder exclusions from Antivirus program

If Antivirus software is active on Source machine

If source machine has an Antivirus software active, installation folder should be excluded. So, exclude folder C:\ProgramData\ASR\agent for smooth replication.

If Antivirus Software is active on Configuration server

Exclude following folders from Antivirus software for smooth replication and to avoid connectivity issues

  • C:\Program Files\Microsoft Azure Recovery Services Agent.
  • C:\Program Files\Microsoft Azure Site Recovery Provider
  • C:\Program Files\Microsoft Azure Site Recovery Configuration Manager
  • C:\Program Files\Microsoft Azure Site Recovery Error Collection Tool
    • C:\thirdparty
    • C:\Temp
    • C:\strawberry
    • C:\ProgramData\MySQL
    • C:\Program Files (x86)\MySQL
    • C:\ProgramData\ASR
    • C:\ProgramData\Microsoft Azure Site Recovery
    • C:\ProgramData\ASRLogs
    • C:\ProgramData\ASRSetupLogs
    • C:\ProgramData\LogUploadServiceLogs
    • C:\inetpub
    • ASR server installation directory. For example: E:\Program Files (x86)\Microsoft Azure Site Recovery

If Antivirus Software is active on scale-out Process server/Master Target

Exclude following folders from Antivirus software

  1. C:\Program Files\Microsoft Azure Recovery Services Agent
  2. C:\ProgramData\ASR
  3. C:\ProgramData\ASRLogs
  4. C:\ProgramData\ASRSetupLogs
  5. C:\ProgramData\LogUploadServiceLogs
  6. C:\ProgramData\Microsoft Azure Site Recovery
  7. ASR load balanced process server installation directory, Example: C:\Program Files (x86)\Microsoft Azure Site Recovery

Common issues

Installation failures

Sample error message Recommended action
ERROR Failed to load Accounts. Error: System.IO.IOException: Unable to read data from the transport connection when installing and registering the CS server. Ensure that TLS 1.0 is enabled on the computer.

Registration failures

Registration failures can be debugged by reviewing the logs in the %ProgramData%\ASRLogs folder.

Sample error message Recommended action
09:20:06:InnerException.Type: SrsRestApiClientLib.AcsException,InnerException.
Message: ACS50008: SAML token is invalid.
Trace ID: 1921ea5b-4723-4be7-8087-a75d3f9e1072
Correlation ID: 62fea7e6-2197-4be4-a2c0-71ceb7aa2d97>
Timestamp: 2016-12-12 14:50:08Z
Ensure that the time on your system clock is not more than 15 minutes off the local time. Rerun the installer to complete the registration.
09:35:27 :DRRegistrationException while trying to get all disaster recovery vault for the selected certificate: : Threw Exception.Type:Microsoft.DisasterRecovery.Registration.DRRegistrationException, Exception.Message: ACS50008: SAML token is invalid.
Trace ID: e5ad1af1-2d39-4970-8eef-096e325c9950
Correlation ID: abe9deb8-3e64-464d-8375-36db9816427a
Timestamp: 2016-05-19 01:35:39Z
Ensure that the time on your system clock is not more than 15 minutes off the local time. Rerun the installer to complete the registration.
06:28:45:Failed to create certificate
06:28:45:Setup cannot proceed. A certificate required to authenticate to Site Recovery cannot be created. Rerun Setup
Ensure you are running setup as a local administrator.

Next steps

Set up your target environment