Processes used in NetBackup client-server communication

This topic describes the logs that record the 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

Log directory	Type of backup
Linux/UNIX log: /usr/openv/netbackup/logs/bpbkar Windows log: install_path\netbackup\logs\bpbkar	Standard, MS-Windows, FlashBackup, FlashBackup-Windows, Enterprise Vault, Lotus Notes, Domino, SharePoint, DB2 snapshot backups, Oracle RMAN PROXY/snapshot backups, Oracle Block Incremental Backups without RMAN, MS-SQL-Server snapshot backups
Linux/ UNIX log: /usr/openv/netbackup/logs/bpdb2 Windows log: install_path\netbackup\logs\bpdb2	DB2 stream-based backups. The `bpdb2` directory must be writable by the DB2 user (not only by the root user).
Linux/UNIX log: /usr/openv/netbackup/logs/dbclient Windows log: install_path\netbackup\logs\dbclient	Oracle RMAN stream-based backups. The `dbclient` directory must be writable by the Oracle user (not only by the root user).
Windows log: install_path\netbackup\logs\dbclient	MS-SQL-Server stream-based backups. (Not supported on UNIX or Linux.)
Linux/UNIX log: /usr/openv/netbackup/logs/exten_client Windows log: install_path\netbackup\logs\exten_client	DataStore/XBSA stream-based backups. The `exten_client` directory must be writable by the application that performs the backup operation or the restore operation.
Linux/UNIX log: /usr/openv/netbackup/logs/infxbsa	Informix stream-based backups. The `infxbsa` directory must be writable by the Informix user. (Not supported on Windows.)
Linux/UNIX log: /usr/openv/netbackup/logs/sybackup Windows log: install_path\netbackup\logs\sybackup	Sybase stream-based backups. The `sybackup` directory must be writable by the application that performs the backup operation or the restore operation.

Log directory

Type of backup

Linux/UNIX log:

/usr/openv/netbackup/logs/bpbkar

Windows log:

install_path\netbackup\logs\bpbkar

Standard, MS-Windows, FlashBackup, FlashBackup-Windows, Enterprise Vault, Lotus Notes, Domino, SharePoint, DB2 snapshot backups, Oracle RMAN PROXY/snapshot backups, Oracle Block Incremental Backups without RMAN, MS-SQL-Server snapshot backups

Linux/ UNIX log:

/usr/openv/netbackup/logs/bpdb2

Windows log:

install_path\netbackup\logs\bpdb2

DB2 stream-based backups.

The bpdb2 directory must be writable by the DB2 user (not only by the root user).

Linux/UNIX log:

/usr/openv/netbackup/logs/dbclient

Windows log:

install_path\netbackup\logs\dbclient

Oracle RMAN stream-based backups.

The dbclient directory must be writable by the Oracle user (not only by the root user).

Windows log:

install_path\netbackup\logs\dbclient

MS-SQL-Server stream-based backups. (Not supported on UNIX or Linux.)

Linux/UNIX log:

/usr/openv/netbackup/logs/exten_client

Windows log:

install_path\netbackup\logs\exten_client

DataStore/XBSA stream-based backups.

The exten_client directory must be writable by the application that performs the backup operation or the restore operation.

Linux/UNIX log:

/usr/openv/netbackup/logs/infxbsa

Informix stream-based backups.

The infxbsa directory must be writable by the Informix user. (Not supported on Windows.)

Linux/UNIX log:

/usr/openv/netbackup/logs/sybackup

Windows log:

install_path\netbackup\logs\sybackup

Sybase stream-based backups.

The sybackup directory must be writable by the application that performs the backup operation or the restore operation.

Processes used in NetBackup client-server communication

Feedback

Feedback