Re: Best way to restore database back to previous point in time

From: Max Powers <patrick.gunia_at_googlemail.com>
Date: Thu, 20 Mar 2014 05:42:20 -0700 (PDT)
Message-ID: <25d2948d-ac58-406c-8a5f-33214bbab0f1_at_googlegroups.com>


Am Donnerstag, 20. Mrz 2014 13:17:08 UTC+1 schrieb Max Powers:
> Am Donnerstag, 20. Mrz 2014 13:03:27 UTC+1 schrieb Preston:
>
> > patrick.gunia_at_googlemail.com wrote:
>
> >
>
> >
>
> >
>
> > > Hi everybody,
>
> >
>
> > >
>
> >
>
> > > I have a question concerning the best way to restore a database to a
>
> >
>
> > > previous point in time. My concrete intention is a little bit
>
> >
>
> > > different from the usual backup-purpose. As Im working on
>
> >
>
> > > performance testing Id like to have a fixed backup (or several
>
> >
>
> > > backups) which all have a fixed state in time. I load such a state,
>
> >
>
> > > run my benchmarks (which alter the database) and afterwards roll the
>
> >
>
> > > database back to the state before I started my test. So when I
>
> >
>
> > > restore my database I explicitely dont want any recovery (because I
>
> >
>
> > > dont want the database to return to the current state).
>
> >
>
> >
>
> >
>
> > What's the reason for not using flashback?
>
> >
>
> >
>
> >
>
> > --
>
> >
>
> > Preston.
>
>
>
> As far as I read about flashback its mainly used for quite recent backups. Maybe I got that wrong. Is it possible to use flashback providing it with a concrete backuppiece? Or does it require "automatic" backup-functionality?

I just read the documentation and it sounds like I first got it wrong and GUARANTEED restore points are what Im looking for...Ill give it a try and see, if it works out... Received on Thu Mar 20 2014 - 13:42:20 CET

Original text of this message