Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for Hyper-V 11.4 - User Guide

Renaming and relocating a VM during image-level restore

The plug-in lets you restore a VM to a different name and location. The renaming of a VM can be useful if you do not want to overwrite the existing version.

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
With the VM selected on the Create Selection Set page, select Rename from the Actions list.
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.

Restoring data to an alternate Hyper-V Server

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
To save the settings, click Ok, and then click Next.
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
Click Save or Save & Submit, whichever is applicable.
You can monitor progress on the Job Status page and view the logs on the View Logs page. For more information, see the Quest NetVault Backup Administrator’s Guide.

Troubleshooting

NetVault Backup 10.x service, netvault-pgsql, does not start on Windows

To see if the following message is displayed, check the Windows Event Viewer: PDT FATAL: lock file “postmaster.pid” already exists.

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.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione