Thanks for the tips. I wasn't sure about the mis-matched release, but
suspected as much.

Unfortunately, we can't upgrade the existing server to anything higher due
to OS requirements, which is the main reason we want to move it (besides
being underpowered), so we will have to downgrade the replacement server.

The tape drives are already connected via SAN.

Can I assume the disk LZ needs to be completely empty since the target
system would have a completely empty storagepool?

I assume you mean a standalone DSMSERV RESTOREDB for which I need the
volhistory/devconfig file from the existing server (so I need to do a
"backup volhist" and "backup devconfig" first).

Sorry for the dumb and dumber questions but we have never done one of
these and this gives us a great opportunity to do a test DR.



Wanda Prather <wprather AT JASI DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/06/2008 12:22 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

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.