And, if you want the move to be seamless on the client end change the IP
address and host name on the new box to match the old box (this is what
I've done).  This will enable you to skip step 5 below.  However I must
add that before you run a DB Backup after step 1, empty out your
diskpools and remove them from TSM.  Then when you restore your DB, you
can redefine them on the new box.  This will cut down the startup time
after the restore, as TSM Will be looking for the storage pools.

If you are afraid to upgrade on the old box, setup the new box with the
new OS and the same version of TSM on the old box.
        1.  Backup the db (after emptying and removing the diskpools) on
old box.
        2.  Change host name and IP address of new server to match old
(after shutting down the old server).
        3.  restore the db on new box, and redefine disk storage pools.
        4.  Make sure all is well, and then halt TSM.
        5.  Perform in place upgrade to 5.5.

I've tested these steps in AIX, and they worked fine, but YMMV.  I'd
make sure to run a couple of tests on spare hardware before you go live
with it to make sure its going to fly.

See Ya'
Howard
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Wanda Prather
Sent: Tuesday, February 06, 2007 11:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Recommendations/suggestions for moving a TSM
server

Just think of it as an opportunity for a DR test.

First, TSM does not SUPPORT restoring a TSM DB from a lower level TSM to
a higher level server.  ("does not support" means they don't test it.
I'm sure some people have gotten it to work, but the recommended way is
quick
anyway.)

But the recommended procedure is to

1) upgrade your old TSM in place from 5.3 to 5.5.   I haven't done it on
Linux, but on Windows and AIX the 5.3 to 5.5 upgrade is very quick and
straightforward.

2) run a DB backup  (not unload)

3) move your tape drive connections to your new TSM box & configure

4) RESTORE the TSM db to your new box.

5) Switch your IP addresses/DNS alias or whatever so your clients point
to the new box.

Your DR recovery is complete!

There are other things you can do, like running the backup to disk
instead of tape if you have SAN connections to the disk, or import the
disk with the DB to the new system, depending on your hardware config.

But I prefer to do it as a DR drill, if only to give the instructions a
workout.  Especially good exercise if you have junior admins that have
never done it...



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Wednesday, February 06, 2008 10:58 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Recommendations/suggestions for moving a TSM server

I need to completely replace my old RH3 Linux TSM server (5.3) by moving
the contents to a newer, beefier, RHEL4 box. I also want to upgrade the
server to 5.5.

Of course, the replacement process needs to be completely transparent.
Basically a push-pull.

Can someone point me to docs/references/cookbooks to perform such a
task?

Is a DSMSERV UNLOADDB/LOADFORMAT/RESTOREDB the way to do this?

Currently, the replacement machine is up and fully running with V5.5
server running.