Best practice: Back up vSphere VMs restored using Rapid VM Restore

To prevent data loss, we highly recommend backing up vSphere virtual machines (VMs) that are restored using Rapid VM Restore. When a VM is first restored using Rapid VM Restore, it is dependent on a running Rapid VM Restore process and connections to the VRA and vault. If the connection is lost to the VRA or vault, the VM could be lost. 

We also recommend backing up a VM immediately before migrating it, in case a problem occurs during the migration. You cannot back up a VM while it is being migrated, or migrate a VM while it is being backed up.

If you restore a VM and the original VM still exists in the vSphere environment, the VM will be restored as a copy of the original VM. You must modify your backup job to include the restored VM.

If you restore a VM and the original VM no longer exists in the vSphere environment, the VM will be restored with the same unique identifier (UUID) as the original VM. The restored VM will be backed up by the existing job, although the first backup might take longer than expected.

In a disaster recovery situation, if multiple VMs from the same backup job no longer exist in the vSphere environment, restore all missing VMs using Rapid VM Restore before running the backup job. If you run the job when only some of the VMs have been restored, the backup will skip the missing VMs and they will reseed when the backup job next runs.