Troubleshooting Debug logging
Line 14 provides the name of the batch file. Since the backup was launched immediately, it was placed in install_path\NetBackup\DbExt\MsSql\Temp directory.
Line 16 provides the actual SQL syntax that was used to launch the backup command.
Line 17 indicates that this was a single stream backup.
Lines 18 to 42 provide NetBackup-based client parameters and statuses. Note that the server status on line 40 indicates that the operation completed with status 0, which indicates success.
The NetBackup master server and client software offers a comprehensive set of debug logs for troubleshooting problems that may occur during NetBackup operations. Debug logging is also available for SQL backup and restore operations. You can control the amount of information written to debug logs. Following the instructions in “Setting the debug level”. After the cause of the problem has been determined, debug logging can be disabled.
For details on the contents of these debug logs, refer to the NetBackup Troubleshooting Guide. For additional NetBackup client logs and NetBackup master server logs, see the online help for the Backup, Archive, and Restore interface and the NetBackup Administrator’s Guide, Volume I.
To create all debug logs
Run the following batch file:
Backup operation debug logging
The following logs pertain to backup operations: install_path\NetBackup\logs\bphdb (scheduled backups only) install_path\NetBackup\logs\dbclient install_path\NetBackup\logs\bpbkar (Snapshot Client) install_path\NetBackup\logs\bpfis (Snapshot Client)
Log names are formatted as mmddyy.log, where mm is the month, dd is the day, and yy is the year.