NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and usage reporting
- How capacity licensing works
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Reviewing an NEVC licensing report
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About Tape I/O commands on UNIX
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
|
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:
|