Restoring an old data base (3.7.5) to a new level of the server (5.1) SHOULD
work but it isn't guaranteed.
That is, Tivoli doesn't test that process, and if it doesn't work, they
probably won't fix it. And you will be going up SEVERAL levels of code. So
unless you can find someone else who has done it going from 3.7 to 5.1, on
Solaris, I recommend you stick with plan A, and upgrade in place. If you
have problems with that, Tivoli support will be able to help you.
Then you can move the DB to your new server.
-----Original Message-----
From: John N. Stacey Jr [mailto:john.stacey AT EURORSCG DOT COM]
Sent: Tuesday, November 12, 2002 11:27 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Seeking 3.7.5 -> 5.1 upgrade advice..
Hello,
I would really appreciate some advice on how to proceed with an
upgrade we are planning.
Currently, we are running TSM version 3.7.5 on an Ultra 10/Solaris 7
Our plans are to upgrade to 5.1.x on a Sun Ultra Enterprise 2/Solaris 8.
I am currently trying to figure out if it would be easier to upgrade the
current 3.7.5 server to 5.1 which will automatically convert everything
to 5.1 and then move the newly converted database and other needed files
to the new server which would have 5.1 already installed and running on
it.
Or, would it be easier to restore the 3.7.5 database from tape to the
newly configured 5.1 server and run an UPGRADEDB command to bring the
database up to the current level?
If the second path is the best, does the database have to have the same
physical path on the disk as the first server?
And are the registered nodes, users, volumes and automated commands
stored in a file which can be easily transferred to the new machine?
Thank you for any help you can give.
-john
_________________________________________________________________
John N. Stacey Jr. * Information Technology
Euro RSCG MVBMS Partners
* 350 Hudson St. * New York, NY 10014
Ph. 212.886.4369 * Email: john.stacey AT eurorscg DOT com
|
