The include-exclude list

You can define an include-exclude list to specify which files are eligible for the different processes that the client can run. Include and exclude options in the list determine which files are eligible for backup and archive services and which files can be migrated from the client (space-managed).

The options also include how the server controls symbolic links and processing such as image, compression, and encryption.

If you do not create an include-exclude list, the following default conditions apply:
  • All files that belong to the user are eligible for backup and archive services.
  • The default management class governs backup, archive, and space-management policies.
Figure 1 shows an example of an include-exclude list. The statements in this example list perform the following actions:
  • Excludes certain files or directories from backup, archive, and client migration operations

    Line 1 in Figure 1 means that the SSTEINER node ID excludes all core files from being eligible for backup and client migration.

  • Includes some previously excluded files
    Line 2 in Figure 1 means that the files in the following directory are excluded:
    • AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systems/home/ssteiner
    • Windows operating systems*:\home\ssteiner
    The include statement that follows on line 3, however, means that the options.scr file in that directory is eligible for backup and client migration.
  • Binds a file to a specific management class
    Line 4 in Figure 1 means that all files and subdirectories that belong to the following directory are managed by the policy defined in the MCENGBK2 management class:
    • AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systems/home/ssteiner/driver5
    • Windows operating systems*:\home\ssteiner\driver5
Figure 1. Example of an include-exclude list
AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systems
exclude /.../core
exclude /home/ssteiner/*
include /home/ssteiner/options.scr
include /home/ssteiner/driver5/.../* mcengbk2
Windows operating systems
exclude *:\...\core
exclude *:\home\ssteiner\*
include *:\home\ssteiner\options.scr
include *:\home\ssteiner\driver5\...\* mcengbk2

Tivoli® Storage Manager 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. Therefore, the order in which the include and exclude options are listed affects which files are included and excluded. For example, suppose that you switch the order of two lines in the example, as follows:

AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systems
include /home/ssteiner/options.scr
exclude /home/ssteiner/*
Windows operating systems
include *:\home\ssteiner\options.scr
exclude *:\home\ssteiner\*
The exclude statement comes last, and excludes all files in the following directory:
  • AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systems/home/ssteiner
  • Windows operating systems*:\home\ssteiner
When Tivoli Storage Manager is processing the include-exclude list for the options.scr file, it finds the exclude statement first. This time, the options.scr file is excluded.

Some options are evaluated after the more basic include and exclude options. For example, options that exclude or include files for compression are evaluated after the program determines which files are eligible for the process being run.

You can create include-exclude lists as part of client options sets that you define for clients.

For detailed information on the include and exclude options, see the user’s guide for the appropriate client.