You could probably create two nodes, one that backs up the /test files and
another that backs up the /data files. Each node can be defined in a
different domain where the default management class has the required
management criteria.

But this is a very poor way to manage things. The best/preferred way is
the one that we provided for just this purpose: the include/exclude lists.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Paul Biggin <paul.biggin AT CONSIGNIA DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/10/2002 10:50
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        One Client, Two File Types, Different Retention Reqd.



Hi,

Can someone please suggest the best/preferred way of having different
retention
periods for different groups of files from one client.

I've got a client that has two different groups of files, lets say /data
and
/test.
/data needs to be retained for one month, /test for one week.

I assume that to have each group held for different retention periods, I
will
have to set up two management classes each pointing to their own backup
copy
groups. But how do I associate the  files with the intended management
class/copy group? The client is defined to a single policy domain.
I can't try include/exclude lists, as we don't use them! Is there another
way?

Cheers
Paul




This  email  and any attachments are confidential and intended for the
addressee
only.   If  you  are  not  the  named  recipient,  you  must  not use,
disclose,
reproduce,  copy  or distribute the contents of this communication.  If
you have
received  this  in  error,  please contact the sender and then delete this
email
from your system.