IMPORTANT: If your environment uses Windows Server 2008 R2 and you use the Rename feature, the recovery does not include network adapters that the VM backup included. |
1 |
In the Navigation pane, click Create Restore Job, select Plug‑in for Hyper‑V from the Plugin Type list, select the applicable saveset, and click Next. |
2 |
On the Create Selection Set page, select the localhost or <clusterName> node to display the VMs, and then select the VM to restore. |
3 |
4 |
In the Rename/Relocate dialog box, complete both fields (required): |
• |
Rename: Enter the new name. |
• |
Relocate: Enter the new full path. If you are recovering clustered VMs, verify that the path is part of the cluster. |
This functionality is useful during disaster recovery operations. You can restore a VM to a different Hyper-V Server by using the steps provided in the following topic.
• |
Same version of Hyper-V Server installed: The Hyper-V Server version must be the same as the version running on the existing server. |
• |
NetVault Backup software and the Plug‑in for Hyper‑V installed: The same version of NetVault Backup software and the plug-in must be installed and configured on the new restore target. |
• |
Client added to the NetVault Backup Server: The target machine must be added to the NetVault Backup Server by using the Manage Clients page of the NetVault Backup WebUI. |
2 |
In the Navigation pane, click Create Restore Job, select Plug‑in for Hyper‑V from the Plugin Type list, select the applicable saveset, and click Next. |
4 |
On the Create Selection Set page, click Edit Plugin Options, and select the Recover entire VM to host and/or cluster option. |
5 |
6 |
In Job Name, specify a name for the job if you do not want to use the default setting. |
7 |
In the Target Client list, select the alternate Hyper-V Server. |
8 |
Use the Schedule, Source Options, and Advanced Options lists to configure any additional required options. |
9 |
NetVault Backup 10.x uses a PostgreSQL database. If the PostgreSQL database does not start, NetVault Backup cannot start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server. For more information, see https://support.questcom/netvault-backup/kb/122475.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center