Richard,

You might be able to use the mergefilespaces=yes option on the import to
avoid the filespace name juggling Wanda mentioned in her caveat.

Alex Paschal
Freightliner, LLC
(503) 745-6850 phone/vmail

-----Original Message-----
From: Prather, Wanda [mailto:Wanda.Prather AT JHUAPL DOT EDU]
Sent: Tuesday, October 21, 2003 7:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: What to do with archives when deleting a client


No, there isn't any way to archive data so that it isn't attached to a
particular client.

And there isn't really any reason you can't leave the archives attached to
the old node name; once the old node name has been idle for 30 days, it will
drop from your license count, it doesn't cost you anything just to let it
sit there.

If you really want to move the data to another client, there is a hokey way
to do it, requiring some work:

Assume the client that is going away is called SOURCE, and the client you
are keeping is called TARGET.

1) If SOURCE and TARGET aren't in the same domain, make sure that TARGET has
the same management class names (for archives) as the SOURCE domain.
2) On the TSM server, rename node TARGET to OTHER.
3) On the TSM server, rename node SOURCE to TARGET.
4) EXPORT the archive data from what is now TARGET:  EXPORT NODE TARGET
FILEDATA=ARCHIVE ...
5) Rename everybody back to their original names.
You now have SOURCE=SOURCE, and TARGET=TARGET, but the archive data from
SOURCE was exported under the name TARGET.
6) IMPORT the data.

That will work if the TARGET machine doesn't already have archives with the
same filespace names.
If it DOES already have archives with the same filespace names, you have to
play the same games with the filespace names before doing the EXPORT.




-----Original Message-----
From: Richard Rhodes [mailto:rrhodes AT FIRSTENERGYCORP DOT COM]
Sent: Tuesday, October 21, 2003 9:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: What to do with archives when deleting a client


We have systems where we have archived data where I can see the life of the
archive data
will far out lasting the client system itself.

So, say you have a client system that is being removed from service.  It's
ok to delete
all backups for the client and remove the client from TSM.  But, the client
has archive
files that you want to keep.

Q)  Short of restoring the archives and re-archiving from a different
client, is there
anyway within TSM to move the archives to a different client?

It funny, but I've often thought that there should be a way to archive data
so that
it isn't attached to any particular client system . . . .maybe there is . .
. .

Thanks!

Richard Rhodes








-----------------------------------------
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.