I did an 'over the network' upgrade from the 5.5.4 server to the 6.2.5.0 one, 
no sweat. Of course, being the man that I am, I steered clear of any GUI that 
IBM has provided. Your plan will most likely work, but why bother with TSM v5 
on the new box? Either dump the db to tape on the old one or transfer via IP….

On 14 jun. 2013, at 16:17, Zoltan Forray <zforray AT VCU DOT EDU> wrote:

> I am scheduling to do the above and want to make sure I am not missing
> something, especially since the upgrade guide is a little confusing.
> 
> Current config - RedHat 5.9, TSM 5.5.6.100
> New config - RedHat 6.4, TSM 6.3.3.200
> 
> What I am proposing (all done on the new, virgin server)
> 
> 1.  Install 5.5.7 server and server upgrade
> 2.  Backup DB, devconfig and volhist on 5.5 server and halt/shut down
> 3.  Restore 5.5 server DB backup using last devconfig and volhist
> 4.  Install 6.3.3
> 5.  Run dsmupgdx process which does the UPGRADEDB, EXTRACTDB and then
> configs and loads the new DB
> 6.  Switch over network connections/config
> 
> The last version of the upgrade book I have has you going through the
> upgradedb and extractdb manually but then when you run the dsmupgdx is does
> it all over again......
> 
> Am I missing anything?
> 
> FWIW, next up is replacing my 6.1 server....fun.....
> 
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html

-- 

Met vriendelijke groeten/Kind regards,

Remco Post
r.post AT plcs DOT nl
+31 6 24821622