As you know, it works from the bottom up. 

Once a pattern is found that matches the file. It backs up the file and 
moves on.  All the other inclexcl lines, above it, are ignored once it 
matches the pattern for that file.  (With the exception of "exclude.dir", 
which is never ignored)

As long as you have /backups/databases/* under the /backups/*  that will 
be the first pattern that is matched for those
files and it will not be backed up twice. 

Remember to perform a "q inclexcl" from the client to make sure everything 
looks as you expect.  Also remember that "q inclexcl" shows everything in 
the "correct" order from top to bottom and combines all the 
inclusions/exclusions from the registries, option files and server clopts.

Regards, 
Shawn
________________________________________________
Shawn Drew





Internet
billpp AT GMAIL DOT COM

Sent by: ADSM-L AT VM.MARIST DOT EDU
09/16/2009 06:51 PM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
[ADSM-L] [TSM] Client Options Set - A bit confuse






Hi folks, evening all...

I'm trying to write my first CLIENTOPT (at server side) and i'm
totally confused...

What I need is:
(all mgmtclass are already defined)

/backups/backup_mail/mailman IS EXCLUDED
/backups/backup_mail/vmail IS EXCLUDED
/backups/* goes to 7Ver3Anos
/backups/databases/* goes to 14Ver3Anos

I could easily write it dir by dir, but I want to understand how to
use "more specific" clause...

I know that inclexcl is read from bottom to top and already read that
/backups/.../* would backup everyting under /backups directory...
But I can't find how to use it with different Mgmtclass...

If I do:

/backups/.../* 7Ver3Anos
/backups/databases/.../* 14Ver3Anos

Will "databases" dir be backed up twice?
Can it be done? (I'm almost sure it can).

Thanks in advance.

--

Flávio do Carmo Júnior aka waKKu
Florianópolis/SC - Brazil



This message and any attachments (the "message") is intended solely for 
the addressees and is confidential. If you receive this message in error, 
please delete it and immediately notify the sender. Any use not in accord 
with its purpose, any dissemination or disclosure, either whole or partial, 
is prohibited except formal approval. The internet can not guarantee the 
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) 
not therefore be liable for the message if modified. Please note that certain 
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.