Set up the source environment (VMware to Azure)

This article describes how to set up your on-premises environment to start replicating virtual machines running on VMware to Azure.

Prerequisites

The article assumes that you have already created:

  • A Recovery Services Vault in the Azure portal.
  • A dedicated account in your VMware vCenter that can be used for automatic discovery.
  • A virtual machine on which to install the configuration server.

Configuration server minimum requirements

The following table lists the minimum hardware, software, and network requirements for a configuration server.

Important

When deploying a Configuration Server for protecting VMware virtual machines, we recommend that you deploy it as a Highly Available (HA) virtual machine.

Hardware
Number of CPU cores 8
RAM 12 GB
Number of disks 3

- OS disk
- Process server cache disk
- Retention drive (for failback)
Disk free space (process server cache) 600 GB
Disk free space (retention disk) 600 GB
Software
Operating system version Windows Server 2012 R2
Operating system locale English (en-us)
VMware vSphere PowerCLI version PowerCLI 6.0
Windows Server roles Do not enable the following roles:
- Active Directory Domain Services
- Internet Information Services
- Hyper-V
Network
Network interface card type VMXNET3
IP address type Static
Internet access The server should be able to access the following URLs either directly or through a proxy server:
- *.accesscontrol.windows.net
- *.backup.windowsazure.com
- *.store.core.windows.net
- *.blob.core.windows.net
- *.hypervrecoverymanager.windowsazure.com
- https://cdn.mysql.com/archives/mysql-5.5/mysql-5.5.37-win32.msi (not required for Scale-out Process Servers)
- time.nist.gov
- time.windows.com
Ports 443 (Control channel orchestration)
9443 (Data transport)
Note

HTTPS-based proxy servers are not supported by the configuration server.

Choose your protection goals

  1. In the Azure portal, go to the Recovery Services vault blade and select your vault.
  2. On the resource menu of the vault, go to Getting Started > Site Recovery > Step 1: Prepare Infrastructure > Protection goal.

    Choose goals

  3. In Protection goal, select To Azure, and choose Yes, with VMware vSphere Hypervisor. Then click OK.

    Choose goals

Set up the source environment

Setting up the source environment involves two main activities:

  • Install and register a configuration server with Site Recovery.
  • Discover your on-premises virtual machines by connecting Site Recovery to your on-premises VMware vCenter or vSphere EXSi hosts.

Step 1: Install and register a configuration server

  1. Click Step 1: Prepare Infrastructure > Source. In Prepare source, if you don’t have a configuration server, click +Configuration server to add one.

    Set up source

  2. On the Add Server blade, check that Configuration Server appears in Server type.
  3. Download the Site Recovery Unified Setup installation file.
  4. Download the vault registration key. You need the registration key when you run Unified Setup. The key is valid for five days after you generate it.

    Set up source

  5. On the machine you’re using as the configuration server, run Azure Site Recovery Unified Setup to install the configuration server, the process server, and the master target server.

Run Azure Site Recovery Unified Setup

Tip

Configuration server registration fails if the time on your computer's system clock differs from local time by more than five minutes. Synchronize your system clock with a Time Server before starting the installation.

  1. Run the Unified Setup installation file.
  2. In Before You Begin, select Install the configuration server and process server.

    Before you start

  3. In Third Party Software License, click I Accept to download and install MySQL.

    Third-party software

  4. In Registration, select the registration key you downloaded from the vault.

    Registration

  5. In Internet Settings, specify how the Provider running on the configuration server connects to Azure Site Recovery over the Internet.

    a. If you want to connect with the proxy that's currently set up on the machine, select Connect to Azure Site Recovery using a proxy server.

    b. If you want the Provider to connect directly, select Connect directly to Azure Site Recovery without a proxy server.

    c. If the existing proxy requires authentication, or if you want to use a custom proxy for the Provider connection, select Connect with custom proxy settings.

    • If you use a custom proxy, you need to specify the address, port, and credentials.
    • If you're using a proxy, you should have already allowed the URLs described in Prerequisites.

      Firewall

  6. In Prerequisites Check, Setup runs a check to make sure that installation can run. If a warning appears about the Global time sync check, verify that the time on the system clock (Date and Time settings) is the same as the time zone.

    Prerequisites

  7. In MySQL Configuration, create credentials for logging on to the MySQL server instance that is installed.

    MySQL

  8. In Environment Details, select whether you're going to replicate VMware VMs. If you are, then Setup checks that PowerCLI 6.0 is installed.

    MySQL

  9. In Install Location, select where you want to install the binaries and store the cache. The drive you select must have at least 5 GB of disk space available, but we recommend a cache drive with at least 600 GB of free space.

    Install location

  10. In Network Selection, specify the listener (network adapter and SSL port) on which the configuration server sends and receives replication data. Port 9443 is the default port used for sending and receiving replication traffic, but you can modify this port number to suit your environment's requirements. In addition to the port 9443, we also open port 443, which is used by a web server to orchestrate replication operations. Do not use port 443 for sending or receiving replication traffic.

    Network selection

  11. In Summary, review the information and click Install. When installation finishes, a passphrase is generated. You will need this when you enable replication, so copy it and keep it in a secure location.

    Summary

After registration finishes, the server is displayed on the Settings > Servers blade in the vault.

Note

The configuration server can be installed via command line. For more information, see Installing the configuration server using Command-line tools.

Add the VMware account for automatic discovery

  1. On your configuration server, launch CSPSConfigtool.exe. It is available as a shortcut on the desktop and located in the install location\home\svsystems\bin folder.
  2. Click Manage Accounts > Add Account.

    Add account

  3. In Account Details, add the account that will be used for automatic discovery.

    Details

    Note

    It can take 15 minutes or more for the account name to appear in the portal. To update immediately, click Configuration Servers > server name > Refresh Server.

Step 2: Add a vCenter

To allow Azure Site Recovery to discover virtual machines running in your on-premises environment, you need to connect your VMware vCenter Server or vSphere ESXi hosts with Site Recovery.

Select +vCenter to start connecting a VMware vCenter server or a VMware vSphere ESXi host.

  • In Add vCenter, specify a friendly name for the vSphere host or vCenter server, and then specify the IP address or FQDN of the server. Leave the port as 443 unless your VMware servers are configured to listen for requests on a different port. Select the account that is to connect to the VMware vCenter or vSphere ESXi server. Click OK.

    VMware

    Note

    If you're adding the VMware vCenter server or VMware vSphere host with an account that doesn't have administrator privileges on the vCenter or host server, make sure that the account has these privileges enabled: Datacenter, Datastore, Folder, Host, Network, Resource, Virtual machine, and vSphere Distributed Switch. In addition, the VMware vCenter server needs the Storage views privilege enabled.

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 in Azure.