Include-exclude file options

You can use an include-exclude options file to exclude or include specific files from space management and to assign specific management classes to these files. For example, you might want to keep certain files, on your local file system always, and thus need to exclude them from migration. Or, you might also want to include certain files for backup or migration.

Note:

If you do not create an include-exclude options file, all files are considered for backup services and the default management class is used.
On GPFS™ file systems, do not use the inclexcl option in a failover environment. Unlike dsm.opt and dsm.sys files, include-exclude options files are not shared between different nodes of a failover group. Add the include-exclude list directly to the dsm.sys file or verify that the include-exclude list files match on all nodes that participate in the local failover group or node set.

For all other file systems, use the inclexcl option in your dsm.sys file to specify the name of your include-exclude options file. You can create an include-exclude options file for each Tivoli® Storage Manager server that your client node contacts for services. For example, if your dsm.sys file contains two stanzas with options for two Tivoli Storage Manager servers, you can include an inclexcl option in each stanza. Each inclexcl option can point to a different include-exclude options file. The files that you create must reside in a directory to which all users on your workstation have read access.

Follow these rules when you include or exclude files from either backup or migration:

Use include statements to include files for backup or migration.
Use exclude statements to exclude files or directories from backup or migration.
End the specification for an include or exclude statement with a file name. You can use a wildcard in place of a specific file name.

The following options include or exclude objects from space management.

Table 1. Include and Exclude Statements
Option	Description
exclude	Excludes a file or a group of files from space management.
exclude.backup	Excludes a file from backup.
exclude.file	Excludes a file or a group of files from space management.
exclude.file.spacemgmt	Excludes a file from HSM services only. Use this option when you have both the backup-archive client and the HSM client installed.
exclude.spacemgmt	Excludes files and directories from HSM services only. Use this option when you have both the backup-archive client and the space management client installed.
include	Includes files for backup and HSM services or LAN-free data transfer.
include.file	Includes a file for backup.

The following example displays a sample include-exclude options file:

exclude /.../core
include /home/.../* personal_files
include /home/davehil/dsnew/.../*
include /home/davehil/driver5/.../* source_code
exclude.spacemgmt /home/jones/proj1/status/.../*
exclude /home/root/cron.log

In the sample include-exclude options file, personal_files and source_code identify management classes that are assigned to specific files. If you do not assign a management class to your files, the default management class is used.

Include-exclude options are processed from the bottom up. For example, when you build a migration candidates list for a file system, each file is tested against the options in the include-exclude options file beginning with the last option that you specified. If a match is found, it does not test the file against any additional options. It either excludes or includes the file as the option specifies. If a match is not found, the file is implicitly included for space management and backup services.

If you exclude a file from space management after it migrates to storage, it remains migrated until it is automatically or selectively recalled. After it is recalled, it is no longer eligible for migration. To prevent a file from migrating to storage from a local file system, assign the file to a management class without automatic or selective migration.