About the Mobility service for VMware VMs and physical servers

When you set up disaster recovery for VMware virtual machines (VM) and physical servers using Azure Site Recovery, you install the Site Recovery Mobility service on each on-premises VMware VM and physical server. The Mobility service captures data writes on the machine, and forwards them to the Site Recovery process server. The Mobility service is installed by the Mobility service agent software that you can deploy using the following methods:

  • Push installation: When protection is enabled via the Azure portal, Site Recovery installs the Mobility service on the server.
  • Manual installation: You can install the Mobility service manually on each machine through the user interface (UI) or command prompt.
  • Automated deployment: You can automate the Mobility service installation with software deployment tools such as Configuration Manager.

Note

The Mobility service uses approximately 6%-10% of memory on source machines for VMware VMs or physical machines.

Antivirus on replicated machines

If machines that you want to replicate are running antivirus software, exclude the Mobility service's installation folder C:\ProgramData\ASR\agent from antivirus operations. This exclusion ensures that replication will work as expected.

Push installation

Push installation is an integral part of the job that's run from the Azure portal to enable replication. After choosing the set of VMs you wish to protect and enable replication, the configuration server pushes the Mobility service agent to the servers, installs the agent, and completes the agent's registration with the configuration server.

Prerequisites

The push installation workflow is described in the following sections:

Mobility service agent version 9.23 and higher

For more information about version 9.23 see Update Rollup 35 for Azure Site Recovery.

During a push installation of the Mobility service, the following steps are performed:

  1. The agent is pushed to the source machine. Copying the agent to the source machine can fail due to multiple environmental errors. Visit our guidance to troubleshoot push installation failures.

  2. After the agent is successfully copied to the server, a prerequisite check is performed on the server.

    • If all prerequisites are met, the installation begins.
    • The installation fails if one or more of the prerequisites aren't met.
  3. As part of the agent installation, the Volume Shadow Copy Service (VSS) provider for Azure Site Recovery is installed. The VSS provider is used to generate application-consistent recovery points. If installation of the VSS provider fails, this step is skipped and the agent installation continues.

  4. If the agent installation succeeds but the VSS provider installation fails, then the job status is marked as Warning. This doesn't impact crash-consistent recovery point generation.

    • To generate application-consistent recovery points, refer to our guidance to complete a manual installation of the Site Recovery VSS provider.
    • If you don't want to generate application-consistent recovery points, modify the replication policy to turn off application-consistent recovery points.

Mobility service agent version 9.22 and below

  1. The agent is pushed to the source machine. Copying the agent to the source machine can fail due to multiple environmental errors. Refer to our guidance to troubleshoot push installation failures.

  2. After the agent is successfully copied to the server, a prerequisite check is performed on the server.

    • If all prerequisites are met, the installation begins.
    • The installation fails if one or more of the prerequisites aren't met.
  3. As part of the agent installation, the Volume Shadow Copy Service (VSS) provider for Azure Site Recovery is installed. The VSS provider is used to generate application-consistent recovery points.

    • If the VSS provider installation fails, the agent installation will fail. To avoid failure of the agent installation, use version 9.23 or higher to generate crash-consistent recovery points and do a manual install of the VSS provider.

Install the Mobility service using UI

Prerequisites

Important

Don't use the UI installation method if you're replicating an Azure Infrastructure as a Service (IaaS) VM from one Azure region to another. Use the command prompt installation.

  1. Copy the installation file to the machine, and run it.

  2. In Installation Option, select Install mobility service.

  3. Choose the installation location and select Install.

    Mobility service installation option page.

  4. Monitor the installation in Installation Progress. After the installation is finished, select Proceed to Configuration to register the service with the configuration server.

    Mobility service registration page.

  5. In Configuration Server Details, specify the IP address and passphrase that you configured.

    Mobility service registration page.

  6. Select Register to finish the registration.

    Mobility service registration final page.

Install the Mobility service using command prompt

Prerequisites

Windows machine

  • From a command prompt, run the following commands to copy the installer to a local folder, such as C:\Temp, on the server that you want to protect. Replace the installer's file name with the actual file name.

    cd C:\Temp
    ren Microsoft-ASR_UA_version_Windows_GA_date_release.exe MobilityServiceInstaller.exe
    MobilityServiceInstaller.exe /q /x:C:\Temp\Extracted
    cd C:\Temp\Extracted
    
  • Run this command to install the agent.

    UnifiedAgent.exe /Role "MS" /InstallLocation "C:\Program Files (x86)\Microsoft Azure Site Recovery" /Platform "VmWare" /Silent
    
  • Run these commands to register the agent with the configuration server.

    cd C:\Program Files (x86)\Microsoft Azure Site Recovery\agent
    UnifiedAgentConfigurator.exe  /CSEndPoint <CSIP> /PassphraseFilePath <PassphraseFilePath>
    

Installation settings

