We are about to upgrade a server from 3.1 to 4.1 along with switching
libraries and media. The media change isn't that bad we will be going from
3590 base tapes to extended tapes along with going from 3590 B1A's to E1A's.
Rather than loading 3.1 on the new box and restoring the db then migrating
to 4.1 the sequence I am thinking about is to:
On the old server AIX
Disable sessions
drain disk pool
Mark all tapes readonly
Use move media to put tapes into overflow location
Document db, logvol and diskpool files
backup db
copy dsm.opt, dsm.sys, volhist, devconf
halt server
On new server AIX
format db, logvols and diskpool to size documented
dsmserv restore db
dsmserv upgradedb
change devclass for new drives
create new tapepool with extended tapes
point disk migration to new tape pool
enable sessions
This should allow me to access the old tapes manually( I don't have enough
cells to suppport the 3590 base and extended tapes) along with being able to
copy the base tapes over in an organized manner. I can also upgrade the
clients to the new level code in an organized manner. This leaves me with a
quick fallback if there are problems,all I should have to do is checkin the
libvols.
The old library and server will disappear quickly after the upgrade so I
will not have the luxury of server to server nor will I be able to bring the
other library over to the new server. Your comments on the above sequence
are most welcome. Thanks
