Anne,
Perhaps your situation is unique, but what we did is establish a
management class of DIR for the DIRMC class. In other words, in all of our
CLOPTSETs, we specify the DIRMC option with a value of DIR. So, all our
directory information goes to management class DIR and we provide the
appropriate services for the DIR management class and DIR storage pools.
Actually, I can't claim credit for this idea. A look through the ADSM-L
archives on DIRMC will help out a lot.
Once again, good luck.
John G. Talafous IS Technical Principal
The Timken Company Global Software Support
P.O. Box 6927 Data Management
1835 Dueber Ave. S.W. Phone: (330)-471-3390
Canton, Ohio USA 44706-0927 Fax : (330)-471-4034
[EMAIL PROTECTED] http://www.timken.com
-----Original Message-----
From: Short, Anne [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 20, 2001 1:44 PM
To: [EMAIL PROTECTED]
Subject: Re: Using client option sets with multiple active policy sets.
But if I had a single client option set that contained the following:
Dirmc=<name_of_default_management_class>
I don't think that would work because each DOMAIN's
<name_of_default_management_class> is different.
Anne Short
Lockheed Martin Enterprise Information Systems
Gaithersburg, Maryland
301-240-6184
CODA/I Storage Management
-----Original Message-----
From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 20, 2001 1:36 PM
To: [EMAIL PROTECTED]
Subject: Re: Using client option sets with multiple active policy sets.
Anne,
Only one client optionset should be necessary. For example, you could
create a cloptset of WINDOWS with the include/exclude statements you require
for your WINDOWS clients. Notice the REG NODE and UPD NODE commands. You
specify the CLOPTSET in addition to the DOMAIN. They should work to
compliment one another.
Good luck!
John G. Talafous IS Technical Principal
The Timken Company Global Software Support
P.O. Box 6927 Data Management
1835 Dueber Ave. S.W. Phone: (330)-471-3390
Canton, Ohio USA 44706-0927 Fax : (330)-471-4034
[EMAIL PROTECTED] http://www.timken.com
-----Original Message-----
From: Short, Anne [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 20, 2001 12:53 PM
To: [EMAIL PROTECTED]
Subject: Using client option sets with multiple active policy sets.
Hoping someone can either give me some advice or tell me about similar
experiences....
We have NT clients in 4 different active Policy Sets, and each Policy Set
has a uniquely named Default Management Class. I now want to create a
Client Option Set to be used for ALL clients. The client option set is to
contain include/exclude statements (to associate certain files with a new
Management Class I will be creating and which I now realize I will have to
create in every Policy Set), as well as a DIRMC option (to force the
directories to continue to be associated with the default MC as opposed to
the new one). Since Client Options Sets are not associated with any
particular Policy Domain/Set, am I going to be forced to create 4 different
Client Option Sets to accommodate the different default MC names in each
Set??
I need the DIRMC statement, as the new MC class I will be creating will have
a longer retention period than the default MC. But I do not want the
directories to rebind with the new MC as that would eat up way too many
resources (tapes, disk, db, etc). The new MC I want to create is to be able
to keep 365 copies of just 3 files that change every day on every client
(over 100). I don't need to keep ALL the directories for 365 days when I
only want to keep 3 files located on the C: drive for that long.
The other option that has been proposed is to use the archive function on
these 3 files as opposed to a backup. I'm beginning to think that would
make more sense due to the number of active Policy Sets we have. Anyone
have any advice/experience?
Anne Short
Lockheed Martin Enterprise Information Systems
Gaithersburg, Maryland
301-240-6184
CODA/I Storage Management
