Veritas NetBackup™ for Hyper-V Administrator's Guide
- Notes and prerequisites
- Configure NetBackup communication with Hyper-V
- Configure NetBackup policies for Hyper-V
- Backup options on the Hyper-V tab
- Hyper-V - Advanced Attributes
- Browse for Hyper-V virtual machines
- Configure Hyper-V Intelligent Policies
- NetBackup Hyper-V for SCVMM
- Windows Server failover cluster support
- Virtual machine maintenance after a restore
- Back up and restore Hyper-V
- Restoring individual files to a shared location on the virtual machine
- Use Accelerator to back up Hyper-V
- Best practices and more information
- NetBackup logs for Hyper-V and how to create them
- Errors during policy creation
- NetBackup status codes related to Hyper-V
- Appendix A. VSS backup method: Hyper-V online and offline backups
- Appendix B. Hyper-V pass-through disks
- Appendix C. NetBackup commands to back up and restore Hyper-V virtual machines
- Examples of nbrestorevm for restoring VMs to Hyper-V
Linux VMs and persistent device naming
For Linux VMs without persistent device naming, multiple disk controllers (such as IDE, SCSI, and SATA) may complicate the recovery of individual files. This issue occurs because non-persistent device naming, such as /dev/sda and /dev/sdb, may cause unexpected mount point changes after a restart. If the VM has a SCSI disk and SATA disk, the Backup, Archive, and Restore interface may show incorrect mount points for the VM's files. For example, the files originally under /vol_a might appear under /vol_b when you browse to restore them. The restore is successful, but the restored files may not be in their original directories.
As a workaround, search for the files on the restored VM and move them to the proper locations.
To prevent this issue on Linux VMs with multiple disk controllers, Veritas recommends a persistent device-naming method for mounting the file systems. When persistent naming is in place, device mounting is consistent and this issue does not occur when you restore files from future backups.
For persistent device naming, you can mount devices by UUIDs. The following is an example of the
/etc/fstab file that contains the devices that are mounted by UUIDs:
UUID=93a21fe4-4c55-4e5a-8124-1e2e1460fece /boot ext4 defaults 1 2 UUID=55a24fe3-4c55-4e6a-8124-1e2e1460fadf /vola ext3 defaults 0 0
To find the device UUIDs, you can use either of the following commands:
ls -l /dev/disk/by-uuid/
NetBackup also supports the by-LABEL method for persistent device naming.