Veritas NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Notes and prerequisites
- Configure NetBackup communication with VMware
- Adding NetBackup credentials for VMware
- Validating VMware virtualization server certificates in NetBackup
- 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)
Preventing browsing delays caused by DNS problems
This topic applies to NetBackup for VMware.
NetBackup may be unable to identify virtual machines when you use the Browse for Virtual Machines dialog. Virtual machine host names may not be properly configured in your Domain Name Server system (DNS), or the DNS system may be slow. A timeout message may appear, or messages similar to the following may appear in the NetBackup detailed status log:
17:25:37.319 [12452.10360] get_vSphere_VMs: Processing vm 002-wcms 17:25:37.319 [12452.10360] get_vSphere_VMs: uuid 421a8b46-063d-f4bd-e674-9ad3707ee036 17:25:37.319 [12452.10360] get_vSphere_VMs: vmxdir [san-05] 002-wcms/ 17:25:37.319 [12452.10360] get_vSphere_VMs: datastore san-05 17:25:37.319 [12452.10360] get_vSphere_VMs: IpAddress 172.15.6.133 17:25:41.866 [12452.10360] get_vSphere_VMs: retry_gethostbyaddr for 172.15.6.133 failed with The requested name is valid, but no data of the requested type was found.
Note:
NetBackup may be unable to determine the host names of the virtual machines from their IP addresses (reverse lookup may fail).
To prevent browsing delays caused by DNS problems (Windows)
- On the Windows desktop of the backup host, click Start > Run and enter regedit.
- To be on the safe side, make a backup of the current registry (File > Export).
- Go to HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion > Config and create a key that is called BACKUP.
- Create a new DWORD under BACKUP, called disableIPResolution.
This registry key causes NetBackup to use the virtual machine's IP address as the virtual machine's host name.
- Use the NetBackup Browse for Virtual Machines screen to rediscover the virtual machines. The host names should now be the IP addresses.
To prevent browsing delays caused by DNS problems (Linux)
- On the Linux backup host, create (or open) the following file:
/usr/openv/netbackup/virtualization.conf
- Add the following to the file:
[BACKUP] "disableIPResolution"=dword:00000000
This entry causes NetBackup to use the virtual machine's IP address as the virtual machine's host name.
Note: If the file already contains a [BACKUP] line, do not add another [BACKUP] line. Any other lines that already exist under [BACKUP] should remain as they are.
- Use the NetBackup Browse for Virtual Machines screen to rediscover the virtual machines. The host names should now be the IP addresses.
More Information