Restoring Hyper-V data

Hyper-V restore jobs support Instant VM Restore and Instant Disk Restore scenarios, which are created automatically based on the selected source.

To define a Hyper-V restore job, complete the following steps:

1. In the navigation pane, click Manage Protection > Hypervisors > Hyper-V > Create Restore Job to open the "Snapshot restore" wizard.
   Tips:

   • You can also open the "Snapshot restore" wizard by clicking Jobs and Operations > Create Restore Job > Hyper-V.
   • For a running summary of your selections in the "Snapshot restore" wizard, move the cursor to the information icon in the navigation pane in the wizard.
   • To bypass the optional pages in the wizard, select Skip optional steps.
2. On the Source select page, take the following actions:
   1. Review the available sources, including virtual machines (VMs) and virtual disks (VDisks). You can expand a source by clicking its name.

      You can also enter all or part of a name in the Search for box to locate VMs that match the search criteria. You can use the wildcard character (*) to represent all or part of a name. For example, vm2* represents all resources that begin with "vm2".

   2. Click the plus icon next to the item that you want to add to the restore list next to the list of sources. You can add more than one item of the same type (VM or virtual disk).

      To remove an item from the restore list, click the minus icon next to the item.

   3. Click Next.
3. On the Source snapshot page, specify the instance of the VM or virtual disk that you want to restore. Complete the following fields and click Next to continue. Some fields are not displayed until you select a related field.

   Option	Description
   Restore Type	Select the type of restore job: On-demand Runs a one-time restore operation. Recurring Creates a repeating point-in-time restore job that runs on a schedule.
   Restore Location Type	Select a type of location from which to restore data: Site The site where snapshots were backed up. The site is defined on the System Configuration > Site pane. Cloud Offload The cloud server where snapshots were offloaded. The cloud server is defined on the System Configuration > Backup Storage > Cloud pane. Repository Offload The repository server where snapshots were offloaded. The repository server is defined on the System Configuration > Backup Storage > Repository Server pane. Cloud Archive The cloud server on which snapshots were archived. The cloud server is defined on the System Configuration > Backup Storage > Cloud pane. Repository Archive The repository server where snapshots were archived. The repository server is defined on the System Configuration > Backup Storage > Repository Server pane.
   Select a location	If you are restoring data from a site, select one of the following restore locations: Demo The demonstration site from which to restore snapshots. Primary The primary site location from which to restore snapshots. Secondary The secondary site location from which to restore snapshots. If you are restoring data from a cloud or repository server, select a server from the Select a location menu.
   Date selector	For on-demand restore operations, specify a range of dates to show the available snapshots within that range.
   Restore Point	For on-demand restore operations, select a snapshot from the list of available snapshots in the selected data range.
   Use alternate vSnap server for the restore job	If you are restoring data from a cloud resource or repository server, select this box to specify an alternative vSnap server, and then select a server from the Select alternate vSnap menu. When you restore data from a restore point that was offloaded or archived to a cloud resource or repository server, a vSnap server is used as a gateway to complete the operation. By default, the vSnap server that is used to complete the restore operation is the same vSnap server that is used to complete the backup and offload operations. To reduce the load on the vSnap server, you can select an alternative vSnap server to serve as the gateway.

4. On the Set destination page, choose the instance to be restored for the selected source and click Next:

   Original Hyper-V Host or Cluster

   Select this option to restore data to the original host or cluster.

   Alternate Hyper-V Host or Cluster

   Select this option to restore data to a local destination that is different from the original host or cluster, then select the alternative location from the available resources.

   In the VM Folder Destination field, enter the virtual machine folder path on the destination datastore. Note that the directory will be created if it does not exist. Use "/" as the root virtual machine folder of the targeted datastore.

5. On the Set datastore page, take the following actions:
   • If you are restoring data to an alternate Hyper-V host or cluster, select the destination datastore and click Next.
   • If you are restoring data to the original ESX Host or cluster, you do not need to set a datastore. Just click Next.
