Hello,

Yes, of course, it will be better to use a backup DB to restore but:
Our DB is 62GB big and the real used space is about 30GB. This crash was a
good reason (not the exact term but my english is poor) to reorganize the
DB. Otherwize, there is no way to reduce the DB once the space has been
used.
The last Full Backup is 2 weeks old and there are 26 incr. The full of
last week was missed. (problems are never coming alone). I was thinking it
should take too much time to read back all the full and incr cartridges.
(weekly full backup takes 6 to 7 hours to complete). Now, it seems that
LOADDB may be slower as RESTORE DB but I'm not sure. It is to be tested. The
problem is I have disk space enough for only one 62GB DB ;-).

Thanks a lot for your ideas.

Francis.

PS. After 10 hours, 1/10 of the DB is reloaded.......

> ----------
> From:         Steven P Roder[SMTP:tkssteve AT REXX.ACSU.BUFFALO DOT EDU]
> Sent:         maandag 22 november 1999 15:14
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Help: ANY HINTS TO SPEED UP LOADDB are welcome
>
> > Francis,
> >
> > Do you not have an up to date DB backup that you could use instead ?
> >
> > Angie Hopkins
>
> Yes, that would be my question too.  My other question would be why you
> were using a recovery log that was at the absolute maximum size?  Once you
> are back online, I would stronly recommend reducing the size of your
> recovery log, so that the next time, you have room to extend it, saving
> 3-5 days of downtime...
>
> Steve (unVMix Systems Programmer/Dude) Roder
> (tkssteve AT ubvm.cc.buffalo DOT edu | tkssteve AT acsu.buffalo DOT edu | 
> (716)645-3564
> ,
>    | http://ubvm.cc.buffalo.edu/~tkssteve)
>