Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- About the capacity licensing model
- nbdeployutil utility options
- Creating and viewing the licensing report
- After creating a traditional licensing report
- After creating a capacity licensing report
- Reconciling the capacity licensing report results
- 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 selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
About busy file processing on UNIX clients
Busy file processing applies only to UNIX clients.
Information about VSP (Volume Snapshot Provider) is available for Windows clients.
The following conditions result in the detection of busy files:
Read error on the file
File modification time changed
File inode time changed
File size changed
The backup usually completes with a status of 1, which indicates that the backup was partially successful. Busy file processing allows the user control the actions of NetBackup when busy files are detected.
Busy file processing can also be enabled by adding the BUSY_FILE_PROCESSING option to the client /usr/openv/netbackup/bp.conf file. Then add other busy file options to control the processing of busy files. The options can exist in both the client /usr/openv/netbackup/bp.conf file and a user's $HOME/bp.conf. The user's bp.conf file takes precedence when the options are in both places.
NetBackup creates several files and directories when it processes busy files. Initially, a working directory named busy_files is created under /usr/openv/netbackup. NetBackup then creates the /actions directory under busy_files and places action files in that directory. An action file contains the information that NetBackup uses to control the processing of busy files.
By default, the contents of the action file are derived from the BUSY_FILE_ACTION options in bp.conf. A user can also create an action file to control a specific backup policy and schedule. NetBackup creates a logs directory under busy_files for storing busy file status and diagnostic information.