6. On the Set network page, specify the network settings to use for each chosen source and click Next.
   • If you are restoring data to the original Hyper-V host or cluster, specify the following network settings:

     Allow system to define IP configuration

     Select this option to allow your operating system to define the destination IP address. During a test mode restore operation, the destination virtual machine receives a new MAC address along with an associated NIC. Depending on your operating system, a new IP address can be assigned based on the original NIC of the virtual machine, or assigned through DHCP. During a production mode restore the MAC address does not change; therefore the IP address should be retained.

     Use original IP configuration

     Select this option to restore to the original host or cluster using your predefined IP address configuration. During the restore operation, the destination virtual machine receives a new MAC address, but the IP address is retained.

   • If you are restoring data to an alternate Hyper-V host or cluster, complete the following steps:
     1. In the Production and Test fields, set virtual networks for production and test restore job runs. Destination network settings for production and test environments should point to different locations to create a fenced network, which keeps virtual machines used for testing from interfering with virtual machines that are used for production. The networks that are associated with test and production modes will be used when the restore job is run in the associated mode.
     2. Set an IP address or subnet mask for virtual machines to be repurposed for development, testing, or disaster recovery use cases. Supported mapping types include IP to IP, IP to DHCP, and subnet to subnet. Virtual machines that contain multiple NICs are supported.
        Take one of the following actions:

        • To allow your operating system to define the destination subnets and IP addresses, click Use system defined subnets and IP addresses for VM guest OS on destination.
        • To use your predefined subnets and IP addresses, click Use original subnets and IP addresses for VM guest OS on destination.
        • To create a new mapping configuration, select Add mappings for subnets and IP addresses for VM guest OS on destination, click Add Mapping, and enter the IP address of the source machine in the Add Source Subnet or IP Address field.
          Choose one of the following network protocols:

          • Select DHCP to automatically select an IP and related configuration information if DHCP is available on the selected source.
          • Select Static to enter a specific subnet or IP address, subnet mask, gateway, and DNS. The Subnet / IP Address, Subnet Mask, and Gateway are required fields. If a subnet is entered as a source, a subnet must also be entered as a destination.
            Note: When a mapping is added, the source IP address must be entered into the field by the + button. The destination IP address information should be entered into the Subnet / IP Address, Subnet Mask, and Gateway fields. Re-addressing can only be performed on machines with VMware Tools installed prior to executing the backup job that is to be restored.

          IP reconfiguration is skipped for virtual machines if a static IP is used but no suitable subnet mapping is found, or if the source virtual machine is powered off and there is more than one associated NIC. In a Windows environment, if a virtual machine uses DHCP only, then IP reconfiguration is skipped for that virtual machine. In a Linux environment, all addresses are assumed to be static, and only IP mapping will be available.

7. On the Restore methods, select the restore method to be used for source selections. Set the Hyper-V restore job to run in test, production, or clone mode by default. After the job is created, you can run the job in production or clone mode by using the Job Sessions pane. You can also change the name of the restored VM by entering the new VM name in the Rename VM (optional) field. Click Next to continue.
8. Optional: On the Job Options (optional) page, configure advanced options and click Next.

   Make IA clone resource permanent

   Enable this option to move the virtual disk to permanent storage and clean up temporary resources. This action is accomplished by starting a vMotion operation for the resources in the background. The destination of the vMotion operation is the VM Configuration Datastore. The Instant Access disk is still available for read/write operations during this operation.

   Power on after recovery

   Toggle the power state of a virtual machine after a recovery is run. Virtual machines are powered on in the order in which they are recovered, as set in the Source step.

   Restriction: Restored virtual machine templates cannot be powered on after recovery.

   Overwrite virtual machine

   Enable this option to allow the restore job to overwrite the selected virtual machine. By default, this option is disabled.

   Continue with restore even if it fails

   Toggle the recovery of a resource in a series if the previous resource recovery fails. If disabled, the restore job stops if the recovery of a resource fails.

   Run cleanup immediately on job failure

   Enable this option to automatically clean up allocated resources as part of a restore job if the virtual machine recovery fails.

   Allow to overwrite and force cleanup of pending old sessions

   Enable this option to allow a scheduled session of a recovery job to force an existing pending session to clean up associated resources so the new session can run. Disable this option to keep an existing test environment running without being cleaned up.

   Append suffix to virtual machine name

   Enter a suffix to add to the names of restored virtual machines.

   Prepend prefix to virtual machine name

   Enter a prefix to add to the names of restored virtual machines. Click Save to save the policy options.

9. Optional: On the Apply scripts page, choose the following script options and click Next.
   • Select Pre-script to select an uploaded script, and an application or script server where the prescript runs. To select an application server where the script will run, clear the Use Script Server check box. Go to the System Configuration > Script page to configure scripts and script servers.
   • Select Post-script to select an uploaded script and an application or script server where the postscript runs. To select an application server where the script runs, clear the Use Script Server check box. Navigate to the System Configuration > Script page to configure scripts and script servers.
   • Select Continue job/task on script error to continue running the job when the script that is associated with the job fails. When this option is enabled and the prescript completes with a nonzero return code, the backup or restore job continues to run and the prescript task status returns COMPLETED. If a postscript completes with a nonzero return code, the postscript task status returns COMPLETED. When this option is not selected, the backup or restore job does not run, and the prescript or postscript task status returns with a FAILED status.
10. Take one of the following actions on the Schedule page:
    • To run an on-demand job, click Next.
    • To set up a recurring job, enter a name for the job schedule, and specify how often and when to start the restore job. Click Next.
11. On the Review page, review your restore job settings and click Submit to create the job.

    On-demand jobs will begin immediately; recurring jobs will begin at the scheduled start time.