This is from memory, so bear with me... For AIX server 3.7.x to 4.1 upgrades: Check OS patch levels against required levels in the release/patch README Check device driver levels against the required levels in the release/patch README Make sure your copystgpools are current. Do a BACKUP DB type=full
Down TSM server process and stop all instances of dsmadmc, dsmcad, dsmc, dsm and dsmserv For the truly paranoid: Create a fresh mksysb Create backup copies of the following files in /usr/tivoli/tsm/server/bin device config file volume history file dsmserv.dsk dsmserv.opt Mount 4.1 installation media, install using smitty (The README has the appropriate options to use). Verify startup scripts - (If you use some variations of externally managed libraries, the startup sequence may need to be changed from 3.x to 4.x due to some timing issues at startup - though if it works, don't break it ;)) Reboot the AIX box so the bosboot changes will be in effect. (this may not be strictly required, but it gives me warm fuzzies..) Don't be alarmed if the TSM startup time is slightly longer on the first startup - an UPGRADEDB is automagically run. Once the TSM server has started, log in and verify your configuration. Repeat the above steps as your paranoia dictates for the next patch/release level you desire... The licensing issue with 4.1, if I remember correctly, was that certain levels of the 4.1 release would not allow you to re-use a license file - TSM ships with a 1, 5, 10 and 50 count license file for various things - 10mgsyslan.lic is the 10 license file for managed LAN nodes. In those levels of 4.1, you could only have 66 licenses active without some sort of magic. Everything still worked, you just got these annoying messages in the activity log constantly. This issue was fixed in 4.1.5.0 I believe, maybe earlier. I'm sure I left several critical steps out, everyone jump right in and correct me please... -----Original Message----- From: Farren Minns [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 3:31 AM To: [EMAIL PROTECTED] Subject: Re: Migrate Install 3.7 to 4.2 any Notes? Hi George I am soon to be doing the very same upgrade. I'm running TSM Server 3.7.3.8 on a Solaris box. Did you go directly from 3.7.x.x to 4.1.x.x and what exact patch level did you upgrade to? Also, I know this has been questioned before, but I'm a little confused about the problems people were having with the licenses. Unfortunately for me, I was not present when our TSM server was set up and I did not see the licenses being set up. Sorry for being such a novice. Thanks ever so much Farren Minns - Trainee Solaris and TSM system admin John Wiley & Sons Ltd George Lesho <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 09/04/2002 22:41:52 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Migrate Install 3.7 to 4.2 any Notes? I saved off all config files, the accounting log and a bunch of other things. I backed up the db and was ready for the worst. I needed nothing... it was very straightforward. The licesnse files need to be installed properly. I would highly recommend latest ATAPE driver and that is about it. I didn't need any of the stuff I had saved off... no config changes at all when upgrade was complete... only had to redo licensing. George Lesho System/Storage Admin AFC Enterprises Craig Simpson <[EMAIL PROTECTED] To: [EMAIL PROTECTED] COM> cc: (bcc: George Lesho/Partners/AFC) Sent by: "ADSM: Subject: Re: Migrate Install 3.7 to 4.2 any Notes? Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 04/09/02 04:53 PM Please respond to "ADSM: Dist Stor Manager" On AIX 4.3.3. Any notes you have would be great. We are running an IBM 3494 Librairy with 3590 drivers. Craig -- Craig Simpson "Jolliff, Dale" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "ADSM: cc: Dist Stor Subject: Re: Migrate Install 3.7 to 4.2 any Notes? Manager" <[EMAIL PROTECTED] .EDU> 04/09/02 03:27 PM Please respond to "ADSM: Dist Stor Manager" What OS? I just did some 3.7.4 to 4.2.x for AIX. It's pretty straightforward for the server code itself, but watch out for changes in the startup scripts if you use an externally managed library. -----Original Message----- From: Craig Simpson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 3:15 PM To: [EMAIL PROTECTED] Subject: Migrate Install 3.7 to 4.2 any Notes? Doing a Migrate Install from 3.7 to 4.2.11. Do anyone have any notes on doing this? Any hang ups that they ran into? Anyone have issues with the following: Schedules Tuning New features that might be on by default How much configuration do we lose Lisenceing Thanks, Craig -- Craig Simpson
