Re: Upgrade Time
Posted in 1993
Re:
> >we experienced similar errors when upgrading on our sun 690mp. what
> >it came down to was that the 4.0/4.1 instance was corrupted and we
> >ended up doing the dbexport/tbinit -i/dbimport. just out of
> >curiosity - how long does it take on your machine for 1gig to be
> >recreated from scratch.
> >ours took under 24 hours for 14gig.
>
> The database is actually 550 MB in size : It took 5 hours to export,
> 5 hours to import and 3 hours to do a level 0 archive.
|
|Sounds like you ran to tape.
|
Nope - to an admittedly slow HP-IB disk over an admittedly slow
HP-IB controller which has five disks attached to it.
|In January we did an upgrade of about 1GB SE database to Online 5.0.
|We borrowed some disks for the occasion - in fact we took another
|engine's mirror to do it. I don't have data left from the export -
|although I remember it was fairly quick - 30 minutes or so. The
|two engines loaded from disk using dbimport (vs dbload which is
|faster) ran at ~550MB/Hours (6 minutes) (55 MB engine) and ~350/Hour
|(3 hours) (1GB engine).
|The drives in question:
|
| SE engine was on 4 eagle drives (Don't know the size).
| dbexported to a blitz (1.3GB)
| dbimported back to eagles.
|I don't have performance specs on these drives - so I don't know
|what affect this had. If I had to do it again - I would shut down
|all other engines except for the ones being imported - and max out
|the buffers for the importing engine then reset them after the
|import. I would also preferred to have re-written the import SQL
|using dbload.
We shut down all other engines but only thought of maxing the buffers
after the import had already been running for a couple of hours -
would this not help the export run faster too ? (We tend not to have
spare disks lying around so couldn't try any other disks)
|We did a number of things to make it faster at the time - but were
|somewhat limited by the conversion script.
Next time we'll run a tbcheck on the database before we start and
if the normal procedure doesn't work we'll call in Informix support
and let them sit around for 13 hours :)
Cheers,
Richard Ridley