Chat now with support
Chat mit Support

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

Introducing NetVault Backup Plug-in for Hyper-V Installing or removing the plug-in Configuring the plug-in Backing up data Restoring data Troubleshooting

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.

1
Verify that the following requirements are met on the new restore target before continuing this process.
•
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.
3
Select the VM to be restored from the backup saveset.
4
On the Create Selection Set page, click Edit Plugin Options, and select the Recover entire VM to host and/or cluster option.
For information about other options available, see Setting image-level restore options.
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.
Assign a descriptive name that lets you easily identify the job when monitoring its progress. The job name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Windows, there is no length restriction; however, a maximum of 40 characters is recommended.
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.
10
After the restore is finished, use Hyper-V Manager to import the new VM.
 

Troubleshooting

•
NetVault Backup 10.x service, netvault-pgsql, does not start on Windows
•
Backup job fails while using VSS snapshot

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.

Backup job fails while using VSS snapshot

If a backup job is stopped or fails while a VSS snapshot is being used, the plug-in might not clean up the VSS snapshot. If this issue occurs, you can use a tool such as Microsoft CLI diskshadow.exe to remove the snapshot.

1
After DiskShadow is run from a command line with elevated permissions, run the following command at the DISKSHADOW> prompt to find and remove the orphaned shadow copy.
list shadows all
The preceding command lists the current shadow copies.
2
Look through the list of shadow copies noting the Exposed Locally as field.
3
Find the field with the exposed directory name that matches the VM name used during the stopped or failed job.
4
Using the Shadow copy ID field from that entry, run the following command:
delete shadows ID <ShadowCopyIDofAbortedOrFailedJob>
5
Navigate to <installationDirectory>\tmp\Hyper-V, and delete the directory with the VM name used during the stopped or failed job.
6
Exit DiskShadow and return to a standard command prompt.
7
To verify that all VSS Writers, especially Hyper-V VSS Writer, are in a Stable State, run the following command:
vssadmin list writers
The preceding command lists the VSS Writers and their State.
8
If a VSS Writer is listed in a State other than Stable, use Hyper-V Manager to select the host node, and stop and start the Virtual Machine Manager service.

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen