Processes used in NetBackup client-server communication
The logs described in this topic record details about the NetBackup client-server communication. You can use these logs to adjust NetBackup client-server communication by means of wait and delay counters, as described in related topics.
Table: Logs used in NetBackup client-server communication
Type of backup
Standard, MS-Windows, FlashBackup, FlashBackup-Windows,
Lotus Notes, Domino,
DB2 snapshot backups,
Oracle RMAN PROXY/snapshot backups,
Oracle Block Incremental Backups without RMAN,
MS-SQL-Server snapshot backups
DB2 stream-based backups.
The bpdb2 directory must be writable by the DB2 user (not just by the root user).
Oracle RMAN stream-based backups.
The dbclient directory must be writable by the Oracle user (not just by the root user).
MS-SQL-Server stream-based backups. (Not supported on UNIX or Linux.)
DataStore/XBSA stream-based backups.
The exten_client directory must be writable by the application that is performing the backup/restore operation.
Informix stream-based backups.
The infxbsa directory must be writable by the Informix user. (Not supported on UNIX or Linux.)
Sybase stream-based backups.
The sybackup directory must be writable by the application that is performing the backup/restore operation.
See Finding wait and delay counter values
See Example of using wait and delay counter values