On 9 jul, 16:31, Steve Howard <stevedhow..._at_gmail.com> wrote:
> On Jul 9, 10:24 am, "fitzjarr..._at_cox.net" <fitzjarr..._at_cox.net> wrote:
>
>
>
>
>
> > On Jul 9, 9:05 am, Alexander Skwar <alexan..._at_skwar.name> wrote:
>
> > > fitzjarr..._at_cox.net <fitzjarr..._at_cox.net> wrote:
> > > > An export is a logical copy of the object or objects exported at the
> > > > time the object copy began. It is not a backup, even in the loosest
> > > > sense of the word.
>
> > > What makes this a "non backup"? You can use an EXP dump to recover
> > > all the data, can't you? You'll of course just need to create an
> > > "empty" database before you can run IMP.
>
> > > Alexander Skwar
>
> > The inability to recover from a corrupt or lost/deleted data file. An
> > export simply cannot recover tablespaces or datafiles, only objects
> > within them, and only from the point in time when the object copy
> > began. Having to create a new database to restore data from an .dmp
> > file proves that exp is not a backup.
>
> > Of course you're welcome to prove me wrong.
>
> > David Fitzjarrell
>
> I think we have too strict a definition of "backup" at times. We have
> used exp (and now datapump) to take a single table backup (yes, I
> think that term is appropriate) when mass data changes will be made
> to it and we want to be able to go back to it at that exact point in
> time (without worrying about having enough undo to flashback the
> table). We like the way the table looks, have taken into account any
> constraints, and a quick and dirty export allows us to put it back to
> that point with a minimum of fuss/muss.
>
> In that sense, yes, it is a backup for us.
>
> Regards,
>
> Steve- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -
Export is NOT a backup. PERIOD
Anyone who thinks export is a backup doesn't deserve to be a DBA, and
should be directed to the door asap.
--
Sybrand Bakker
Senior Oracle DBA
Received on Mon Jul 09 2007 - 09:35:23 CDT
