Chat now with support

Live-Hilfe anfordern
Registrierung abschließen

Anmelden

Preisinformationen anfragen

Vertrieb kontaktieren

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

Inhaltsnavigation

Introducing NetVault Backup Plug-in for Hyper-V

NetVault Backup Plug-in for Hyper-V: at a glance Key benefits Feature summary Target audience Recommended additional reading

Installing or removing the plug-in

Deploying the plug-in Prerequisites for installing the plug-in Prerequisite for using SMB file servers Installing or upgrading the plug-in

Installing the plug-in in a standalone deployment Installing the plug-in in a clustered deployment

Creating a Virtual Client

Licensing the plug-in Removing the plug-in from a standalone deployment

Configuring the plug-in

Configuring settings for a clustered deployment Enabling communication between VMs in clustered environment

Backing up data

Backing up data: an overview Performing backups

Selecting data for a backup Setting backup options Finalizing and submitting the job

Restoring image-level backups

Prerequisites for image-level restore Selecting data for an image-level restore Setting image-level restore options Finalizing and submitting an image-level restore job

Performing file-level recovery

Selecting data for a file-level restore Setting file-level restore options Finalizing and submitting a file-level restore job

Using other restore procedures

Renaming and relocating a VM during image-level restore Restoring data to an alternate Hyper-V Server

Troubleshooting

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

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

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center