Maybe the better wording of "new domain, copy mgmt classes" was "copy the
domain to new one and move the node in it" :-)) Thus you will do it in
single "copy domain" command.
After the node with no limits is moved into new domain, you can simply
delete the unlimited class in old domain. Non-existent directories will
respect default class' copygroup settings and existing directories will be
re-bound either to the class with longest retention (which probably is the
default one).
Having unnecessary mgmtclasses might be additional burden to manage. We
cannot measure how many cents or dollars, but it will cost you something.
I(nsH)MO you can safely get rid of the class. After expiration runs once
expiring all unnecessary directories and you are confident all nodes have
DIRMC enforced somehow, you can copy back the class and move the node back
deleting the no more necessary copy of the policy domain. Cleanup often
produces effectiveness!

Zlatko Krastev
IT Consultant






"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01.07.2003 18:45
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Management class problems.....


When you set up the DIRMC parameter and run a new backup, the directories
that still exist on the client will be rebound to the DIRMC management
class, and expire according to its rules.

Directories that no longer exist on the machine because they have been
deleted can't be rebound.

If that is a big problem for you, there are some funky things you can do
that are more work.  You could create a new domain, copy the management
classes so they are identical.  Move the 1 client that needs NOLIMIT to
that
domain.  Then change the existing management class in the original domain
so
it doesn't specify UNLIMITED anymore.  That should work.

-----Original Message-----
From: Raminder Braich [mailto:Raminder.Braich AT DAVEY DOT COM]
Sent: Tuesday, July 01, 2003 11:32 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Management class problems.....


Thanks Wanda. On closer inspection I found exactly what you described. The
directories are being bound to this management class. I would look into
DIRMC parameter, but is there any way to expire the directories from the
present management class.

Thanks,
Raminder Braich.



"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
07/01/2003 11:10 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Management class problems.....





DIRECTORIES are always bound to the management class with the longest
retention period, not necessarily the default management class.  That
probably explains what is happening.

Look at using the DIRMC parameter in the dsm.opt file.
It lets you specify which management class you want the directories to
use.





-----Original Message-----
From: Raminder Braich [mailto:Raminder.Braich AT DAVEY DOT COM]
Sent: Tuesday, July 01, 2003 9:56 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Management class problems.....


The environment:
        TSM server 4.1.2.0
        TSM Client 4.1.2.0
        Server OS Win 2K
        Client OS Win NT

We have one management class  in a policy set which never expires the
files. The limits are set to NOLIMIT. This management class was to be used
only for a particular directory on a particular client. However, most of
the clients are using this management class for backing up some of their
files. The rest of the files are being backed up to the default management
class, which is how it should be.
        How can I make the clients stop using this particular management
class? How can I expire the files from this management class except for
that one particular client? There is no mention of this class in the
client options file and there are no client option sets. Here is the
client options file from one of the clients.

LANG                    AMENG
commmethod              TCPIP
tcpserveraddress        xx.x.xxx.x
passwordaccess          generate
schedlogretention       7 d
errorlogretention       30 d
subdir                  yes
schedmode               polling  *changed 5/01/01 RSB
*schedmode              prompted

DOMain ALL-LOCAL
Exclude "*:\macintosh volume\*"
Exclude "*:\macintosh volume\*.*"
Exclude "*:\macintosh volume\...\*"
Exclude "*:\macintosh volume\...\*.*"
Exclude "*:\microsoft uam volume\*"
Exclude "*:\microsoft uam volume\*.*"
Exclude "*:\microsoft uam volume\...\*"
Exclude "*:\microsoft uam volume\...\*.*"
Exclude "*:\...\EA DATA. SF"
Exclude *:\...\pagefile.sys
Exclude *:\IBMBIO.COM
Exclude *:\IBMDOS.COM
Exclude *:\MSDOS.SYS
Exclude *:\IO.SYS
Exclude *:\...\SYSTEM32\CONFIG\*.*
Exclude *:\...\SYSTEM32\CONFIG\...\*
Exclude i:\...\*
Exclude i:\...\*.*
Exclude i:\*
Exclude i:\*.*
Exclude d:\...\*
Exclude d:\...\*.*
Exclude d:\*
Exclude d:\*.*
Exclude y:\*
Exclude y:\...\*.*
Exclude y:\...\*

Thanks,
Raminder Braich.