Tivoli Header

Tivoli Storage Manager for UNIX Backup-Archive Clients Installation and User's Guide

Processing Include and Exclude Options

The Tivoli Storage Manager server can define include-exclude options using the inclexcl parameter in a client option set. The include-exclude statements specified by the server are evaluated along with those in the client user options file (dsm.opt). The server include-exclude statements are always enforced and placed at the bottom of the include-exclude list and evaluated before the client include-exclude statements.

If the client system options file (dsm.sys) include-exclude list contains one or more inclexcl options that specify include-exclude files, the include-exclude statements in these files are placed in the list position occupied by the inclexcl option and processed accordingly.

When performing an incremental backup, Tivoli Storage Manager evaluates all exclude.fs and exclude.dir statements first, and removes the excluded file spaces, directories, and files from the list of objects available for processing. See Excluding File Spaces and Directories and Exclude Options for more information about the exclude.fs and exclude.dir options.

Note:
Because directory branches excluded using the exclude.dir option do not display in the GUI, setting this option prevents you from performing either selective or incremental backups of data in the excluded directories from the GUI. However, you can still perform selective backups of such data from the command line.

After evaluating all exclude.fs and exclude.dir statements, Tivoli Storage Manager evaluates the include-exclude list from the bottom up and stops when it finds an include or exclude statement that matches the file it is processing. The order in which the include and exclude options are entered therefore affects which files are included and excluded. See Chapter 9, Setting Processing Options for more information about the order in which all options are processed.

To display a list of all include-exclude statements in effect on your client workstation in the actual order they are processed, use the query inclexcl command. See Query Inclexcl for more information.

The client program processes the include and exclude options as follows:

  1. Files are checked; directories are only checked if the exclude.dir option is specified.
  2. File names are compared to the include-exclude list from the bottom up. When a match is found, the processing stops and checks whether the option is include or exclude. If the option is include, the file is backed up. If the option is exclude, the file is not backed up.
  3. If a match is not found, files listed are implicitly included and backed up.
  4. If policy administration is in effect, files are backed up according to the default management class, or the management class you specify on a matching include option.

The following examples demonstrate bottom up processing.

Example 1
Assume that /home is defined as the domain, and you defined the following statements for the include and exclude options:
   exclude *.o
   include /home/foo/.../*.o
   exclude /home/foo/junk/*.o

The file being processed is: /home/foo/dev/test.o. Processing follows these steps:

  1. Rule 3 (the last include or exclude statement defined) is checked first because of bottom up processing. The file /home/foo/junk/*.o does not match the file name that is being processed.
  2. Processing moves to Rule 2 and checks. This time, file /home/foo/.../*.o matches the file name that is being processed. Processing stops, the option is checked, and it is include.
  3. File /home/foo/dev/test.o is backed up.

Example 2
Assume that /home is defined as the domain, and you defined the following statements for the include and exclude options:
   exclude *.obj
   include /home/foo/.../*.o
   exclude /home/foo/junk/*.o

The file being processed is: /home/widg/copyit. Processing follows these steps:

  1. Rule 3 is checked and finds no match.
  2. Rule 2 is checked and finds no match.
  3. Rule 1 is checked and finds no match.
  4. Because a match is not found, file /home/widg/copyit.bat is implicitly included and backed up.

Example 3
Assume that /home is defined as the domain, and that you defined the following statements for the include and exclude options:
   exclude /.../*.o
   include /home/foo/.../*.o
   exclude /home/foo/junk/*.o

The current file being processed is: /home/lib/objs/printf.o. Processing follows these steps:

  1. Rule 3 is checked and finds no match.
  2. Rule 2 is checked and finds no match.
  3. Rule 1 is checked and a match is found.
  4. Processing stops, the option is checked, and it is exclude.
  5. File /home/lib/objs/printf.o is not backed up.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]