Ok, Here's a copy of my upgrade process with some notes and an added license
note for those I emailed separately. Sorry I forgot about it till just now.
I did send it to quite a few people but am sending it to the list per
Kelly's request for archive purposes
Upgrading ADSM 3.1.2.55 on AIX 4.3.3 to TSM 4.1.2.0
3494 Automated Library with 4 3590-E1A's
I followed the document and did not have any problems. However, when I
installed I did end up installing the HSM client. I didn't bother to pick
and choose the list, maybe I should have. I just let it install everything.
I removed HSM later without any problems.
I did see the errors related to the Atape driver upgrade. I did not have to
stop/remove anything as it relates to the drives or library. SMIT took care
of it all during the update and TSM did not blink. I updated the Atape and
atldd at the same time.
On step 20 I noticed the volhist and devconfig files were not moved/copied
to /usr/tivoli/tsm/server/bin so I copied them. The dsmserv.dsk did get
moved so I was a bit bewildered as to why the other 2 weren't, given the
problems we see daily maybe I shouldn't have been. I did have to make
changes to dsmserv.opt, dsm.sys and dsm.opt to conform to the new
configuration.
Before I installed the 4.1.2.0 patch I brought up the server to make sure
everything was ok. I heard from Tivoli Customer support that some people
have had problems because they applied the patch, right after the upgrade,
without bring up TSM first. I didn't even want to ask what they were I just
wanted the correct procedure.
I did not have to upgrade the database, it happened automatically when I
started the server the first time.
I downloaded the .bff files for the patch, there were 8 of them. When I went
into smit to install them only 5 showed up on the list. I wasn't sure if
that's because some were installed already or some were part of the other
packages. So I can only guess if everything was installed properly...and
Tivoli help had no clue about it either, so what does that tell you
The TSM install did not completely remove the old ADSM directory structure.
There are 2 fairly large files in /usr/lpp/adsmser/bin, db.dsm and log.dsm.
These files are not in the new directory so I'm not sure if I will have
problems if I go through with renaming the directory before I try to delete
it. They may well be default files created when the ADSM server was
installed, but since IBM installed it I have nobody to ask.
I have everything working properly at the moment, or so it seems. My only
worry is, will the server come up properly from a cold boot, even though
inittab was modified with the new install. That will definitely happen in
the future, it's just a matter of when. The last time that happened I lost
every one of my TCP/IP settings and had to remove everything and reinstall
and reconfigure all of it. I was dumbfounded at that.
License note: The instructions in the Tivoli Storage Manager Quick Start
Guide for 4.1 states the following when installing the licenses:
register license file=mgsyslan.lic number=10
This does not work since the name of the license files are 10mgsyslan.lic,
1mgsyslan.lic and 50mgsyslan.lic. This holds true for all the other licenses
from what I can see. I ran this:
register license file=10mgsyslan.lic number=10 and got 100 licenses
registered. So you'll have to be careful with those obviously. If I would
have chosen 1mgsyslan.lic I would have been ok. I needed the 100 licenses
anyway.
Good luck...
Geoff Gill
NT Systems Support Engineer
SAIC
Computer Systems Group
E-Mail: [EMAIL PROTECTED]
Phone: (858) 826-4062
Pager: (888) 997-9614
UPGRADE INSTRUCTIONS
1) Use the BACKUP DEVCONFIG command to backup the ADSM
"Device Configuration" file to an alternate location
(assuming that you have one defined).
For example: BACKUP DEVCONFIG FILENAMES=/tmp/devconfig.bak
NOTE: The 'QUERY OPTION' command will show the DEVCONFIG option,
if defined, which will identify the current location of
this file.
NOTE: If you do not have one defined, please define it now by
adding the following option to the dsmserv.opt file:
DEVCONFIG /my_directory/deconfig.out
and perform the operation outlined in this instruction.
NOTE: You can acquire much of the same information through
the "QUERY LIBRARY", "QUERY DRIVE" and "QUERY STG"
commands.
For example:
Q LIBRARY * F=D
Q DRIVE lib_name F=D
2) Copy the "Server Options" file, dsmserv.opt, to an alternate
location.
For example:
cp /usr/lpp/adsmserv/bin/dsmserv.opt /tmp/dsmserv.opt.bak
3) If you are also updating ADSM code for the client residing on
the same machine as the server, you should also the copy "Client
Options" file(s) to an alternate location. The default location
for these files on AIX is: /usr/lpp/adsm/bin
For an example (on an AIX platform):
cp
