Re: [ADSM-L] Moving TSM instance to new hardware

I've also done it this way, treating it as a DR exercise and restoring the DB, 
not difficult at all.
Restoring DB very well documented in the V6 cmd ref. 

But I realize you wanted to do it without restoring the DB, just importing the 
VG.

I could be wrong, but I think it's more complicated now than in V5 and you 
can't just move the DB over by importing the volume group.
If you are installing the code on a new V6 system, you're installing DB2, but 
it doesn't know about the DB you'll be importing in the volume group. 
I'm sure there are some DB2 commands you can do to register that DB on the new 
server, but I don't know what they are.
Any DB2 wizards out there with suggestions?

W

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
James Choate
Sent: Wednesday, April 09, 2014 4:28 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Moving TSM instance to new hardware

I have done this recently on Windows, AIX and Linux.
We treated it like a DR exercise and basically installed TSM (same version) on 
new hardware.

Made sure I migrated storage pools to 0.  
Ran a prepare. 

Put the volhist, devconf, dsmserv.opt in the proper place.
Took care of zoning with the tape library Allocate new storage for 
DB/activelog/archlog (we kept paths to these the same as old server, but used 
new storage just in case)

Restore DB

***the above order may vary, but I think you get the point.  The important step 
is next.

Go to lunch.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Kevin Kettner
Sent: Wednesday, April 09, 2014 2:02 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Moving TSM instance to new hardware

I'm running 6.3.4 server on AIX. The server is getting to the end of it's life 
so we're planning to replace the hardware. I have just about everything related 
to TSM installed on SAN disk, besides the stuff that gets installed in /usr. 
The last time I did a hardware swap was with TSM 5.5. The basic procedure was 
this:

 1. Install the TSM software(exact same version) on the new hardware.
 2. Shutdown TSM on the old hardware.
 3. Export all volumes.
 4. Rezone all SAN storage.
 5. Import volumes on new hardware.
 6. Start TSM.

I did that several times and never had any problems.

So I'm wondering if anyone has done something similar with TSM 6.x?

Thanks!

-Kevin