Skip to main content
BlueXP backup and recovery for VMs

Restore Virtual Machines from Amazon FSx

Contributors netapp-manishc
PDFs

When you restore a Virtual Machine, you can overwrite the existing content with the backup copy that you select, or you can make a copy of the Virtual Machine.

You can restore VMs to the following locations:

  • Restore to original location

    • To the original datastore mounted on the original ESXi host (this overwrites the original VM)

  • Restore to alternate location

    • To a different datastore mounted on the original ESXi host

    • To the original datastore mounted on a different ESXi host that is managed by the same vCenter

    • To a different datastore mounted on a different ESXi host that is managed by the same vCenter

    • To a different datastore mounted on a different ESXi host that is managed by a different vCenter in linked mode

Before you begin

  • A backup must exist.

    You must have created a backup of the Virtual Machine using BlueXP backup and recovery for VMs before you can restore the Virtual Machine.

    Note

    Restore operations cannot finish successfully if there are Snapshot copies of the Virtual Machine that were performed by software other than BlueXP backup and recovery for VMs.

  • The Virtual Machine must not be in transit.

    The Virtual Machine that you want to restore must not be in a state of vMotion or Storage vMotion.

  • HA configuration errors.

    Ensure there are no HA configuration errors displayed on the vCenter ESXi Host Summary screen before restoring backups to a different location.

About this task

  • Virtual Machine is unregistered and registered again.

    The restore operation for Virtual Machines unregisters the original Virtual Machine, restores the Virtual Machine from a backup Snapshot copy, and registers the restored Virtual Machine with the same name and configuration on the same ESXi server. You must manually add the Virtual Machines to resource groups after the restore.

  • Restoring datastores

    You cannot restore a datastore, but you can restore any Virtual Machine in the datastore.

  • VMware consistency snapshot failures for a Virtual Machine.

    Even if a VMware consistency snapshot for a Virtual Machine fails, the Virtual Machine is nevertheless backed up. You can view the entities contained in the backup copy in the Restore wizard and use it for restore operations.

Steps

  1. In the VMware vSphere client toolbar, click Host and Clusters, and then select the storage system.

  2. In the left Navigator pane, right-click a Virtual Machine, then select BlueXP backup and recovery for VMs in the drop-down list, and then select Restore to start the wizard.

  3. In the Restore wizard, on the Select Backup page, select the backup Snapshot copy that you want to restore.

    You can search for a specific backup name or a partial backup name, or you can filter the backup list by clicking the filter icon and selecting a date and time range, selecting whether you want backups that contain VMware Snapshots, whether you want mounted backups, and the location. Click OK to return to the wizard.

  4. On the Select Scope page, select Entire Virtual Machine in the Restore scope field, then select the restore location, and then enter the destination information where the backup should be mounted.

    In the VM name field, if the same VM name exists, then the new VM name format is '<vm_name>_<timestamp>'.

    When restoring partial backups, the restore operation skips the Select Scope page.

  5. Enable Restart VM checkbox if you want the Virtual Machine to be powered on after the restore operation.

  6. On the Select Location page, select the location for the restored datastore.

  7. Review the Summary page and then click Finish.

  8. Optional: Monitor the operation progress by clicking Recent Tasks at the bottom of the screen.

After you finish

  • Add restored Virtual Machines to resource groups.

    Ensure that the newly restored VM is protected. If it is not, protect it by manually adding the restored VM to the appropriate resource groups.