About the logs directory on UNIX
During busy file processing NetBackup creates a number of files under the busy_files/logs directory. These files contain status and diagnostic information. NetBackup derives the names of these files from the policy name, schedule name, and process ID (PID) of the backup.
NetBackup creates the following logs:
Busy file log
NetBackup records the names of any busy files in the busy file log. The name of the busy file log has the following form:
policy_name.schedule_name.PID
Diagnostic log file
NetBackup generates a log file that contains diagnostic information. The name of the log file has the following form:
log.policy_name.schedule_name.PID
Retry log file
NetBackup also generates a retry file that contains diagnostic information that is recorded when the repeat option is specified. The name of the retry file has the following form:
policy_name.schedule_name.PID.retry.retry_count
Where retry_count starts at zero and increases by one every time a backup is repeated. Processing stops when retry_count is one less than the number that is specified by the repeat option.
Example:
To service busy file backup requests, the administrator defined a policy named AAA_busy_files that has a user backup schedule named user. A scheduled backup is initiated with the policy named production_servers, schedule named full, and PID of 1442.
If busy files are detected, NetBackup generates the following files in the /usr/openv/netbackup/busy_files/logs directory:
production_servers.full.1442
log.production_servers.full.1442If the actions file has the repeat count set to 2, NetBackup generates the following files:
production_servers.full.1442.retry.0
AAA_busy_files.user.10639
log.AAA_busy_files.user.10639If a repeat backup is attempted, NetBackup generates the following files:
production_servers.full.1442.retry.1
AAA_busy_files.user.15639
log.AAA_busy_files.user.15639