Oh lordy be! You really know how to ask for trouble! I hope your resume
is updated.

I would STRONGLY recommend NOT changing everything at the same time. If
something goes wrong, as it inevitably will, you'll never know where to
start looking for the problem. (Or, are you being given a week of
downtime for this?)

Break this into 3 separate projects:

1. Move to new hardware, keeping everything else the same.

2. Upgrade AIX from 4.3.3 to the latest 5.2 (with Maintenance Level 3!)

3. Upgrade TSM from 5.1.6.1 to 5.2.2.0

Steps 1 and 2 could be swapped and done in either order. But the
important thing here is you should approach this as three separate
projects. If something goes wrong at any of the three steps, you'll have
a much easier time figuring it out and recovering, in a reasonable
amount of time, and with reasonable chances of not destroying your TSM
database.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
==== A carelessly planned project will take three times longer than ====
== expected; a carefully planned project will take only twice as long.==


On Wed, 30 Jun 2004, Lawrence Clark wrote:

>Questions:
>1). Are the dsmsrv.opt compatible across 5.1 to a 5.2 TSM release
>2). Will the upgradedb auto-invoke when I attempt to bring up the 5.2 server 
>pointing to the old 5.1 database
>3). If not, where is it.....upgradedb is not found on the server. Would it be 
>explicitly invoked prior to bringing up the 5.2 server as in dsmc upgradedb?
>4). Are there any things that should be done prior to migration, such as an 
>audit db on the 5.1 TSM db
>
>My plan is below for the AIX environment. Any helpful comments would be useful:
>
>Upgrade TSM steps:
>
>Current setup:
>*        TSM Server Version 5, Release 1, Level 6.1
>*       AIX  4.3.3.0
>
>Migrating to:
>*        TSM Server Version 5, Release 2, Level 2.0TSM Server
>*       AIX 5.2.0.0
>
>All current storage of disk based volume groups and TSM DB is on SSA disk.
>
>Migration scenario:
>
>*       Stop all scheduled processes on old server
>*       Back up TSM db on old server
>*       Halt  both servers
>
>*       Move from old to new server /usr/tivoli/tsm/server/bin/
>o       Dsmserv.opt
>o       Dsmserv.sys
>o       Dsmserv.dsk
>
>*       Move from old to new server /home/root/tsmfiles/
>o       Devconfig.info
>o       Volhistory.info
>o       Inclexcl.list (for client)
>o       Dsm.opt (for client)
>
>
>
>*       Export SSA disk on current TSM server
>*       Import SSA disk on replacement server running TSM 5.2
>*       Verify all volume groups and mount points are set.
>*       Start new server (is upgradedb invoked?)
>
>
>*       Bring over tape libraries
>*       Recycle node and TSM server
>