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.
Before you begin
- Ensure that a Hyper-V backup job was run at least once. For instructions, see Backing up Hyper-V data.
- Ensure that the destination that you plan to use for the restore job is registered in IBM Spectrum® Protect Plus. This requirement applies to restore jobs that restore data to original hosts or clusters.
- Ensure that the latest Hyper-V integration services are installed.
For Microsoft Windows environments, see Supported Windows guest operating systems for Hyper-V on Windows Server.
For Linux® environments, see Supported Linux and FreeBSD virtual machines for Hyper-V on Windows.
- Ensure that the appropriate roles for restore operations are assigned to the affected users. Grant users access to hypervisors and backup and restore operations in the Accounts pane. Roles and associated permissions are assigned during user account creation. For instructions, see Managing user access and Managing user accounts.
- Windows file indexing and file restore on volumes residing on dynamic disks is not supported.
- When restoring from a IBM Spectrum Protect archive, files will be migrated to a staging pool from the tape prior to the job beginning. Depending on the size of the restore, this process could take several hours.
- When restoring a virtual machine by using clone mode and by using the original IP configuration, ensure that credentials are established through the Guest OS Username and Guest OS Password options within the backup job definition.
About this task
If a Virtual Hard Disk (VHDX) is selected for a restore job, 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 the snapshot can be accessed or copied as required. All other sources are restored by using Instant VM restore jobs, which can be run in the following modes:
- Production mode
- Production mode enables disaster recovery at the local site from primary storage or a remote disaster recovery site, replacing original machine images with recovery images. All configurations are carried over as part of the recovery, including names and identifiers, and all copy data jobs that are associated with the virtual machine continue to run.
- Test mode
- 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 while they are needed to complete testing and verification and are then cleaned up. Through fenced networking, you can establish a safe environment to test your jobs without interfering with virtual machines that are used for production. Virtual machines that are created in test mode are also given unique names and identifiers to avoid conflicts within your production environment.
- Clone mode
- Clone mode creates copies of virtual machines for use cases that require permanent or long-running copies for data mining or duplication of a test environment in a fenced network. Virtual machines that are created in 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 because clone mode creates permanent or long-term virtual machines.
Procedure
To define a Hyper-V restore job, complete the following steps:
What to do next
After the job is complete, select one of the following options from the Actions menu on the Jobs Sessions or Active Clones sections on the Restore pane:
- Cleanup
- Destroys the virtual machine and cleans up all associated resources. Because this is a temporary virtual machine to be used for testing, all data is lost when the virtual machine is destroyed.
- Clone (migrate)
- Migrates the virtual machine to the datastore and virtual network that are defined as the test network.