Enabling the debug logs manually (DB2 client) (UNIX/Linux)
To enable the debug logs manually
- Create the following directories on the client:
bpubsdb2
For any DB2 instance browse problems when bpdb2proxy is used for backup or restore.
/usr/openv/netbackup/logs/bpubsdb2
bphdb
For any backup that is initiated from an automated schedule on the primary server.
/usr/openv/netbackup/logs/bphdb
bpdb2
For any backup or restore of the database and or LOGARCHMETH2=VENDOR log backups.
/usr/openv/netbackup/logs/bpdb2
bpbkar
For any snapshot backup or user-exit log backup.
/usr/openv/netbackup/logs/bpbkar
nbtar
For any snapshot restore or user-exit log restore.
/usr/openv/netbackup/logs/tar
- Verify the user or group that the DB2 process (process that loads bpdb2) has appropriate permissions to access the following directories if they exist. If the following directories do not exist, the directories are created automatically with the correct permissions.
/usr/openv/logs/user_ops
/usr/openv/logs/user_ops/dbext
/usr/openv/logs/user_ops/dbext/logs
Also verify that the user or group that the DB2 process runs as has appropriate permissions to access the log directories in step 1.
- On the NetBackup server or servers, create the debug log directories for the legacy processes that interact with the DB2 agent.
On the primary server:
/usr/openv/logs/bprd
On the media server or servers:
/usr/openv/logs/bpbrm
/usr/openv/logs/bptm
- The debug logs for unified processes on the server and the client hosts are created automatically by NetBackup.
NetBackup writes unified logs to /usr/openv/logs.
For information on how to use logs and reports, see the NetBackup Troubleshooting Guide.