Brecton Whitten wrote:
>
>   We are currently planning to move our TSM
> server from a 604e high node in an SP2 complex
> to an H50 standalone. Both platforms have the same
> number of CPU's and amount of memory ( 2 G ). The
> big difference being MCA vs. PCI. We are on TSM 3.7.4
> and are going to move up to TSM 4.1.2 ( AIX 4.3.3 ).

I just made basically the same move, from a similar high node
to an H80.  I just did the hardware move, and the upgrade from
ADSM 3.1 to TSM 4.1 will happen in a couple weeks.  Overall,
the process went pretty smoothly.

>   From combing the postings it appears that our best ( only ? )
> choice for this migration is to export each node to tape then
> import on the new platform. The problem we will have with
> this is that we only have 2 3590 drives native attached in a
> 3494. We will have to export everything , disconnect the drives,
> re-connect to the new platform, and then import. Our data is all
> on tapes, we don't have enough DASD to keep more than 1
> days data on disk ( therefore we also don't have enough to export
> to FILE ). If anyone has any input or 'gotchas' , I would much
> appreciate hearing from you.

It's all still AIX, so you don't need to do any export and import
of database or node data.  MCA vs. PCI attachment doesn't make any
difference for interaction with the data on either the DASD or the
tape drives.  If you were moving between AIX and Solaris or WinNT,
that'd be a different story.

In my case, I was moving from external RAID boxes on the high node
to a drawer of SSA on the H80.  On the high node, I migrated disk to
tape, deleted the disk pool volumes, and shut down the ADSM server.
I had already installed the same level ADSM code on the new box and
set up the corresponding filesystems, so I just had to FTP the
database and log volumes over, start up the server, and recreate the
disk pool volumes.

If you are moving your existing DASD to the new server as well, and
your TSM disk volumes are in a separate volume group on it, you don't
even need to mess with that.  You can basically export the volume
group(s), rewire the DASD and 3590s to the H50, and import the volume
group(s) there.  You'll still have to make sure the TSM code is
installed on the H50 and that you've got your server config files
(.opt, .dsk, nodelock) in place.

Other things to remember:
  - if you're LAN-attached to your 3494, make sure you define the H50
    as a LAN host on the 3494
  - don't forget to install Atape and atldd, and to define your library
  - make sure the H50 discovers the 3590s in the same order as the
    high node did (things should still work, but you'll be confused
    if /dev/rmt0 isn't the same physical drive you're expecting)

If you have further questions or would like the checklist I used for
my move, you can drop me a note directly...  Good luck!

=Dave

--
Hello World.                                    David Bronder - Systems Admin
Hello World.                                    David Bronder - Systems Admin
Segmentation Fault                                     ITS-SPA, Univ. of Iowa
Core dumped, disk trashed, quota filled, soda warm.   david-bronder AT uiowa 
DOT edu