PowerProtect Data Manager 19.16 Virtual Machine User Guide

Restore individual virtual disks to an alternate virtual machine

When restoring individual virtual disks (VMDKs), a Restore to Alternate VM restores VMDKs to an alternate virtual machine on the same or a different vCenter server.

1. From the PowerProtect Data Manager UI, select Restore > Assets, and then select the Virtual Machine tab.
   The Restore window displays all virtual machines available for restore.
2. Select the checkbox next to the appropriate virtual machines and click Restore.
   You can also use the filter in the Name column to search for the name of the specific virtual machine or click the File Search button to search on specific criteria.
   The Restore wizard appears.
3. On the Select Copy page, for each virtual machine that is listed in the table, select the radio button next to the virtual machine and click Choose Copy.
   The Choose Copy dialog box appears.

   NOTE:If you click Next without choosing a copy, the most recent backup copy is used, and the Purpose page displays.
4. On the Choose Copy dialog:
   1. In the left pane, click to the right of the icon for the asset. The table in the right pane lists the backup copies.
   2. Select one of the available copies that display in the table.
   3. Click OK to save the selection and exit the dialog, and then click Next.
5. On the Purpose page, select Restore Individual Virtual Disks, and then click Next.
6. On the Restore Location page:
   1. Select Restore to Alternate VM.
   2. Select a vCenter server. The table updates to display the vCenter hierarchy.
   3. Select the virtual machine within the vCenter hierarchy where you want to restore the VMDKs.
      NOTE:For Linux virtual machines, if you select the original virtual machine as the alternate virtual machine, and then select disk 1 to restore, you might be unable to reboot the virtual machine after the restore completes.
   4. Click Next.
7. On the Select Disks page:
   • If you want a different configuration for each VMDK being restored, move the Configure Per Disk slider to the right, select each disk that you want to restore, and specify the storage location and the type of provisioning to use. Click Next.
   • If you want to use the same configuration for all VMDKs being restored, select the datastore and provisioning type to use for the restore, select each disk that you want to restore, and then click Next.
8. On the Options page:
   1. For low-bandwidth environments, select Enable DDBoost Compression.
      This option reduces network usage by compressing data on the protection storage system before transfer to the VM Direct Engine, which decompresses the data. Compression reduces restore times but increases CPU usage on both systems.
   2. Optionally, move the Select a Protection Engine slider to the right if you want to override the automatic protection engine selection, and then select another VM Direct Engine to use for the restore. When the restore job is started, the name of the protection engine used for the restore displays in the Jobs window Details pane.
   3. You can select Troubleshooting mode to enable debug logging, and then select the level of logging to use:
      • Info—Includes information such as status changes. This is the default log level for scheduled backups and restores.
      • Debug—Additional information that helps with problem diagnosis.
      • Trace—The most detailed amount of information for complex problem diagnosis.
   4. Click Next.
9. On the Summary page, click Restore.
   An informational dialog box appears indicating that the restore has started.

   NOTE:During the restore, the virtual machine will be powered on, if it is not powered on already. After the restore completes, the virtual machine returns to its power state prior to the restore.
10. Go to the Jobs window to monitor the restore.
    A restore job appears with a progress bar and start time.