Hi, You can leverage vSphere Replication in different topologies: 1) The classic two sites setup, where each site is geographically separated from its pair site. This setup requires a vCen...
See more...
Hi, You can leverage vSphere Replication in different topologies: 1) The classic two sites setup, where each site is geographically separated from its pair site. This setup requires a vCenter Server and a vSphere Replication Appliance at both sites. When the primary site faces a disaster event, the recovery can be performed on the secondary site. 2) Single vCenter setup, in which you have several hosts/clusters managed by a single vCenter Server and you are replicating VMs between your hosts/clusters. In that case when one of the hosts “dies”, you could perform recovery on another host. This requires that your vCenter Server and VR Appliance are operational. The vSphere Replication Appliance consists of both a vSphere Replication Management Server and a vSphere Replication Server. The latter listens for the replication traffic on the target site and applies it on the target datastores. In an increased scale you can deploy up to 9 additional vSphere Replication Server appliances to distribute the replication load. In a single site setup, you may have also additional vSphere Replication Servers deployed for optimization purposes, so that they are “closer” to the target datastores. After you have performed successful recovery and your primary site is back, you can power off your VM on primary site (if it is running), remove it from inventory (but do not delete its disks) and then configure replication of the recovered VM to be replicated back to the original site using its original disks as replication seeds. In that way, VR will just copy the blocks that have been changed on the recovered VM since the disaster happened and you will reduce the traffic spread over. Hope this hleps!