Veritas NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Notes and prerequisites
- Configure NetBackup communication with VMware
- Adding NetBackup credentials for VMware
- Configure NetBackup policies for VMware
- VMware backup options
- Exclude Disks tab
- Configure a VMware Intelligent Policy
- Reduce the size of backups
- Back up virtual machines
- Use Accelerator to back up virtual machines
- Restore virtual machines
- Restoring the full VMware virtual machine
- Virtual Machine Recovery dialog boxes (restore to original location)
- Virtual Machine Recovery dialogs boxes (restore to alternate location)
- Restoring VMware virtual machine disks by using Backup, Archive, and Restore
- Restoring VMware virtual machine disks by using NetBackup commands
- Restoring individual VMware virtual machine files
- Browse and search virtual machines for restore
- Restore virtual machines with Instant Recovery
- Use NetBackup for vCloud Director
- Virtual machine recovery dialog boxes for vCloud Director
- Best practices and more information
- Troubleshooting
- Appendix A. NetBackup commands to back up and restore virtual machines
- Using NetBackup commands to create a VMware policy
- Appendix B. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- About configuring services for NFS on Windows 2008 and 2008 R2 (NetBackup for VMware)
- Appendix C. The Reuse VM selection query results option
- Appendix D. Backup of VMware raw devices (RDM)
Simultaneous hotadd backups (from the same VMware backup host) fail with status 13
During simultaneous backups from the same VMware backup host, some of the backups may fail with status 13, "file read failed." A hotadd backup of multiple disks may take more time than the client-read timeout allows (the default is 300 seconds). The delay may be caused by locking timeouts in the VMware VDDK.
In the NetBackup Activity Monitor, the detailed status log may include messages similar to the following:
12/05/2014 06:43:53 - begin writing 12/05/2014 06:48:53 - Error bpbrm (pid=2605) socket read failed: errno = 62 - Timer expired 12/05/2014 06:48:55 - Error bptm (pid=2654) media manager terminated by parent process
The /NetBackup/logs/vxms
log may include repeated instances of a VDDK message similar to the following:
12/08/2014 05:11:35 : g_vixInterfaceLogger:libvix.cpp:1844 <DEBUG> : [VFM_ESINFO] 2014-12-08T05:11:35.146-06:00 [7F1B1163F700 info Libs'] FILE: FileLockWaitForPossession timeout on '/var/log/vmware/hotAddLock. dat.lck/M34709.lck' due to a local process '15882-26732358(bpbkarv)'
To prevent this issue, do one of the following:
Reduce the number of hotadd backups that run simultaneously.
Increase the client-read timeout on the media server as appropriate (15 minutes or more):
In the NetBackup Administration Console, click
Double-click on media server .