Any client can exclude some files from some policy operations and include other files in other operations. This is done with statements in an include-exclude list or, on UNIX clients, in an include-exclude file. For example, an include-exclude file should exclude system files that, if recovered, could corrupt the operating system. TSM server and client directories should also be excluded. See the appropriate TSM client user's guide for details.
You can define include-exclude statements for your installation. Users can add these statements in their client options file (dsm.opt). You can also enter the statements in a set of options and assign that set to client nodes when when you register or update the nodes. For details about the DEFINE CLOPTSET and DEFINE CLIENTOPT commands, see Administrator's Guide and Administrator's Reference.
Here are a few examples of include-exclude statements:
+--------------------------------------------------------------------------------+ |exclude d:\eng\spec\*.* | |include d:\eng\spec\*.drw | |include d:\eng\spec\*.sct | +--------------------------------------------------------------------------------+
![]() | TSM reads the statements from the bottom up until a match is found. In the preceding example, no match would be found on the include statements for the file d:\eng\spec\proto.obj. TSM reads the exclude statement, finds a match, and excludes the file. |
+--------------------------------------------------------------------------------+ |exclude d:\eng\spec\*.* | |include d:\eng\spec\*.drw monthly | |include d:\eng\spec\*.sct | +--------------------------------------------------------------------------------+In this example,