How to restore VMs, H/W configs and VMDKs from a host based backup

Ops Center Protector VMware Application Guide

Part Number

It is assumed that a policy, which creates VM backups exists, has been implemented and that at least one backup has been created in the designated destination store. See How to create VM restore points using host based backups for an example of how to do this.

This task describes the steps to follow when using a repository backup to:
  • restore entire VMs
  • restore individual virtual disks (VMDKs)
  • restore VM hardware configurations
  • clone entire VMs for repurposing
All the above scenarios follow the same basic workflow:
  1. Identify the destination where the VMs are to be restored, then ensure that it is prepared to receive them by locating the vCenter or ESX/ESXi Host node in the Nodes Inventory and checking it is authorized and online.
    If applications are accessing or running on the restore target VMs, then additional work may be required to suspend activity on those VMs prior to restoring.
  2. If there are backup policies currently active on the location where the VMs are being restored, these should be suspended while restoring is taking place.
  3. Locate the VMware backup to be restored by navigating to the Restore screen, then locate to the required recovery point.
    Note: The restore screen allows filtering by Application Node Type. When choosing VMware from this selection an extended filter will appear allowing recoverable items to be searched by Virtual Machine, Folder and Datastore names.
    Store Details listing available repository snapshots is displayed.
  4. Click Restore Snapshot to open the Restore from host based backup Wizard - VMware.
    The process of restoring data may result in overwriting some of the original data that exists on the restore location.

    Ensure that any critical data is copied to a safe location or is included in the data set being restored.

  5. Select the VMs, configurations or virtual disks required. Click Next.
    Tip: Each VM in the backup is listed and can be expanded to reveal its parts as follows:
    • <Virtual Machine Name>
      • System configuration
      • Virtual Hard disk <N> Configuration.vmdk
      • Virtual Hard disk <N> Data.vmdk
    Select the <Virtual Machine Name> to restore an entire VM. Select the System configuration to restore the hardware state. Select the Virtual Hard disk <N> Configuration.vmdk and corresponding Virtual Hard disk <N> Data.vmdk to restore individual virtual disks.

    Note that the items listed by Protector do not correspond directly to the files listed in the vSphere Client's datastore view since some are aggregated by Protector.

  6. Choose whether to restore to the Original location or create a Clone. Click Next.
    Note: You cannot restore a VM if one having the same name currently exists at that location; the restore job will fail if you attempt to do so.
  7. If creating a Clone:
    1. Specify a Cloned Virtual Machine Name Prefix (this will be prepended to the existing name of each VM being restored along with a '-' between the prefix and name) and a VMware server Destination Node. Click Next
    2. Select a Datacenter and folder. Click Next.
    3. Select a Compute Resource (host, cluster, resource pool or vApp). Click Next.
    4. Select a Datastore. Click Next.
  8. Select the Virtual Machine Options required following restoration: Power State After Creation / Network Card Connection. Click Finish.
    A Processing message will appear briefly, then the wizard will close and the Jobs Inventory will be displayed. A new Restore Job will appear at the top of the Jobs list, with the Progress entry initially indicating processing and finally indicating successful completion.
  9. Once the restore process is complete, further steps may be needed to fix-up the VM(s).
    The amount of fix-up work required depends on the applications accessing or running on the restored VM(s).
  10. Restart any applications that access or run on the restored VM(s).
  11. Resume any backup policies for the restored VM(s). If you have restored data to a new location for repurposing (test and development work for example), you should consider if it is necessary to implement a new backup policy to protect this new instance(s).