Step 1

Check the syntax for the directives and the file path rules.

See Pathname rules for Windows client backups.

See Pathname rules for Windows disk image (raw) backups.

See Pathname rules for Windows registry backups.

See Pathname rules for UNIX client backups.

Path rules for the NetBackup clients that are running separately-priced options are covered in the NetBackup guide for the product. (For example, Snapshot Client or NetBackup for MS-Exchange.)

Step 2

Check for warning messages.

The backup status code does not always indicate errors on the Backup Selection list. Because NetBackup does not require all paths in the Backup Selections list to be present on all clients, an error may not be especially helpful.

See About the Reports utility.

Step 3

Create a File System Backup Coverage Report.

Run the check_coverage script to create a File System Backup Coverage Report.

The script is located in install_path\NetBackup\bin\goodies (on Windows) or in /usr/openv/netbackup/bin/goodies (on UNIX). The script can reveal mistakes in the selections list that make it impossible for NetBackup to find the files. Mistakes in the selections list can result in files being skipped in the backup.

On Windows: If a path is not found, NetBackup logs a trivial (TRV) message or a warning (WRN) message. However, the same job can end with a backup status code of 0 (successful). Usually, to report files missing from the backup selections list is not helpful because not all files are expected to be present on every client. However, check the logs or use the check_coverage script to ensure that files are not missed due to bad or missing backup selections list entries.