I was actually trying to avoid the use of a long domain statement.  This
adds complexity and I'm looking to simplify.

In real life there are well over 20 file systems on this particular
server of which many are required.  We have strict SLA's and as per our
clients we do not back up what they don't need.  We also have a usage
based chargeback system in place which gives us a lot of incentive to
minimize the amount of non-business data being backed up.  We run daily
comparison reports of dumps of the file spacetable which alert us if a
new filespace has been added / removed from a client.  The "exclude
/.../*" allows TSM to recognize a new filespace without actually backing
up the data.

If domain is my only options then I may have to remove the exclude
/.../* statement.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Thomas Denier
Sent: Tuesday, February 07, 2006 4:42 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Inclexcl for root file system


>From: "L'Huillier, Denis (GTI)" <denis_lhuillier AT ML DOT COM>
>
>I'm trying to include the root "/" file system and exclude
>everything
>else not previously matched in my inclexcl file.
>
>Example...
>File systems:
>/
>/data
>/data1
>/data2
>/dump
>/junk
>
>Inclexcl:
>
>Exclude /.../* <-- Here I want to exclude everything not
>explicitly
>stated below which would include "/junk" and any future file system.
>Include /    <--Here I want the root file system and all
>subdirectories that are mounted on root.
>Include /data/.../* CLASS3
>Exclude /data/.../*.out
>Include /data1/.../* CLASS2
>Include /data2/.../* CLASS1
>
>The "Include /" line will not get all files and subdirectories that
>are
>part of the root file system. If I use "Include /.../*" then it
>negates
>the "Exclude /.../*" above it.

I really don't recommend making exclusion the rule and inclusion the
exception. If the system file population changes and you forget a
necessary update to the include/exclude file you may fail to backup
data that should be backed up. If inclusion is the rule and exclusion
the exception, a similar mistake might cause you to backup unneeded
data. The latter is normally considered the less serious risk.

If you must go ahead with this approach, I would suggest using the
'domain' option to limit backup coverage to the four file systems
containing the data you care about. You could then have three
excludes like 'exclude /data/.../*' and more specific includes as
in your original plan.
--------------------------------------------------------

If you are not an intended recipient of this e-mail, please notify the sender, 
delete it and do not read, act upon, print, disclose, copy, retain or 
redistribute it. Click here for important additional terms relating to this 
e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------