Re: Management class Revamp

Thank you for your reply. 
I have read the articles you refer to as well as the documentation and
thus my confusion.

Here is some clarification. 
I have a single TSM server. I am moving clients from one domain to a
multiple domain structure within TSM. 

Test Scenario Clarified.
Client was backing up to the Original Domain. There was a management
class within that domain called 15yrarchive that I ran a test archive
to. 
I ran a query (select archives.node_name as "NODE_NAME",
substr(char(archives.archive_date), 1, 16) as "ARCHIVE_DATE",
archives.description as "DESCRIPTION", archives.class_name as
"CLASS_NAME"from archives group by
archives.node_name,archives.archive_date,archives.description,archives.c
lass_name) to show the management class that the client's archives were
associated with and received this:
NODEA               2005-03-02 11:18       Archive Date:
15YRARCHIVE       
                                               03/02/2005

I then moved the client to it's new domain (upd node nodea
domain=newdomain). I ran an incremental backup on the client and backup
objects rebound as they should have. I then ran expiration, and re-ran
the query. I received the following:
NODEA               2005-03-02 11:18       Archive Date:
15YRARCHIVE       
                                               03/02/2005

Same thing. 
The old domain will not be deleted just not actively used, I am
beginning to think that if I keep the old domain around the data will
keep the management class association that it was backed up with. 
The articles are contradicting themselves which is adding to my
confusion, from below:
"The Admin Ref manual says that ARCHRETention comes into effect when
either of the following conditions occurs:
- The management class to which a file is bound no longer exists, and
the default management class does not contain an archive copy group.
- The archive copy group is deleted from the management class to which a
file is bound and the default management class does not contain an
archive copy group."

>From this I can gather that if the old domain stays in place the data
will stay associated with the old management class. 

However from technote 1176515, 
"In case a megmt-class is not defined in the new Domain, the
grace_period (defined as ARCHRETention in the Domain-definition) would
apply."

Again any help you have on this would be greatly appreciated. 
Thanks,
Andrew  

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Sunday, March 06, 2005 12:25 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Management class Revamp

I think if you clarify the details of what you're doing, the management
class assignment of your Archive files will be clearer...

Your posting begins by saying that you have one TSM server; then
suggests that you have multiple TSM servers. And we don't know what you
mean by "I then moved the [TSM] server to the new domain...". I don't
understand what you're doing there. In the context of TSM product
discussions, "server" means the TSM server, and "client" means the node
interacting with that server. When posting to say that you did
something, please quote the command so that we may clearly understand
what was done.

The Admin Ref manual says that ARCHRETention comes into effect when
either of the following conditions occurs:
- The management class to which a file is bound no longer exists, and
the default management class does not contain an archive copy group.
- The archive copy group is deleted from the management class to which a
file is bound and the default management class does not contain an
archive copy group.

The Unix client manual stipulates:
When the server is unable to rebind a file to an appropriate management
class, the server uses one of two values to determine the number of days
to retain the file. If it is a backup version, the server uses backup
retention grace period. Archive copies are never rebound because each
archive operation creates a different archive copy. Archive copies
remain bound to the management class name specified when the user
archived them. If the management class to which an archive copy is bound
no longer exists or no longer contains an archive copy group, the server
uses the default management class. If you later change or replace the
default management class, the server uses the updated default management
class to manage the archive copy. If the default management class does
not contain an archive copy group, the server uses the archive retention
grace period specified for the policy domain.

See also IBM site Technote 1176515, "What happens to archive objects
when the node is bound to new domain?".

If the old domain definition survives and you didn't perform an Update
Node to reassign the node to a different domain definition, then status
quo.

    Richard Sims
********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.

If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.

If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.

Thank you.
********************************************