Re: Seeking 3.7.5 -> 5.1 upgrade advice..
TSM'er I agree with Wanda. Stick with plan A. When migrating from TSM 3.7.X to 5.1.X, the data base should be upgrade during the migration. When you try to start the dsmserv process and you recieve an error message complaining about the database, then issue the "dsmserv upgradedb" command. You can be kind of pro-active, you can issue "dsmserv upgradedb" and then start the dsmserv process. I have not experience any problems issuing "dsmserv upgradedb" when the data base is already upgraded. Unless I am one of the semi- lucky one. When I migrated from 3.7 to 4.2, one server the database got upgrade but for some restange reason another server I had to issue the "dsmserv upgradedb" commmand after there was a message complaining about the database. A good hint, before you start the upgrade. Make sure that you have a current backup of the TSM server, backup the volhist, and the devconfig. I would also backup the dsmserv.opt file, if you would have to start from scratch you would not have to try to remember what was set in the dsmserv.opt file. Speaking about Tivoli support, in the US. Have anyone call Tivoli support since June 2002? There was an e-mail or a notice that due to the call volume that they are experiencing that the tech's are calling the customer back. Basicly, you've got some waiting time. Sais Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag On, Prather, Wanda ([EMAIL PROTECTED]) wrote: > 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. > >
Re: Seeking 3.7.5 -> 5.1 upgrade advice..
>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? No, as long as the aggregate size of the installed database volumes on the new system is sufficient. > And are the registered nodes, users, volumes and automated commands > stored in a file which can be easily transferred to the new machine? Registered nodes and administrative users are stored in the TSM database. Information on volumes is also stored in the database. However, a TSM server can and should be configured to save some of the volume information to one or more flat files whenever the information is updated. Copying the flat file involved to the new system will make the database restore much easier. The path to the flat file is given in the server options file. A similar situation prevails for device definitions. However, you will probably not be able to simply copy the flat file of device definitions to the new system; you will probably need to edit the file to reflect the configuration differences between the two systems. Automated commands may or may not be in the database, depending on the exact mechanism used. Scripts and administrative schedules are in the database, but macros are not. After the database restore is done you may need to do some clean-up. If the disk storage pool volumes are different you will need to delete the old ones and define the new ones. If tape libraries and drives are different you will need to update the library and drive definitions. You should probably look at the discussion of server disaster recovery in the "Administrator's Guide". Server disaster recovery is essentially an urgent migration to new hardware.
Re: Seeking 3.7.5 -> 5.1 upgrade advice..
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@;EURORSCG.COM] Sent: Tuesday, November 12, 2002 11:27 AM To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED]
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: [EMAIL PROTECTED]
