With vSphere Replication you can replicate virtual machines from a source site to a target site.

You can set a recovery point objective (RPO) to a certain time interval depending on your data protection needs. vSphere Replication applies all changes made to virtual machines configured for replication at the source site to their replicas at the target site. This process reoccurs at the RPO interval that you set.

To replicate a virtual machine using vSphere Replication, you must deploy the vSphere Replication appliance at the source and target sites. A vSphere Replication infrastructure requires one vSphere Replication appliance at each site.

The source and target sites must be connected for you to be able to configure replications. If one of the sites is unreachable from the other site, is offline, if authentication fails, or if the certificates have changed, it shows the Connection issue state in the vSphere Replication interface. You cannot perform replications if one of the sites is in the Connection issue state due to these reasons. The sites can also appear in the Not authenticated state if you log in to the vSphere Web Client when a previous login session has expired. In this case, scheduled replications continue as normal. See vSphere Replication Sites Appear in the Not Authenticated State.

vSphere Replication does not support the recovery of multiple virtual machines from the same workflow. Each recovery workflow is for an individual virtual machine.

You cannot replicate powered-off virtual machines. Replication begins when the virtual machine is powered on. You cannot use vSphere Replication to replicate virtual machine templates.