Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
NetBackup™ for KVM Administrator's Guide
- Introduction
- Installation and configuration overview
- Managing KVM hosts
- Configuring RBAC roles for KVM administrators
- Protecting KVM virtual machines
- About configuring a backup policy for KVM
- About automatic virtual machine selection
- Add a policy for KVM
- About policy attributes
- Schedule properties
- Add KVM hosts to a policy
- Configure a query to select KVM virtual machines for backup
- Backup options on the KVM attributes tab
- View the protection status of KVM virtual machines
- Perform a manual backup
- Recovering KVM virtual machines
- Troubleshooting KVM backups and recovery
Configuring VxMS logging
The following procedures describe how to configure VxMS logging for NetBackup.
To configure VxMS logging on a Linux backup host
- Create the VxMS log directory:
/usr/openv/netbackup/logs/vxmsNote: 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.conffile: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.conffile:vxmslogdir=path to new log locationNote: 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\vxmsNote: 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_VERBOSEin the following location:HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion > Config
- To configure the logging level, set the numeric value of
VXMS_VERBOSEto 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
vxmslogdirwith 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. |