Chatee ahora con Soporte
Chat con el soporte

NetVault Plug-in for VMware 12.0 - 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

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.

File-level backups do not back up data for a reparse point

Description

The file-level backup method does not back up data through a reparse point.

Symptom

When a disk mounted as a reparse point on a Guest OS is included in a file-level backup, the backup completes without any errors or warnings. However, the plug-in does not back up any data for a reparse point. It is listed as an empty node on the Create Selection Set page.

Solution

The VMware API does not support this type of backup.

Workaround:

•
Install NetVault Backup Client on the Guest OS, and perform a backup using the Plug-in for FileSystem to include the reparse point directory.
— or —
•
Mount the disk as drive letter instead of a reparse point. Then, create a backup job to include the new drive letter.

Restore job fails when using SAN transport

Description

Restore job fails.

Symptom

A restore job fails with the following error:

Log Message:

Failed to restore VM disk data.

Log Context:

Failed to open vmdk VDDK error encountered: code 13

Retrieving error message text VDDK error message is ‘You do not have access rights to this file’

Disk data restore failed for ‘[datastore]VirtualMachineName/ VitrualDiskName.vmdk’

Solution

The NetVault Backup Client running the Plug‑in for VMware may not have access to the SAN. To verify, try using the NBD transport mode. If restore completes successfully with this mode, it indicates SAN connectivity issues.

To use the SAN transport mode, the NetVault Backup Client must have SAN connectivity to the VMFS LUN. Ensure that the LUN is accessible and the SAN is configured correctly.

Restore job fails to add a virtual machine to the server inventory

Description

Restore job fails.

Symptom

A restore job fails with the following error:

Log message:

Failed to add VM to target server's inventory.

Log context:

Fault string is 'Invalid configuration for device '3'.

Solution

When this error occurs, enable trace and run the restore job again. When the job completes, open the file named vmw<nnn>_soaprecv.log, and check if it contains an XML message <WaitForUpdatesExResponse> with contents similar to the following:

<val xsi:type="LocalizedMethodFault">
<fault xsi:type="InvalidDeviceSpec">
<property>deviceChange[3].device.backing.fileName
</property>
<deviceIndex>3</deviceIndex>
</fault>
<localizedMessage>Invalid configuration for device &apos;3&apos;.</localizedMessage>
</val>

If so, it indicates that the backup contains an invalid configuration for a CD or DVD drive.

To correct this problem:

1
Open the file vmware.cfg in a text editor.
You can find this file in <NetVault Backup home>\config on Windows and <NetVault Backup home>/config on Linux.
2
Set the value for the following entry to True:
[Custom:ReconfigureVirtualCdromDevices]
Value=True
(The default value for this entry is False.)
3
Save the file.
4
Run the restore job again.
The job completes successfully. If a CD or DVD drive was set to “Host Device” or “Datastore ISO File” type during the original backup, it is reconfigured as “Client Device” type. A warning message in the logs provides a list of reconfigured devices. The log context includes their original configuration. To view the log context, click the More Info button.
5
After restoring the virtual machine, reset [Custom:ReconfigureVirtual CdromDevices] to False.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación