vSphere Replication (VR) uses replication technologies included in ESX Servers with the assistance of virtual appliances to replicate virtual machines between sites. VR is provided by vSphere Replication Servers (VR Servers or VRS). VR Servers are managed by the vSphere Replication Managment Server (VRMS). Both VRMS and VR Servers are virtual appliances. VRMS provides a way to manage VR Servers across multiple hosts. If you are using VR, you must establish at least one vSphere Replication Server and exactly one VRMS at the recovery site. To enable replication in both directions, you must deploy exactly one VRMS at each site and at least one VRS at each site. You may want to create multiple VR Servers at each site if multiple servers are required to meet your load balancing needs for replication of virtual machines. Each VRMS must be registered with a corresponding vCenter Server. For example, the primary site VRMS must be registered with the primary site vCenter Servers.Both the VRMS and VRS appliances provide a virtual appliance management interface (VAMI). These interfaces can be used to configure the VRMS database, as well as network settings, public-key certificates, and passwords for the appliances. Before using VR, you need to configure the VR infrastructure including having managed IP defined in runtime settings at both sites and having a VRMS database installed. This video provides useful guidance to help ensure you complete the installation and configuration process correctly. When installing SRM, be certain to select the VR option. If you have installed SRM and want to add VR, you can add that option by running the installer again. So, here are the steps for configure-ring vSphere SRM Replication for a Single Virtual Machine.1. On the vSphere Client Home page, click VMs and Templates. 2. Browse the inventory to find the single virtual machine to be replicated using VR. Right-click the virtual machine and click vSphere Replication.3. In the Replication Settings page, configure general replication settings. These settings include the disk file location to which the virtual machine is replicated on the recovery site, how often the virtual machine is replicated, and how the guest OS is quiesced. Use the Recovery Point Objective (RPO) slider or enter a value to configure the maximum amount of data that can be lost during the recovery. The available range is from 15 minutes to 24 hours. For example, a recovery point objective of one hour seeks to ensure that the virtual machine loses no more than one hour of data during the recovery. For smaller RPOs, less data is lost in a recovery, but more network bandwidth is consumed keeping the replica synchronized. The available quiescing types are determined by the virtual machine's operating system. Microsoft Volume Shadow Copy Service (VSS) quiescing is supported for Windows virtual machines running Windows XP or later. Linux does not support quiescing. If no target file location is specified or if you want to override the default determined by the datastore mappings, click Browse to select a target location for the virtual machine.