Veritas NetBackup™ Logging Reference Guide
- Using logs
- About unified logging
- About legacy logging
- About global logging levels
- 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
- Java-based administration console logging
About extra disk space required for logs and temporary files
For successful operation, the NetBackup Administration Console requires extra disk space to store logs and temporary files. The disk space should be available in the following locations.
On the host that is specified in the logon dialog box
In /usr/openv/netbackup/logs/user_ops
On the host where the console was started
In /usr/openv/netbackup/logs/user_ops/nbjlogs
If space is not available in the respective file systems, you can experience the following:
Long waits for application response
Incomplete data
No response during logon
Reduced functionality in the NetBackup interface, for example, only the Backup, Archive, and Restore and Files System Analyzer nodes appear in the tree
Unexpected error messages:
"Cannot connect" socket errors during logon to the NBJava application server
"Unable to log in, status: 35 cannot make required directory"
"/bin/sh: null: not found (1) "
"An exception occurred: vrts.nbu.admin.bpmgmt.CommandOutputException: Invalid or unexpected class configuration data: <the rest of the message will vary>"
Empty warning dialog boxes