Setting Details
Syntax UnifiedAgent.exe /Role \<MS/MT> /InstallLocation \<Install Location> /Platform "VmWare" /Silent
Setup logs %ProgramData%\ASRSetupLogs\ASRUnifiedAgentInstaller.log
/Role Mandatory installation parameter. Specifies whether the Mobility service (MS) or master target (MT) should be installed.
/InstallLocation Optional parameter. Specifies the Mobility service installation location (any folder).
/Platform Mandatory. Specifies the platform on which the Mobility service is installed:
VMware for VMware VMs/physical servers.
Azure for Azure VMs.

If you're treating Azure VMs as physical machines, specify VMware.
/Silent Optional. Specifies whether to run the installer in silent mode.

Registration settings

Setting Details
Syntax UnifiedAgentConfigurator.exe /CSEndPoint \<CSIP> /PassphraseFilePath \<PassphraseFilePath>
Agent configuration logs %ProgramData%\ASRSetupLogs\ASRUnifiedAgentConfigurator.log
/CSEndPoint Mandatory parameter. <CSIP> specifies the configuration server's IP address. Use any valid IP address.
/PassphraseFilePath Mandatory. Location of the passphrase. Use any valid UNC or local file path.

Linux machine

  1. From a terminal session, copy the installer to a local folder such as /tmp on the server that you want to protect. Replace the installer's file name with your Linux distribution's actual file name, then run the commands.

    cd /tmp ;
    tar -xvf Microsoft-ASR_UA_version_LinuxVersion_GA_date_release.tar.gz
    
  2. Install as follows:

    sudo ./install -d <Install Location> -r MS -v VmWare -q
    
  3. After the installation is finished, the Mobility service must be registered to the configuration server. Run the following command to register the Mobility service with the configuration server.

    /usr/local/ASR/Vx/bin/UnifiedAgentConfigurator.sh -i <CSIP> -P /var/passphrase.txt
    

Installation settings

Setting Details
Syntax ./install -d \<Install Location> -r \<MS/MT> -v VmWare -q
-r Mandatory installation parameter. Specifies whether the Mobility service (MS) or master target (MT) should be installed.
-d Optional parameter. Specifies the Mobility service installation location: /usr/local/ASR.
-v Mandatory. Specifies the platform on which Mobility service is installed.
VMware for VMware VMs/physical servers.
Azure for Azure VMs.
-q Optional. Specifies whether to run the installer in silent mode.

Registration settings

Setting Details
Syntax cd /usr/local/ASR/Vx/bin<br/><br/> UnifiedAgentConfigurator.sh -i \<CSIP> -P \<PassphraseFilePath>
-i Mandatory parameter. <CSIP> specifies the configuration server's IP address. Use any valid IP address.
-P Mandatory. Full file path of the file in which the passphrase is saved. Use any valid folder.

Azure Virtual Machine agent

  • Windows VMs: From version 9.7.0.0 of the Mobility service, the Azure VM agent is installed by the Mobility service installer. This ensures that when the machine fails over to Azure, the Azure VM meets the agent installation prerequisite for using any VM extension.
  • Linux VMs: The WALinuxAgent must be installed manually on the Azure VM after failover.

Locate installer files

On the configuration server go to the folder %ProgramData%\ASR\home\svsystems\pushinstallsvc\repository. Check which installer you need based on the operating system. The following table summarizes the installer files for each VMware VM and physical server operating system. Before you begin, you can review the supported operating systems.

Note

The file names use the syntax shown in the following table with version and date as placeholders for the real values. The actual file names will look similar to these examples:

  • Microsoft-ASR_UA_9.30.0.0_Windows_GA_22Oct2019_release.exe
  • Microsoft-ASR_UA_9.30.0.0_UBUNTU-16.04-64_GA_22Oct2019_release.tar.gz
Installer file Operating system (64-bit only)
Microsoft-ASR_UA_version_Windows_GA_date_release.exe Windows Server 2016
Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2 SP1
Microsoft-ASR_UA_version_RHEL6-64_GA_date_release.tar.gz Red Hat Enterprise Linux (RHEL) 6
CentOS 6
Microsoft-ASR_UA_version_RHEL7-64_GA_date_release.tar.gz Red Hat Enterprise Linux (RHEL) 7
CentOS 7
Microsoft-ASR_UA_version_SLES12-64_GA_date_release.tar.gz SUSE Linux Enterprise Server 12 SP1
Includes SP2 and SP3.
Microsoft-ASR_UA_version_SLES11-SP3-64_GA_date_release.tar.gz SUSE Linux Enterprise Server 11 SP3
Microsoft-ASR_UA_version_SLES11-SP4-64_GA_date_release.tar.gz SUSE Linux Enterprise Server 11 SP4
Microsoft-ASR_UA_version_OL6-64_GA_date_release.tar.gz Oracle Enterprise Linux 6.4
Oracle Enterprise Linux 6.5
Microsoft-ASR_UA_version_UBUNTU-14.04-64_GA_date_release.tar.gz Ubuntu Linux 14.04
Microsoft-ASR_UA_version_UBUNTU-16.04-64_GA_date_release.tar.gz Ubuntu Linux 16.04 LTS server
Microsoft-ASR_UA_version_DEBIAN7-64_GA_date_release.tar.gz Debian 7
Microsoft-ASR_UA_version_DEBIAN8-64_GA_date_release.tar.gz Debian 8

Next steps

Set up push installation for the Mobility service.