Tivoli Header

Tivoli Storage Manager for NetWare Backup-Archive Client 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 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 options file 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.dir statements first, and removes the excluded directories and files from the list of objects available for processing. See Excluding Directories and Exclude Options for more information about the exclude.dir option.

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.

After evaluating all 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, Using 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 servera\data: is defined as the domain, and that you defined the following statements for the exclude and include options:
Note:
In a NetWare environment, if you do not specify a server name, the client program uses the local server name.
   exclude servera\*:*.obj
   include servera\data:foo/.../*.obj
   exclude servera\data:foo/junk/*.obj

The current file being processed is: servera\data:foo/dev/test.obj. Processing follows these steps:

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

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

The current file being processed is: servera\data:widg/copyit.bat. 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 servera\data:widg/copyit.bat is implicitly included and is backed up.

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

The current file that processes is: servera\data:lib/objs/printf.obj. 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 servera\data:lib/objs/printf.obj is not backed up.
Note:
include and exclude.dir cannot be used together. For example the following example is not valid:
exclude.dir nds:.o=adsm
include nds:.o=adsm.ou=tucson.*

To achieve the desired results, enter:

exclude nds:.o=adsm.*
include nds:.o=adsm.ou=tucson.*

Example 4: Backing up the NDS
To back up objects in container .ou=islands.o=greece, code the following statements in the dsm.opt file:
   exclude nds:.o=greece.*
   include nds:.o=greece.ou=Islands.*   

You must specify the syntax as it appears in the examples.

Notes:

  1. Include and exclude processing does not affect processing of container entries. All containers are backed up.

  2. The NDS names that are stored by Tivoli Storage Manager are case sensitive; file space qualifiers are not.


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