VM Instant Recovery

Starting With Bacula Enterprise 12.6, it is now possible to recover a vSphere Virtual Machine in a matter of minutes by running it directly from a Bacula Volume.

Any changes made to the VM disks are virtual and temporary. This means that the disks remain in a read-only state. The users may write to the VM disks without the fear of corrupting their backups. Once the Virtual Machine is started, it is then possible via VMotion to migrate the temporary Virtual Machine to a production datastore.

The feature is available inside the mount-vm script and follows this workflow:

1. User chooses a VM backup.

2. Script mounts the VM disks locally.

3. User chooses the ESXi host that will own the VM.

4. Script creates a temporary NFS Datastore locally.

5. Script creates and powers on the VM in this temporary NFS Datastore.

6. User chooses to keep the VM permanently or to discard it.

To learn more about this feature, see the sections below:

• VM Instant Recovery Installation
• Recovery Scenarios
• VM Instant Recovery Limitations

See also

Go back to:

• Backup

• Restore

• Quiescing Guests

Go to:

• VMware Single Item Restore

• List Host Operations

Go back to the main vSphere Plugin Operations page.

Go back to the main vSphere Plugin page.