Configuring backup and restore of virtual machines with VVols is the same as for virtual machines without VVols, with these exceptions:

• To restore a virtual machine with the hotadd transport mode: VMware requires that the virtual machine and the restore host virtual machine reside on the same VVol datastore. Otherwise, the restore must use a different transport mode (not hotadd).

• For a restore to standard (non-VVol) datastores, the NetBackup job creates a vSphere snapshot of the virtual machine while NetBackup restores the data. Note: For a restore to a VVol datastore, NetBackup restores the data to the virtual machine without creating a vSphere snapshot.

• For additional notes on NetBackup support for vSphere 6.0, see the following Veritas document:

  Support for NetBackup in virtual environments

When troubleshooting backups of virtual machines on VVols, note the following:

• Each NetBackup snapshot job creates a vSphere snapshot of the virtual machine. Licensing requirements for vSphere snapshots vary from one type of VVol storage to another, depending on the array vendor. Ensure that you have the required snapshot license from the array vendor; otherwise, snapshot creation may fail.

• To investigate snapshot failures, check the storage array's VASA provider logs as well as the vSphere error messages. (VASA is vSphere API for Storage Awareness.)

• If the vSphere snapshot fails because of insufficient space in VVol storage, consult the storage array documentation. Space requirements vary from one array vendor to another.

For information on VVols, see the following VMware documentation:

• Virtual Volumes

• The VMware guide vSphere Storage ESXi 6.0

• The VMware vSphere 6.0 Documentation Center