Re: BACKUP STRATEGY

Muli Koppel wrote:
>
> have you tried the direct=yes buffer=1024000 flags?
>
> yours,
>
> Muli Koppel
>
> qutub_at_hotmail.com wrote:
>
> > Hi ,
> >
> > I am in the stage to design the backup strategy for our 30GB database
> > running with cluster machines with Oracle parallel server. Database is
> > required 24 hours , seven days a week.
> >
> > I am planning for the implementation of HOTBACKUP, do i need logical
> > backup (export) of the database? if yes , what is the best way to
> > implement for my enviroment. A complete export takes 8 hours daily.
> >
> > Thanks
> > ABD
> >
> > -------------------==== Posted via Deja News ====-----------------------
> > http://www.dejanews.com/ Search, Read, Post to Usenet

DANGER! You must not confuse export with backup.

The normal mode of export is single table consistency. This means that the exported table is a snapshot as of a single time. However, the next table exported is a snapshot as of a later time! So, if any updating is allowed, your tables are not guaranteed to be consistent with each other. One solution is to exclude all users during the export, but this does not fit the 7x24 requirement.

The other choice is to code CONSISTENT=Y in the export parameters. This is the equivilent of 'set transaction read only'. All the tables will be exported as of the same point in time. But, you better have a humongous rollback segment!

The other point about export/import: there is no forward recovery from log files possible with imported tables. What you import is what you get!

With these limitations, what does export bring to your situation? If its a good thing for you, use it. Received on Mon Nov 24 1997 - 00:00:00 CST