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
- NetBackup secure communication logging
- NetBackup proxy helper logging
- NetBackup proxy tunnel logging
- Snapshot technologies
- Locating logs
- Java-based administration console logging
About UNIX system logs
On UNIX, NetBackup automatically records robotic and network errors in the system logs by using syslogd. On Windows, NetBackup records robotic and drive errors in the Event Viewer Application log. On both operating systems, log entries are also made when robotically controlled drives change between UP and DOWN states.
On HP-UX, the sysdiag tool may provide additional information on hardware errors.
To enable additional logging by NetBackup to the system logs, use one of the following:
Use the ltid command that started the device management processes. If the -v option is included on the ltid command, all daemons that were started as a result also have the -v option in effect.
Use a command to start a specific daemon (for example, acsd -v).
On UNIX, enable debug logging to the system logs by including the verbose option (-v) on the command that you use to start a daemon.
To troubleshoot ltid or robotic software, you must enable system logging. See the syslogd(8) man page for information on setting up system logs. Errors are logged with LOG_ERR, warnings with LOG_WARNING, and debug information with LOG_NOTICE. The facility type is daemon.
See the syslogd man page for the locations of system log messages on your system.