bp.conf file entries on UNIX
The following table describes the bp.conf file entries that are used to configure busy file processing.
Table: bp.conf file entries
Entry | Description |
|---|
BUSY_FILE_PROCESSING | Enables the NetBackup busy file-processing feature. By default, this entry is not present in the client's /usr/openv/netbackup/bp.conf file.
|
BUSY_FILE_DIRECTORY | Specifies an alternate path to the busy files working directory. This entry is not required. By default, this entry is not present in the client's /usr/openv/netbackup/bp.conf or $HOME/bp.conf file. By default, NetBackup creates the busy_files directory in /usr/openv/netbackup or the user's home directory.
|
BUSY_FILE_ACTION | Directs the action that NetBackup performs on busy files. By default, this entry is not present in the client's /usr/openv/netbackup/bp.conf or $HOME/bp.conf file.
Multiple entries may exist in the following form:
BUSY_FILE_ACTION =
filename_template action_template Where filename_template is the absolute pathname and file name of the busy file. The shell language metacharacters *, ?, [], [ - ] can be used to match the patterns of file names or parts of file names. action_template is one of the following: MAIL | mail Directs NetBackup to mail a busy file notification message to the user that the BUSY_FILE_NOTIFY_USER option specifies. REPEAT | repeat [repeat_count] Directs NetBackup to retry the backup on the specified busy file. A repeat count can be specified to control the number of backup attempts. The default repeat count is 1. IGNORE | ignore Directs NetBackup to exclude the busy file from busy file processing. The file is backed up and a log entry that indicates that the file was busy appears in the All Log Entries report. BUSY_FILE_NOTIFY_USER Specifies the recipient of the busy file notification message when BUSY_FILE_ACTION is set to MAIL or mail. By default, BUSY_FILE_NOTIFY_USER is not in /usr/openv/netbackup/bp.conf or $HOME/bp.conf file on a client. By default, the mail recipient is root. See Table: Examples of how a BUSY_FILE_ACTION entry works.
|
The following table shows examples of how a BUSY_FILE_ACTIONentry works.
Table: Examples of how a BUSY_FILE_ACTION entry works
Example | Description |
|---|
BUSY_FILE_PROCESSING
BUSY_FILE_DIRECTORY =
/tmp
BUSY_FILE_NOTIFY_USER =
kwc
BUSY_FILE_ACTION =
/usr/* mail
BUSY_FILE_ACTION =
/usr/local ignore | This example causes NetBackup to take the following actions when it encounters busy files: |
BUSY_FILE_PROCESSING
BUSY_FILE_ACTION =
/usr/* repeat 2
BUSY_FILE_ACTION =
/usr/openv mail
BUSY_FILE_ACTION =
/usr/local ignore | This example causes NetBackup to take the following actions when it encounters busy files: Send a busy file notification message to root for busy files in /usr/openv. Repeat the backup up to two times for all busy files that it finds under /usr, except for those in /usr/openv and /usr/local. Exclude the busy files in /usr/local from all actions.
|
