Moving a client to a new domain is as easy as "update node blah
domain=newdomainname".

It doesn't move any data, existing data stays in the same storage pools.
(The DESTINATION in the copy groups only affects NEWLY WRITTEN data, and you
won't be writing any new data with these retired nodes).

And you are correct that if the mgt classes/policies in the new domain are
different than the old,  you can get into a mess.

Just navigate in the GUI to the original domain, and pull down OPERATIONS ->
COPY.

TSM will let you copy the whole domain, including mgmt classes, copy groups
and all, to a new domain with a different name.  Then update the client to
that domain.

Now if your "retired" clients are in many domains now, to get around the
policy issue you may want to create a shadow domain for each one.
Domain1 - RETIRED_domain1
Domain2 - RETIRED_domain2

etc.

Wanda Prather
Johns Hopkins University Applied Physics Laboratory
443-778-8769

"Intelligence has much less practical application than you'd think" -
Dilbert/Scott Adams

-----Original Message-----
From: Richard Rhodes [mailto:rrhodes AT FIRSTENERGYCORP DOT COM]
Sent: Friday, June 11, 2004 10:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: How do you handle retired nodes?


How do you get the data into the new domain?
I didn't think you could move a node between domains.

Do you setup new mgt classes with just the RetainLast policy and
associate the node, in the new domain, to that mgt class?
(same with the archive data . . . needing a policy for it that's
the same as in the origional domain).



Rick





                      Nicholas
                      Cassimatis               To:
ADSM-L AT VM.MARIST DOT EDU
                      <nickpc AT US.IBM DOT CO        cc:
                      M>                       Subject:  Re: How do you
handle retired nodes?
                      Sent by: "ADSM:
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      06/11/2004 08:53
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






We have a domain called DISCO (short for Disconnected) where we move all
the "retired" systems.

We consider the node to have been deleted, so we keep the backup data for
the RetainLast number of days (from the copygroup settings).  Archive data
is kept until expiration deletes it.  We also change the node name, using
the data of "retirement" in the new name.  That forces the SysAdmins to
have to contact us to do a restore, but then we have "passwordaccess
generate" so they'd need a password reset anyway.

Nick Cassimatis
nickpc AT us.ibm DOT com

He who laughs last has a good backup.





-----------------------------------------
The information contained in this message is intended only for the personal
and confidential use of the recipient(s) named above. If the reader of this
message is not the intended recipient or an agent responsible for delivering
it to the intended recipient, you are hereby notified that you have received
this document in error and that any review, dissemination, distribution, or
copying of this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete the
original message.