I agree with Nathan... option 1 is not possible.  I tried it going from AIX
to HP.

Option 2 depends on how much data you have.  We had about 60TB on our AIX
TSM Server in a ATL P3000 (DLT7000 drives).  I roughly calculated it would
take over six months of  tape to tape copies, running 24x7 with optimal
throughput, to migrate the environment to the HP.  BTW, you must do
export/import, because there is no other way to get the database info from
AIX to "other" platform.  Even if you could get all the database info
migrated, you probably would not be able to read the tapes from the AIX
environment on the Sun hardware.  It is not a purely hardware issue
(obviously you can transfer tar images between platforms), but has
something to do with the way TSM records data on the different platforms.
That's what Tivoli support told me.  My solution to this messy problem was
to keep the legacy AIX environment up until all of the data residing there
expires (one year, which will be coming up in about a month!).   I simply
started backing up all clients to the new TSM server, and we handle any
restore requests for older data from the AIX server.  Obviously you have to
have new server and library, but it looks like you have all the pieces....
as long as you did not have any plans for the legacy hardware.

Good Luck!
Robin Sharpe
Berlex Labs



                    Nathan King
                    <[email protected]
                    R.COM>        To:    ADSM-L AT VM.MARIST DOT EDU
                    Sent by:      cc:
                    "ADSM: Dist   Subject:
                    Stor Manager"        Re: new server migrations
                    <ADSM-L AT VM DOT MA
                    RIST.EDU>


                    09/16/02
                    05:11 PM
                    Please
                    respond to
                    "ADSM: Dist
                    Stor Manager"





Actually No.1 just flat out won't work. You can't backup the TSM DB on
one platform and restore to a different platform.

No.2 is your only option, in conjunction with import/export <-- that's
what the tools are for. Don't use server-server.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Nicola Albrecht
Sent: Monday, September 16, 2002 4:49 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: new server migrations


"Reiss David IT751 (ext-CDI)" wrote:

> I have several TSM servers that are going to be replaced with
> new-beefer TSM servers.  Right now the TSM servers are running on old
> RS/6000 boxes running AIX 4.3.3 with Breece Hill Q47 libraries with
> DLT8000 tapes drives in them. The new TSM Servers are going to be Sun
> boxes running Solaris 2.8 with ADIC Scalar 1000 libraries with LTO
> drives.
>
> The issue... I want to keep my current TSM data, as much as possible
> anyway. There seems to be two ways too do this.
>
> 1. On the old RS/6000 backup the TSM database to tape.  Connect the
> old Q47 library to the new Sun box, and restore the TSM database.
> Then, migrate the data via the directly attached SCSI drives from the
> old library to the new library.  Remove old library and beat it to
> death with nearest sledgehammer.
>
> 2. Bring up the new Sun box as a brand new TSM server, define
everything
> from scratch.   Then...and here lies the heart of my question, use
> Server-to-Server stuff to get old data from old Rs/6000 server to new
> one. I know I can push the data doing this... but could I push it in a

> logical manner so that it gets associated properly with what will be
> the node definitions on the new server?
>
> I don't like the #1 option because of all the hardware moving things
> around and such.  I would have to visit the places the server will be
> in.  We don't have people at these sites who would be comfortable just

> switching cables around and stuff.  So, sending them a whole new
> server... have them put it together, and once it is together I can
> just move on from there and do the data moving myself.
>
> Thanks,
>
> David N. Reiss
> TSM Support Engineer
> david.reiss AT swpc.siemens DOT com
> 407-736-3912

David, of the 2 options, number one is the only one that is going to
accomplish the association of stored data to node definitions on the new
server.  The second option (Server-to-Server) stores the data as archive
files on the new server and associates these archive file with a node of
the type server (old server).  Not what it sounds like you want.

Another option could be exporting the data, then importing to the new
server.

Nici
--------------------------------------------
Nici Albrecht
MDR Consulting & Education
1-210-860-4641