Chat now with support
Chat mit Support

NetVault Plug-in for VMware 11.4.5 - User Guide

Introducing NetVault Backup Plug-in for VMware Installing the plug-in Configuring the plug-in Defining a backup strategy Using the image-level backup method Using the file-level backup method Restoring image-level backups Restoring file-level backups Troubleshooting

Crash occurs during a backup

Description

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

Symptom

The plug-in fails with the following error in the NetVault Backup 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.

Solution

To correct this problem, 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

Description

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

Symptom

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

Failed to get changed disk areas.

Solution

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 problem, do either of the following:

•
Ensure that no snapshots exist on the virtual machine before selecting the Enable Change Block Tracking for VM check box.
— or —
•
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

Description

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.

Symptom

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.

Solution

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

Description

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. The HotAdd transport mode does not work if either the backup proxy or the backup target uses Paravirtual SCSI controller.

Symptom

N/A

Solution

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.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen