VMware & Azure Site Recovery – Part 3: Replicating VM’s

This is the third instalment of my VMware and Azure Site Recovery series. In the last two posts I covered how to prepare for the service and installing the components within the cloud and private infrastructure to setup ready to make magic happen!

In this post, I’m going to go through client installation for a Windows and Linux box and setup replication jobs via the ASR interface online.

This process can be achieved in a number of ways: the Process Server can push out the client to servers you want to protect, you can install centrally (SCCM, GPO, Puppet, etc) or you can install manually. I decided to install it via the Process Server for the Windows server (this requires an account with local admin) and for the Linux server I installed manually as I didn’t trust the automated mechanism and the permissions model I have for Linux at work isn’t easy to have an account that isn’t root install things. (Easy life).

Windows Client:

1. Within the online ASR portal, via Site Recovery. Select a source of replication (vCenter Server and Process Server already configured).

ASRP3_1

2. For target, set the right accounts and then select the network that you want to fail-over into (as created previously).
ASRP3_2

3. Select a VM that you want to replicate from your inventory list. This is pulled directly from the vCenter Serve via the Process Server.
ASRP3_3

4. On the configuration properties, select the account that has permissions. In my case, the “AD VC PoC Account” is an account with vCenter permission and is also configured as local admin via GPO for this box. Purely for PoC purposes.

ASRP3_4

5. Select your replication policy for the VM. For me this was the default policy I created earlier.

ASRP3_5

6. Important! Before you proceed to step 7. Make sure the firewall on your server is set to allow traffic through from the process server or the next steps will fail! You need: Firewall & Print Sharing,

ASRP3_6

ASRP3_7

7. Last step is to enable replication.

ASRP3_8

8. Now the Process Server will contact the server and install the right components (agent) and enable replication.

ASRP3_9

9. After about 15 minutes, the installation should be complete! Replication should now start up.

ASRP3_9.5

Linux Client:

The Linux client requires two installs. One is the agent that talks/registers to the Process Server on site, the other is the replication agent.

1. On the process server get the appropriate Linux Agent file from: F:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\pushinstallsvc\repository and SCP it to the Linux box.

ASRP3_10

2. Navigate to your Process Server C:\ProgramData\Microsoft Azure Site Recovery\private. Open the “connection” file and copy the phrase down.

ASRP3_11

3. Unzip the installer and also create a “passphrase.txt” file and insert your passphrase.

ASR3_12

4. Install/Register the agent from the zip file:

ASRP3_13

5. Download the latest “WALinuxAgent” for replication to your Linux Box.

ASRP3_14

6. Unzip the file

ASRP3_15

7. Install and register the replication service:

ASRP3_16

8. Check that services are running:

ASRP3_17

After some private->cloud replication time (process server refresh) it should be possible to select the Linux VM from your inventory and replicate it, similar to how the Windows Server above was configured – minus the agent push.

I’m going to stop the post here and leave the replication/test fail-over for another post which should be the final one. The good thing about ASR is that once configured correctly it provide a “Test DR/Fail-over” option where you can run multiple simulations whilst maintaining replication!

Until next time!

2 comments

  1. Pingback: VMware&Azure Site Recovery - How to Code .NET
  2. Andrew Hellyer

    Hi Ryan,
    I have a question for a particular scenario.
    We are using ASR to for DR from vmware to azure. We also have iscsi (in guest mapped) volumes for hosts running SQL.
    Configuring the replicating from vmware allows me to exclude certain disks on the source (provided i preinstall the ASR agent on the source first).
    Failing over works just fine (we replicate the iscsi volumes into azure using netapp appliances).
    Reprotecting and failing back however, copies all disks attached to the VM when it was running in Azure (excluding the temp storage disk).
    I get no option to exclude disks, and only one breif mention anywhere from any of the MS doco which states

    “only the disks that were replicated from on-premis to Azure will be replicated back. Newly added disks on a failed over Azure virtual machine or on a failed over on-premises virtual machine will not be replicated by re-protect”

    Now this is contrary to what I observe – and I am just wondering if you know anything about this?

Leave a Reply

Your email address will not be published. Required fields are marked *