>Just make sure you have plenty of archivelog space for transactions which
>hit the database during the backup.
As I understand it, this was a major reason we don't do this but use the
"big backup area" approach (which I proposed in "part I").
I'm not an Oracle type, but the guy who put this together here is
very good. And we've "tested" (well, OK, the thing crashed and we had
to recover :-) the result -- several times.
>Now, if you want some redundancy *and* faster backups then you could put
>the database on a raid 1 mirror. When it comes to do the backup, break the
>mirror and mount the broken mirror somewhere. ...
How does the guarantee the disks in the mirror are up to date, i.e.
logically consistent from Oracle's point of view?
This technique comes up once in a while for normal backups, too, and
it's never made any sense to me. It won't work any better than what dump
(or tar, in some cases) does now.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
