Veritas NetBackup™ Logging Reference Guide
- Using logs
- About logs
- About UNIX system logs
- About log retention in NetBackup
- About limiting the size of unified and legacy logs
- About unified logging
- Gathering unified logs for NetBackup
- Types of unified logging messages
- File name format for unified logging
- Originator IDs for the entities that use unified logging
- About changing the location of unified log files
- About rolling over unified log files
- About recycling unified log files
- About using the vxlogview command to view unified logs
- About query strings used with the vxlogview command
- Examples of using vxlogview to view unified logs
- Examples of using vxlogmgr to manage unified logs
- Examples of using vxlogcfg to configure unified logs
- About legacy logging
- UNIX client processes that use legacy logging
- PC client processes that use legacy logging
- File name format for legacy logging
- Directory names for legacy debug logs for servers
- Directory names for legacy debug logs for media and device management
- How to control the amount of information written to legacy logging files
- About limiting the size and the retention of legacy logs
- Configuring the legacy log rotation
- About global logging levels
- Setting retention limits for logs on clients
- Logging options with the Windows Event Viewer
- Troubleshooting error messages in the NetBackup Administration Console
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced Backup and Restore Features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- Snapshot technologies
- Locating logs
- acsssi logging
- bpbackup logging
- bpbkar logging
- bpbrm logging
- bpcd logging
- bpcompatd logging
- bpdbm logging
- bpjobd logging
- bprd logging
- bprestore logging
- bptm logging
- daemon logging
- ltid logging
- nbemm logging
- nbjm logging
- nbpem logging
- nbproxy logging
- nbrb logging
- NetBackup web services logging
- NetBackup web server certificate logging
- PBX logging
- reqlib logging
- robots logging
- tar logging
- txxd and txxcd logging
- vnetd logging
- Java-based administration console logging
- About the Java-based administration console logging
- Java-based administration console logging process flow
- Setting up a secure channel between the Java-based administration console and bpjava-*
- Setting up a secure channel between the Java-based administration console and either nbsl or nbvault
- Java-based administration console logging configuration on NetBackup servers and clients
- Java-based remote administration console logging on a Windows computer where NetBackup is not installed
- Configuring and gathering logs when troubleshooting Java GUI issues
- Undo logging
About limiting the size and the retention of legacy logs
Certain NetBackup processes write legacy debug logs. Because legacy debug logs can grow very large, enable them only if unexplained problems exist. Delete the logs and the associated directories when they are no longer needed.
See About log retention in NetBackup.
To limit the time for which NetBackup retains logs, specify the number of days in the field. The default is 28 days. You can specify the number under Host Properties in the Logging dialog box.
Note:
The following properties have been moved from the host properties to the host properties: and . On the properties screen, these properties are referred to as and respectively.
See the NetBackup Administrator's Guide, Volume I for more information about logging properties.
To limit the amount of disk space that the logs consume, use robust logging. Robust logging involves file rotation, like that which is used in unified logging. Robust logging does not apply to media and device management logging.
See About rolling over unified log files.
Specify the maximum size for a log file and the maximum number of log files to keep in a logging directory. When a log file grows to its maximum size, it closes and a new file opens. If the number of log files exceeds the number that is allowed for the directory, the oldest file is deleted.
Logs created by the following NetBackup processes can use log rotation (robust logging):
bpbkar (UNIX/Linux client only)
bpbrm
bpcd
bpdbm
bpdm
bprd
bptm
nbproxy
For the logs that are created by the other NetBackup processes (except media and device management logs), use the property. The property may override the robust file logging settings. If is set to 10 days and robust file logging settings allow more than 10 days, the logs are deleted on day 11.
For media and device management legacy logs, use the DAYS_TO_KEEP_LOGS setting in the vm.conf file to control log file rotation. The default is 30 days. The vm.conf file is located in the following directory:
Windows | install_path\Volmgr\ |
UNIX | /usr/openv/volmgr/ |
To retain logs for 3 days, enter the following in the vm.conf file:
DAYS_TO_KEEP_LOGS = 3
See the NetBackup Administrator's Guide, Volume II for instructions about how to use this entry.