We got bit by the Systemobject expiration problem and when I went from 4.2.1
to 5.1.0.0 it failed. TSM server wouldn't even start. Gave me ANR9999
messages about unable to convert objects. I had to D/R my system back to
4.2.1, upgraded to 4.2.3.3 and ran the CLEANUP BACKUPGROUPS. Took 14-hours,
but freed up almost 34% in my database. Then I went to 5.1.0.0 and applied
the latest patch. I'm now up to 5.1.6.3 with the only problem being the
formatting of the Q PROCESS output with the ~'s and no line-feeds.

I would say if you aren't backing up any Win2k servers, you could go
straight up to 5.1.x.

Bill Boyer
"I haven't lost my mind -- it's backed up on tape somewhere." - ???

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Rushforth, Tim
Sent: Thursday, March 27, 2003 12:06 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Upgrade from 4.1 to 5.x questions


I'll throw in our experience if it helps anyone.

We just upgraded from 4.2.0 to 5.1.6.1 on W2K.  We were using subfile
backups at 4.2.0 and these were not expiring properly.  This was fixed at
5.1.5.x when I did a test migration to it.  When doing a test migration to
5.1.6.1 we found that there was a problem trying to recover any subfile
backups - client got an error (Error 8 getting backup row for object XXX).

The process we followed which seems to have worked was:
Upgrade to 4.2.3.3 - run expiration twice (cleans up sub file backups).
Upgrade to 5.1.0.0
Upgrade to 5.1.1.0
Upgrade to 5.1.6.2

Redo licences at 5.1.6.1.  Not sure if we needed to go to 5.1.0.0 and
5.1.1.0 before 5.1.6.1 (couldn't we just install 5.1.6.1 then install
licences from a 5.1.5 base version?) but this was according to the readmes.

Tim Rushforth
City of Winnipeg
-----Original Message-----
From: Marco Spagnuolo [mailto:marco AT UWINDSOR DOT CA]
Sent: Thursday, March 27, 2003 10:43 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Upgrade from 4.1 to 5.x questions


Steven,

We just upgraded a few weeks ago (AIX 4.3.3) and we were told by support,
to go from 4.2.1 to 5.1.0 to 5.1.5.  Make sure you do not start the server
until you've completed installing 5.1.5.  You will have to reset your
license file(s) as well.


Marco Spagnuolo
System Administrator
University of Windsor (IT Services)
401 Sunset
Windsor, Ontario N9B 3P4
(519) 253-4232 Ext. 2769
Email: marco AT uwindsor DOT ca