Veritas NetBackup™ Logging Reference Guide
- Using logs
- Changing the logging levels
- About unified logging
- About legacy logging
- 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
- NetBackup secure communication logging
- NetBackup proxy helper logging
- NetBackup proxy tunnel logging
- Snapshot technologies
- Locating logs
- NetBackup Administration Console logging
- Using the Logging Assistant
About legacy logging
In NetBackup legacy debug logging, a process creates log files of debug activity in its own logging directory. By default, NetBackup creates only a subset of logging directories, in the following locations:
If any process runs for a non-root or non-admin user and there is no logging happening under legacy log folders, you can create a folder using the mklogdir command for the required user.
To run a command line for a non-root or non-admin user (troubleshooting when the NetBackup services are not running), it is recommended that you create user folders for the specific command line. You can create the folders either using the mklogdir command or manually with the non-root or non-admin user privileges.
To use legacy logging, a log file directory must exist for a process. If the directory is not created by default, you can use the Logging Assistant or the mklogdir batch files to create the directories. Or, you can manually create the directories. When logging is enabled for a process, a log file is created when the process begins. Each log file grows to a certain size before the NetBackup process closes it and creates a new log file.
You can use the following batch files to create all of the log directories:
See the NetBackup Commands Reference Guide for a complete description about the mklogdir command.
See Directory names for legacy debug logs for servers .
See Directory names for legacy debug logs for media and device management.