Managing Backup Policies (Classes)
83
3
1. Check all entries to ensure you have followed the file-path rules for the
clients you are backing up. Also, verify the syntax for any directives that are
included in the list.
2. For the first set of backups, check the Problems or All Log Entries reports
for warning messages (see examples below) and run the
check_coverage
script (located in install_path
\NetBackup\bin\goodies
).
This step can reveal mistakes that result not backing up files because the
files are not found. The status code for a backup does not always indicate
an error of this nature because NetBackup does not require all paths in the
file list to be present on all clients. This allows you to have a generic list that
multiple clients can share. Requiring all entries to match for a successful
backup would result in more classes, unless all clients had identical
filesystems.
If a path is not found, NetBackup logs a trivial (TRV) or warning (WRN)
message, but can still end the backup with a status code 0 (success). This is
desirable because it eliminates error status codes for files that are not
expected to be on a client. However, it means you must check the logs or
use the
check_coverage
script to ensure that files are not missed due to
bad or missing file list entries.
The examples below show the log messages that appear when files are not
found. For information on using
check_coverage
, see the comments in
the script.
Example 1 - Regular Expressions or Wildcards
Assume the file list contains a regular expression such as:
\home1[0123456789]
Here, NetBackup backs up
\home10
through
\home19
if they are present. If
they are not present, the Backup Problems or All Log Entries report shows a
message similar to the following:
02/02/99 20:02:33 windows freddie from client freddie: TRV - Found
no matching file system for \home1[0123456789]
NetBackup 3.2 System Administrator's Guide for Windows NT
NetBackup 3.2 System Administrator's Guide for Windows NT
