The following notes apply to virtual machines with Linux guest operating systems:
NetBackup cannot exclude unused or deleted blocks from the backup if the virtual machine is configured with software RAID volumes. The policy'soption is not supported.
On Linux virtual machines, NetBackup requires a special utility (SYMCquiesce) to quiesce the file system in preparation for taking the snapshot. Without SYMCquiesce, NetBackup cannot guarantee that data in the file system is in a consistent state when the snapshot occurs.
For the Linux virtual machines that do not have the SYMCquiesce utility: To guarantee that the file system is consistent at the time of backup, consider turning off the virtual machine before the backup. When the virtual machine is turned off, data buffers are flushed to disk and the file system is consistent.
For a description of file system quiesce, see the NetBackup Snapshot Client Administrator's Guide.
If the Linux file system was not quiesced before the snapshot, some files may be inconsistent. Such files can be recovered from the NetBackup.lost+found directory.
Unmounted LVM2 volumes must start with /dev
If the path of an unmounted LVM2 volume does not start with /dev, the backup of the virtual machine fails. Note: The path of the volume is set with the "dir" parameter on the LVM volume configuration file. An example of this configuration file is /etc/lvm/lvm.conf.
For Linux files or directories, NetBackup for VMware has the same path name restriction as NetBackup on a Linux physical host. Files or directories with path names longer than 1023 characters cannot be individually backed up or restored. Such files can be restored when you restore the entire virtual machine from a full virtual machine backup.
The Linux ext4 file system includes a persistent pre-allocation feature, to guarantee disk space for files without padding the allocated space with zeros. When NetBackup restores a pre-allocated file (to any supported ext file system), the file loses its preallocation and is restored as a sparse file. The restored file is only as large as the last byte that was written to the original file. Subsequent writes to the restored file may be non-contiguous.
The restored file contains all of its original data.