Create a Hyper-V Restore Job Definition

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

If a VHDX is selected for restore, IBM Spectrum Protect Plus automatically presents options for an Instant Disk Restore job, which provides instant writable access to data and application restore points. An IBM Spectrum Protect Plus snapshot is mapped to a target server where it can be accessed or copied.

All other sources are restored through Instant VM Restore jobs, which can be run in the following modes:

Test Mode creates temporary virtual machines for development/testing, snapshot verification, and disaster recovery verification on a scheduled, repeatable basis without affecting production environments. Test machines are kept running as long as needed to complete testing and verification and are then cleaned up after testing and verification completes. Through fenced networking, you can establish a safe environment to test your jobs without interfering with virtual machines used for production. Virtual machines created through Test mode are also given unique names and identifiers to avoid conflicts within your production environment.

Clone Mode creates copies of virtual machines for use cases requiring permanent or long-running copies for data mining or duplication of a test environment in a fenced network. Virtual machines created through Clone mode are also given unique names and identifiers to avoid conflicts within your production environment. With clone mode you must be sensitive to resource consumption, since clone mode creates permanent or long-term virtual machines.

Production Mode enables disaster recovery at the local site from primary storage or a remote disaster recovery site, replacing original machine images with restore images. All configurations are carried over as part of the recovery, including names and identifiers, and all copy data jobs associated with the virtual machine continue to run.

Note: Moving from Test Mode to Production Mode is not supported for Hyper-V.

BEFORE YOU BEGIN:

CONSIDERATIONS:

  • When selecting a destination for a Restore job definition, note that the destination must be registered in IBM Spectrum Protect Plus. This includes Restore jobs that restore data to original hosts or clusters.

To create a Hyper-V Restore job definition:

  1. From the navigation menu, expand Manage Protection, then expand Hypervisors. Expand Hyper-V, then click Restore.
  2. In the Restore pane, review the available restore points of your Hyper-V sources, including virtual machines, VM templates, datastores, folders, and vApps. Use the search function and filters to fine-tune your selection across specific recovery site types. Expand an entry in the Restore pane to view individual restore points by date.
  3. To select the latest restore point, click Add to Restore List Add to Restore List icon at the resource level. Then, from the Select a site drop-down menu, select the site associated with the backup storage server you want to recover from. To restore a specific restore point from a specific site, expand a resource in the Restore pane, then click the Add to Restore List Add to Restore List icon icon associated with the restore point. Note that adding a combination of latest restore points and specific restore points to the Restore List is not supported. Click the Remove Remove icon icon to remove restore points from the Restore List.
  4. To run the job now using default options, click Restore. To schedule the job to run using default options, click Manage Jobs and define a trigger for the job definition.
  5. To edit options before creating the job definition, click Options. Set the job definition options.
  6. Destination
  7. Set the Hyper-V destination.
  8. Original Hyper-V Host or Cluster - Select to restore to the original host or cluster.
  9. Alternate Hyper-V Host or Cluster - Select to restore to a local destination different from the original host or cluster, then select the alternate location from available resources.
  10. Restore Type
  11. Set the Hyper-V Restore job to run in Test, Production, or Clone mode by default. Once the job is created, it can be run in Test, Production, or Clone mode through the Job Sessions pane.
  12. Network Settings
  13. Set the network settings for a restore to an alternate Hyper-V host or cluster:
  14. From the Production and Test fields, set virtual networks for production and test restore job runs. Destination network settings for production and test environments should be different locations to create a fenced network, which keeps virtual machines used for testing from interfering with virtual machines used for production. The networks associated with Test and Production will be utilized when the restore job is run in the associated mode.
  15. Set an IP address or subnet mask for virtual machines to be re-purposed for development/testing or disaster recovery use cases. Supported mapping types include IP to IP, IP to DHCP, and subnet to subnet. Virtual machines containing multiple NICs are supported.
  16. Destination Datastore
  17. Set the destination datastore for a restore to an alternate Hyper-V host or cluster.
  18. Pre-scripts and Post-Scripts
  19. In the Pre-Script and/or Post-Script section, select an uploaded script and a script server where the script will run. Scripts and script servers are configured through the Jobs and Monitoring > Script pane. See Configure Scripts.
  20. Pre-scripts and post-scripts are scripts that can be run before or after a job runs at the job-level. Windows-based machines support Batch and PowerShell scripts while Linux-based machines support shell scripts.
  21. Continue job/task on script error - When enabled, if a Pre-script completes with a non-zero return code, the backup or restore is attempted and the Pre-script task status returns COMPLETED. When disabled, the backup or restore is not attempted, and the Pre-script task status returns FAILED. If a Post-script completes with a non-zero return code, the Post-script task status returns COMPLETED. When disabled, the Post-script task status returns FAILED.
  22. Advanced Options
  23. Set the advanced job definition options:
  24. Power on after recovery - Toggle the power state of a virtual machine after a recovery is performed. Virtual machines are powered on in the order they are recovered, as set in the Source step. Note that restored VM templates cannot be powered on after recovery.
  25. Overwrite virtual machine - Enable to allow the restore job to overwrite the selected virtual machine. By default this option is disabled.
  26. 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.
  27. Run cleanup immediately on job failure - Enable to automatically clean up allocated resources as part of a restore if the virtual machine recovery fails.
  28. Allow to overwrite and force clean up 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.
  29. Click Save to save the policy options.
  30. To run the job now, click Restore. To schedule the job click Manage Jobs and define a trigger for the job definition.
  31. Once the job completes successfully, select one of the following options from the Actions menu on the Jobs Sessions or Active Clones sections on the Restore pane: 
  32. Cleanup destroys the virtual machine and cleans up all associated resources. Since this is a temporary/testing virtual machine, all data is lost when the virtual machine is destroyed.
  33. Clone (migrate) migrates the virtual machine to the Datastore and Virtual Network defined as the "Test" network.

 


IBM Spectrum Protect Plus 10.1.2

Licensed Material - Property of IBM Corp. © IBM Corporation and other(s) 2018. IBM is a registered trademark of the IBM Corporation in the United States, other countries, or both. | 8/23/2018