Run this workflow to recover your production virtual machines from your source site to vCloud Air. When possible, VMware recommends you test the recovery before running the recovery.

You can recover a virtual machine by using vCloud Air when your source site is no longer accessible. You might be able to begin a recovery from your source site by using your local vSphere Web Client; for example, you have sufficient warning of an outage and still have access to your local vSphere Web Client so that you can run a planned migration.

For information about recovering virtual machines to the cloud by using planned migration, see What Happens During a Planned Migration in vSphere Replication 6.0 for Disaster Recovery to Cloud.

When you recover a virtual machine from your source site to vCloud Air, the production state of the virtual machine represents a point in time before the outage. Data accumulated after the last replication to vCloud Air and before the recovery is not available in the cloud.

Recovering a virtual machine to vCloud Air stops replication from the source site.

By enabling the multiple point in time (MPIT) setting, you can leverage previous replication points for better control on failover. It allows you to:

Set up to 24 previous restore points

Choose your restore point

Restore up to 24 days previous replication points (dependent on your RPO setting)

Choose from up to 24 Recovery Snapshots

You can choose the MPIT settings in the Recovery settings step while configuring a virtual machine for replication in the vSphere Web Client. See Configure a Replication to Cloud for a Single Virtual Machine in vSphere Replication 6.0 for Disaster Recovery to Cloud for information about configuring replication to the cloud.

Configure Replication - Set MPIT

Assume you have set a 15 minutes (minimum) recovery point objective (RPO) and you start the replication at 9:00 a.m., which means data changes for that particular virtual machine are replicated every 15 minutes. Now in the event of a failover, you can pick a specific time to recover from. For example, if the on-premises data center has an issue and you need to failover at 11 a.m. However, at that time you find that the data may not be suitable. If you have enabled MPIT, you can recover the data copied over at say, 10:30 a.m.

If you were to set your RPO 24 hours (maximum), then you would have the ability to restore up to 24 days previous replication points. This allows you to failback up to 24 days. With the MPIT recovery you can pick the specific point in time that you want to have data recovered, allowing you to successfully recover in the event of data corruption.