Deploy vsphere replication using webclient

* You must have a vCenter deployed on the environment.
* you must have a compatible version of vR iso/ovf downloaded. (The build of vR used on the environment generally depends on the version of the vCenter, if you are unsure as to which version of vR do download, then read this guide here)



Log into the web client and bring up the Deploy ovf template wizard
Note: If you have trouble with CIP (client integration plugin on vCenter 6.0.x and 5.x), try firefox build 30 and CIP for firefox, Alternatively,  you may deploy this using OVFtool as described on my blog here:)

Mount the ISO and point to the ISO drive\bin\ and select the below files as on the screenshot.

Select the respective Datacenter and cluster

Set in the root password and networking information


Once the appliance has been deployed, Power on the Appliance (using web client only!!) and log in to the VAMI page (https://vr-ip:5480)

Switch to the vR>Configuration tab and correct the below
* Lookup service URL (should this be an external PSC)
* username (if you have a custom username/vsphere domain)
* Password

Click on save and restart, it should prompt for a certificate validation like that of the below. if you do not see the below, Ensure the vCenter FQDN can be resolved from the replication appliance.

If successful, you should see the below.


Log out and log in to the vSphere web-client to load the plugin. In some rare occurrences, you will need to restart the vSphere-client service for this plugin to be pulled up.



If you have vCenter 6.0 U2 and vR 6.1.2, the Plugin will not load if the vCenter does not have access to the internet. Please implement the action plan as described here:

Registering the vR to vCenter might fail with SSL validation errors. This is commonly observed with vCenter 6.0 GA, U1 or if it had been upgraded from this build and the certs were changed at one of these builds. Validate this with task 0 as per the below KB and implement if applicable

External PSC:
Embedded PSC:






















Configuring replication using existing seeds/reverse replication

Before proceeding, Ensure there are no stale replications. The VM name must not be listed in the vCenter server>Monitor>Vsphere replication>(on the source) outgoing,  incoming tab (for the destination)

Configuring replication using existing seeds are rather simple.  Configure replication like you normally would except, you would select the datastore>Folder where the source VM’s virtual disk’s are located.

Configure replication:

Select target site:

Select VR server:

Click on Edit for the VM

Select Datastore>VM folder where the disks are located

for the vR to detect the disk as seed, the Disk name must be identical to that of what is on the source side. you will see the below message when it picks up the seed.  Click on “use existing” to use the seeds

Click on use all seeds

Proceed with the wizard

The status of replication is expected to be “initial full sync” however if you click on the i icon as highlighted below, you will see it doing a checksum.

The replications should resume once the checksum has been compared








Recovering a VM using vSphere replication

Log into the recovery site vCenter webclient>vCenter server>Monitor>vSphere replication>incomeing replication>


Click on the VM that you wish to recover and click on the recover button: 


Should you be performing a planned migration of the VM (with the most recent change, select Synchronise recently change (you will need to authenticate with the source side vCenter) ,. Else, use the latest available data or point in time to recover to a point in time snapshot

in my  scenario, the source site was down and  the VM needs to be recovered on the DR,


Now the VM has been recovered and is running at the DR site



Configuring VM replications using vSphere replication

Prerequisites:  Vsphere replication management server must be deployed and registered on the to the vCenter server. For instruction on how to deploy and set up the vR, Click here:


Right click on the VM that you wish to replicate

Select Replicate to vCenter server

If the target site (remote vCenter) is not already on the list, click on add remote site. If you are replicating to a datastore on the same site, click on the site and click next (skip the add remote site part)

Type Fill in the Platform services controller  name, username and password and click on log in, you should see the vCenter server (similar to the image below)–Click on ok.

you should now see the target vCenter on the target site list:

Select a replication server (should you have multiple servers registered to the vCenter), and click on next:


Click on edit on the below

Select a datastore:

switch to the vR plugin (outgoing from protected or incoming from recovery) to check the progress of replication

Outgoing from Protected

Incoming from recovery


Walk through: Simple install of vCenter server 5.5

Installation over view:

Simple install assume’s that all vCenter components are to be installed on the same box.

Components installed during a simple install include:

  • Prerequisites: (installation media\Single Sign-On\prerequisites)
    • KFW.msi
    • Vmware-Openssl
    • VMware-Pythn
    • VMware-jre
    • VMware-tcserver
    • Microsoft Visual c++ Redist 2008
  • VMware Single Single sign on
  • VMware vSphere webclient
  • vCenter Inventory Service
  • vCenter Server
  • VMware vSphere Profile-Driven Storage


Mount the install iso and launch the autorun.exe from the disk drive.

Select simple install and run through the wizard


Type in the SSO password

Sso site name:


SSO port

installation path:

Validate and then hit install

Installation wizard steps here:









web client installation

Inventory Service

vCenter Server

DB Configuration

If you already have a SQL server on the environment, Ensure the ODBC drivers are installed and create a DSN to the SQL server.  Else, leave this to the default to install SQL express 2008


  • express instance has a 4GB database size limitation.
  • admin privileges on the SQL instance are granted to the account used at the time of install.

Service Account


Inventory size

SSO thumbprint validation: