Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

NetVault Plug-in for VMware 13.1.1 - User Guide

Table of Contents

Introducing NetVault Plug-in for VMware

About NetVault Plug-in for VMware

Key benefits Feature summary

Target audience Recommended additional reading

Installing the plug-in

About plug-in editions Deployment overview Prerequisites Installing the plug-in Removing the plug-in

Configuring the plug-in

Adding a server Reconfiguring a server Removing a server Supported transport modes Configuring default settings Enabling or disabling CBT on virtual machines

About CBT Enabling CBT on individual virtual machines Disabling CBT on a virtual machine Manually disabling CBT on a virtual machine

Enabling or disabling quiescing of virtual machines

About quiescing virtual machines Enabling quiescing of virtual machines Disabling quiescing of virtual machines Removing backup preferences for a virtual machine

Unlocking a virtual machine

Defining a backup strategy

About backup methods and types Data backed up and restored for different disk types

RDM disks

Backup and recovery strategy

Using the image-level backup method

Adding patterns to use for inclusion and exclusion of virtual machines Understanding the Distributed Jobs feature Performing image-level backups Continuous data protection backups

Prerequisite

Performing continuous backups

Continuous data protection and Plug-in for Data Copy Additional notes Backup selection tree icons

Restarting a backup job Resetting CBT on a virtual machine Monitoring job progress

Using the file-level backup method

Performing file-level backups Performing file-level continuous backups

Backup selection tree icons

Removing the snapshot and mount folder manually

Restoring image-level backups

About restoring image-level backups Restoring a full virtual machine or individual virtual drives

Prerequisites Restoring data

Important notes Restore selection tree icons

Starting a virtual machine

Relocating a virtual machine to an alternate ESXi Server Restoring a virtual machine to an alternate vCenter Server Renaming a virtual machine during restore Performing file-level restores from image-level backups

Restore selection tree icons

Recovering a virtual machine using Instant Restore Restoring virtual machine disk and configuration files

Restore selection tree icons

Restore selection tree icons

Recovering a virtual machine from the restored files

Searching for files in savesets Viewing media list

Restoring file-level backups

About restoring file-level backups Restoring file-level backups using shared network drives

Setting up a network share Restoring data

Restoring file-level backups using the built-in Plug-in for FileSystem

Prerequisites Restoring data

Searching for files in savesets Viewing media list

Troubleshooting

NetVault Service fails to start on Windows NetVault Service fails to start after the machine is restarted NetVault Service starts, but stops immediately on Linux Linux Hybrid version of the plug-in does not run on 64-bit OS Crash occurs during a backup CBT-based image-level backup fails SAN transport reports errors when multiple backups access the same datastore Default SCSI controller type on RHEL 7 and RHEL 6 File-level backups do not back up data for a reparse point Restore job fails when using SAN transport Restore job fails to add a virtual machine to the server inventory or to the alternate standalone ESXi Server Disk type is always Thick Provision Eager Zeroed after restoring an image-level backup Backup jobs of virtual machines protected by vSphere FT fail intermittently RDM disks are restored to VMDK files Unable to consolidate image-level backups Restore job fails on Linux when file size exceeds 50 MB Web Service process displays message that indicates the server is unavailable Installing an update puts the VMware Vstor2 MntApi driver into an inconsistent state Backing up and restoring encrypted disks Backing up a cloned virtual machine that has the same UUID Backing up virtual machines that are protected by vSphere FT Error using VVols with a storage array Backup proxy opens in NBD mode instead of HotAdd transport mode

Diagnosing virtual machine issues SOAP messages Generating VDDK logs

Crash occurs during a backup

During a backup, the plug-in reports an error and stops responding.

The plug-in fails with the following error in the NetVault logs:

Backing up data of VM disk [XXXXXXX]xxx/xxxxxxxxx. vmdk' to media : “Job manager lost message channel unexpectedly.”

The trace logs include the following message:

Cannot open library: libexpat.so.0: cannot open shared object file in vixDiskLib-16642.log.

To correct this issue, navigate to the /usr/lib directory, and create the following symbolic link:

ln -s /lib/libexpat.so.1.5.2 libexpat.so.0

CBT-based image-level backup fails

An image-level backup for which CBT has been enabled reports an error and fails.

The job fails with the following error in the NetVault logs:

Failed to get changed disk areas.

This issue occurs when a snapshot exists on a virtual machine when CBT is enabled. For snapshots that exist before enabling CBT, the changeId parameter is not set. So, when the QueryChangedDiskAreas API is invoked, it returns an error. For more information, see http://kb.vmware.com/kb/1033816.

To correct this issue, do either of the following:

•

Ensure that no snapshots exist on the virtual machine before selecting the Enable Change Block Tracking for virtual machine check box.

•

Use the Reset Change Block Tracking option. This option reconfigures CBT on a virtual machine and allows you to run CBT-enabled backup that failed previously. For more information about this option, see Resetting CBT on a virtual machine.

SAN transport reports errors when multiple backups access the same datastore

A Linux-based client may fail to read the contents of a virtual drive using the SAN transport mode if multiple backup processes are accessing the same datastore.

During a backup using the SAN transport mode, the following errors are reported:

San transport error: I/O Operation failed.

Error: One of the parameters supplied is invalid.

These errors are caused by a fault in the Linux kernel when handling SCSI reservation conflicts.

The errors are encountered on the following systems:

•

Red Hat Enterprise Linux (RHEL) 6.1 and earlier versions

•

SUSE Linux Enterprise Server (SLES) 11.1 and earlier versions

To correct this issue, upgrade to kernel version 2.6.32-220 or later on RHEL and kernel version 3.0.13 or later on SLES.

Default SCSI controller type on RHEL 7 and RHEL 6

When you create a virtual machine with RHEL 7 or RHEL 6 as the Guest OS, the SCSI controller type is set to VMware Paravirtual by default.

To use HotAdd transport mode, set the SCSI controller type to LSI Logic Parallel or LSI Logic SAS when you create the virtual machine. For more information about configuring this setting, see the relevant VMware documentation.

Quest does not recommend changing the SCSI controller type for an existing virtual machine without testing to ensure that it operates normally with the new controller type.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center