During a backup, the plug-in reports an error and stops responding.
The plug-in fails with the following error in the NetVault Backup logs:
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 problem, navigate to the /usr/lib directory, and create the following symbolic link:
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 Backup 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 problem, do either of the following:
• |
Ensure that no snapshots exist on the virtual machine before selecting the Enable Changed Block Tracking for VM 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. |
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:
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.
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.
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center