Instantly Recovering VMs (8.0)
When Instant VM Recovery is initiated, a temporary data store is created on the Unitrends VBA's backup storage and then presented to the hypervisor. The VM is then started and begins running right from the backup storage.
After the Instant Recovery job has completed, you have a few options, depending on what you'd like to do with your VM. If you were testing only, you would simply end the instant recovery session after verifying your backup. If you intend to keep the VM, you have two options for moving the VM's disks off of the temporary backup storage to your production storage. The first requires proper VMware vSphere licensing and involves using Storage vMotion to migrate the virtual machine disks to your production storage. The second method, UVB Motion, is available for users that do not have the proper licensing or those that do not want to wait for migration.
VMware Storage vMotionTM and Instant Recovery
After instantly recovering your virtual machines, you can leverage the tools that you are already licensed for through VMware to migrate your data into your production storage to ensure the best performance. This process involves no downtime and ensures all changes that occurred while running from the temporary backup storage are moved with the VM to production.
UVB Motion - Seeding and Completing
UVB Motion is a two-step process used to move instantly recovered VMs off of temporary storage to production storage and also merge any changes stored on the write space location. The first step, seeding is essentially a standard restore that is initiated for an instantly recovered VM. UVB Motion Seeding can be initiated along with the instant recovery job or it can be started at any time while the instantly recovered VM is active.
The second and final step of the process, Complete UVB Motion, can occur when the seeding process has completed and when the instantly recovered VM is powered down. The Complete UVB Motion step merges any of the changes made to the instantly recovered VM with the seeded VM restored to permanent storage. The instant recovery VM is then removed. When this step is finished, you have a fully restored and up to date version of your recovered virtual machine.
Instant VM Recovery Notes
- To mount the temporary data store used in the Instant Recovery process, a configured VMkernel port is required.
- The temporary data store used to run the instantly recovered virtual machine (data store that begins with UVBIR within the hypervisor) should never be used as a target for recovery or replication. The Recovery and Replication wizards will display these as available target data stores - but these are temporary locations that are removed when instant recovery sessions are complete.
- The temporary mounted data store should not be modified in any way.
- If an instant recovery session is interrupted and it cannot be recovered, you will need to manually cleanup the temporary mounted data store by unmounting it from the hypervisor.
- If a Unitrends VBA is reset or restarted while instant recovery VMs are active, the sessions will be continued when the Unitrends VBA starts again.