Tivoli Storage Manager for NetWare Using the Backup-Archive Client


Chapter 7. Creating an Include-Exclude List

You can create an include-exclude list to exclude a specific file or groups of files from backup services, and to assign specific management classes to files. TSM backs up any file that is not explicitly excluded. TSM client directories should be excluded from backup services.

You can create an include-exclude list, by performing the following steps:

  1. Determine your include and exclude requirements.
  2. Locate the include-exclude section in your client options file.
  3. Enter your include and exclude statements using the appropriate include-exclude options in Table 7. Because TSM processes your include-exclude list from the bottom of the list up, it is important to enter all your include-exclude statements in the same section.
  4. Save the file and close it.

Table 7 provides brief descriptions of the include and exclude options that you can specify in your client options file. See table references for more information about each option.

Table 7. Include-Exclude Options

Option Description Page
exclude Excludes a file or group of files from backup services. Any file in your client domain that is not specifically excluded with this option is considered for backup. Exclude Options
exclude.archive Excludes a file or group of files from archive services. Exclude Options
exclude.backup Excludes a file or a group of files from backup services only. Exclude Options
exclude.dir Locates matching directory names. If a matching directory is found, that directory, its files, and all its subdirectories and their files are excluded from backup services. Exclude Options
exclude.file Excludes files, but not directories, that match a pattern. Exclude Options
exclude.file.backup Excludes a file from normal backup services. Exclude Options
include Includes files or management classes for backup or archive processing. Include Options
include.file Includes a file for backup services, or assigns a management class to a file. Include Options

Excluding System Files

We recommend that you have the following minimum include-exclude list in your client options file:

Log files:

   SYS:VOL$LOG.ERR
   SYS:TTS$LOG.ERR
   SYS:SYSTEM\SYS$LOG.ERR
   SYS:SYSTEM\EVENTS.LOG
   SYS:SYSTEM\SECAUDIT.LOG
   SYS:SYSTEM\SYSTEM.LOG
Bindery files (Valid for NetWare V3 only) :
   SYS:SYSTEM\NET$OBJ.SYS
   SYS:SYSTEM\NET$PROP.SYS
   SYS:SYSTEM\NET$VAL.SYS
General files that NetWare programs always accessed and that cannot be opened for reading:
   SYS:SYSTEM\CMASTER.DBA
   SYS:SYSTEM\BTRIEVE.TRN
   SYS:SYSTEM\TSA\TSA$TEMP.*

These are system files that cannot be recovered without possibly corrupting the operating system.


Including and Excluding Groups of Files

To specify groups of files that you want to include or exclude, use the wildcard characters listed in Table 8. This table applies to include and exclude statements only. For information about using wildcard characters in TSM commands, see Using Wildcard Characters.

Table 8. Wildcard and Other Special Characters

Character Function
? The match-one character matches any single character except the directory separator; it does not match the end of the string. You cannot use the match-all character (or any wildcard character) when specifying the high-level qualifier of an object, only use it for the low-level qualifier. . For example:
  • The pattern ab?, matches abc, but does not match ab, abab, or abzzz.
  • The pattern ab?rs, matches abfrs, but does not match abrs, or abllrs.
  • The pattern ab?ef?rs, matches abdefjrs, but does not match abefrs, abdefrs, or abefjrs.
  • The pattern ab??rs, matches abcdrs, abzzrs, but does not match abrs, abjrs, or abkkkrs.
* The match-all character. You cannot use the match-all character (or any wildcard character) when specifying the high-level qualifier of an object, only use it for the low-level qualifier. For example:
  • The pattern ab*, matches ab, abb, abxxx, but does not match a, b, aa, bb.
  • The pattern ab*rs, matches abrs, abtrs, abrsrs, but does not match ars, or aabrs, abrss.
  • The pattern ab*ef*rs, matches abefrs, abefghrs, but does not match abefr, abers.
  • The pattern abcd.*, matches abcd.c, abcd.txt, but does not match abcd, abcdc, or abcdtxt.
\... The match-n character matches zero or more directories.
\

The directory separator character limits the scope of the search for the matching n characters and directories. If a pattern does not begin with a directory separator (or one does not follow the drive specification), a match all directories is appended to the pattern. For example, these patterns are equivalent:

   sys:*
   sys:.../*

[ The open character-class character begins the enumeration of a character class. For example:
   xxx[abc] matches xxxa, xxxb, or xxxc.
- The character-class range includes characters from the first character to the last character specified. For example:
   xxx[a-z] matches xxxa, xxxb, xxxc, ... xxxz.
/

The literal escape character. When used within a character class it causes the next character to be treated literally. When used outside a character class, it is used as a directory separator.

This is also a server name delimiter when it is placed before a volume delimiter (:). For example:

servername\volumename:/directoryname/file.name

] The close character-class character ends the enumeration of a character class.
: The volume separator character separates a file specification. The characters before the colon identify a volume name. The characters after the colon identify either a directory name or a file name. For example:
volumename:/directoryname/file.nam

Examples Using Wildcards With Include and Exclude Patterns

TSM accepts the exclude.dir option which can be used to exclude directory entries. However, include and exclude.dir cannot be used together. For example, the following statements will not produce the desired results:

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

You must code the following statements to include only the objects in the .o=adsm.ou=tucson branch of the NDS:

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

Table 9 contains examples of ways you might use wildcard characters with include and exclude patterns.

Table 9. Using Wildcard Characters with Include and Exclude Patterns

Task Pattern
Exclude all files with an extension of .bak, except those found on servera in the one:/dev directory.
exclude servera\*:.../*.bak
include servera\one:dev/*.bak 

Exclude all files and directories under any tmp directory that might exist on servera, except for the file, vol:/tmp/save.fil. Include this file.
exclude servera\*:.../tmp/.../*
include servera\vol:tmp/save.fil

Exclude any .obj file in any directory on volumec, volumee, volumef, and volumeg.
exclude servera\volume[ce-g]:/.../
*.obj

Exclude the .obj files found in the root directory in the volumed drive only.
exclude servera\volumed:*.obj

Exclude any file that resides under the tmp directory found on any volume.
exclude servera\*:tmp/.../*


Processing Include and Exclude Options

Include-exclude options can be defined on the server using the inclexcl parameter. The include-exclude statements specified by the server are evaluated along with those in the client options file. 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. TSM processes 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 listed therefore affects which files are included and excluded. See Chapter 8, "Setting Common Options" for more information about the order in which all options are processed.

The TSM 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.

    You can use the exclude.dir option in your options file to exclude directories and subdirectories from backup. See Exclude Options for more information.

  2. Options are checked from the bottom of the include-exclude list up, until a match is found. However, on full incremental backups exclude.fs statements take precedence over other include-exclude statements, regardless of their position in the include-exclude list. See Exclude Options for more information.

    If 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.

The following examples demonstrate bottom up processing.

Example 1
Assume that servera\data: is defined as the domain, and 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 TSM client program uses the local server name.
   exclude servera\*:*.obj
   include servera\data:foo/.../*.obj
   exclude servera\data:foo/junk/*.obj

The current file that processes 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 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: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 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 dir:.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 TSM are case-sensitive; file space qualifiers are not.


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