ADSM-L

Re: Default management class

2002-12-10 12:22:22
Subject: Re: Default management class
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 10 Dec 2002 10:21:38 -0700
>>
Anyone got any thoughts on the differences between a default management
class as nominated for each policy domain and the the class_name "default"
as assigned by TSM.
<<

There are no differences. They are one and the same. There is no
management class named "DEFAULT". Rather, files bound to the "DEFAULT"
management class are really bound to the class that is designated as the
default management class for that policy domain ("STANDARD", in your
case). If the default management class changes, then files bound to
"DEFAULT" will be managed by the new designated default management class.

Directories are always bound to a specific management class (you should
not see "DEFAULT" for directories); either the one with the longest
RETONLY setting or the one you specified via DIRMC. If a different
management class becomes the one with the longest RETONLY setting, then
directories will be rebound to that management class during the next full
incremental backup (except for the ones bound to the DIRMC management
class).

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.eyebm DOT com (change eye to i to reply)

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




John Naylor <john.naylor AT SCOTTISH-SOUTHERN.CO DOT UK>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/10/2002 09:48
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Default management class



I am reposting this, because I got no takers on the original.
Anyone got any thoughts on the differences between a default management
class as
nominated
for each policy domain and the the class_name "default" as assigned by
TSM.
Thanks,
John
---------------------- Forwarded by John Naylor/HAV/SSE on 12/10/2002
04:43 PM
---------------------------


John Naylor
12/06/2002 01:02 PM

To:   "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>
cc:
Subject:  Default management class  (Document link: John Naylor)

Here is one that someone might like to enlighten me on
I ran a query to extract all the management classes in use by each client
from
the backups table
That probably was not a good move as it runs for a heck of a long time.
Well it finished eventually and I got my listing.
Quite a few clients included a management class of "default"
This is not the deault management class for each policy domain, as I use a
management class
called "standard" for this.
Ok since not all the clients use DIRMC, I assumed this would be for
directories,
where the underlying management class would be the one with the longest
retention.
The first client I looked at showed the majority were files.
I looked in more detail and saw that the date of the backups was the date
the
client was registered
Ok, so I am assuming here that the default class is because a backup was
issued
before the dsm.opt was entered with the proper incl/excl/management class
statements.
The question is then:-

Are the retention values for the files "default" different from those for
the
directories "default".
If you have a default management class set up for each domain does the
file
"default" class take those values or some other values, and if so how do
you
find out what they are
Finally for someone who really knows the internals, if the retention
values are
different for "default"
for files against directories, how does TSM match this up.
Does it have to run separate expiration for files against directories,
Thanks







**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>