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)
Configuring VxMS logging
The following procedures describe how to configure VxMS logging for NetBackup.
Except as noted in this topic, you can also use the Logging Assistant (in the NetBackup Administration Console) to configure VxMS logging.
Note:
VxMS logging may require significant resources on the VMware backup host.
To configure VxMS logging on a Linux backup host
- Create the VxMS log directory:
/usr/openv/netbackup/logs/vxms
Note:
For logging to occur, the VxMS directory must exist.
Note:
If you have run the NetBackup mklogdir command, the VxMS log directory already exists.
- Add the following to the
/usr/openv/netbackup/bp.conf
file:VXMS_VERBOSE=<numeric value of 0 or greater>
See Table: VxMS logging levels for the available logging levels.
- To change the log location, enter the following in the
bp.conf
file:vxmslogdir=path to new log location
Note:
If the VxMS log location is changed, the Logging Assistant does not collect the logs.
To configure VxMS logging on a Windows backup host
- Create the VxMS log directory:
install_path\NetBackup\logs\vxms
Note:
For logging to occur, the VxMS folder must exist.
Note:
If you have run the NetBackup mklogdir.bat command, the VxMS log directory already exists.
- In the Windows registry, create the DWORD registry entry
VXMS_VERBOSE
in the following location:HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion > Config
- To configure the logging level, set the numeric value of
VXMS_VERBOSE
to 0 or greater. Larger numbers result in more verbose logs.See Table: VxMS logging levels for the available logging levels.
- To change the log location:
Open regedit and go to the following location:
HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion
Create the registry entry
vxmslogdir
with a string value(REG_SZ)
. For the string value, specify the full path to an existing folder.
Note:
You can use NTFS compression on VxMS log folders to compress the log size. The new logs are written in compressed form only.
Note:
If the VxMS log location is changed, the Logging Assistant does not collect the logs.
Table: VxMS logging levels lists the VxMS logging levels.
Note:
Logging levels higher than 5 cannot be set in the Logging Assistant.
Note:
Logging levels higher than 5 should be used in very unusual cases only. At that level, the log files and metadata dumps may place significant demands on disk space and host performance.
Table: VxMS logging levels
Level | Description |
---|---|
0 | No logging. |
1 | Error logging. |
2 | Level 1 + warning messages. |
3 | Level 2 + informative messages. |
4 | Same as level 3. |
5 | Highly verbose (includes level 1) + auxiliary evidence files (.mmf, .dump, VDDK logs, .xml, .rvpmem). You can set the logging level for the VDDK messages. |
6 | VIX (VMware virtual machine metadata) dumps only. |
7 | VHD (Hyper-V virtual machine metadata) dumps only. |
> 7 | Full verbose + level 5 + level 6 + level 7. |