Re: backup strategies

Only creating one database backup and then only archving the logs from then on is asking for trouble. Full online backups should be done more often than once unless you want to sit around for hours and hours while it churns thru archive logs. And if for some reason one is messed up youre really screwed.

Jason

"roblop" <roblop_at_friko2.onet.pl> wrote in message news:1qmL4.19219$hK2.380821_at_news.tpnet.pl...
>
> Jason Kratz napisa³(a) w wiadomo¶ci: <8dkhc9$4k9$1_at_flood.xnet.com>...
> >I'm curious as to what people are doing for backing up their database.
> >Currently we run in noarchivelog mode because we have the option to bring
> >down our database once a day. We currently back up the datafiles to
 another
> >machine which backs them up to tape later. We need to switch to
 archivelog
> >mode and I'm curious what people are doing in this mode. Are people
 copying
> >stuff to another machine and backing up to tape like we currently are?
 Are
> >you backing up to tape directly? When you run a backup in archivelog
 mode
> >are you bring a tablespace at a time into/out of backup mode? Are you
> >backing up all tablespaces or just a portion? Any ideas would be
 helpful.
>
>
>
> I never do it, so I write what I know
> If you work in archivelog you backup archived redo log - that mean oracle
> alone create archive log, default in %oracle_home%\database\archive. You
> must copy these files on tape, another disk etc. You must do full backup
 and
> after it you backup only archived redo log.
> Archivelog is good if your database must works non stop online. Export it
> good stuff to backup your data if you have a little amount of transactons
> during day.
>
> Roblop
>
>
>
>
>
>
Received on Wed Apr 19 2000 - 00:00:00 CDT