Re: Importance of archivelog : searching for good document

From: MARK BRINSMEAD <mark.brinsmead_at_gmail.com>
Date: Tue, 10 Mar 2015 14:08:50 -0400
Message-ID: <CAAaXtLBha0ibVX5AWj=+YKJb25vMO4W+Q7ayi7EYarNr5WZCFg_at_mail.gmail.com>

Wow. I did not think it was *necessary* to argue in favour of archive-logging. :-)

The main points are already covered: PITR, online backups, dataguard, logminer.

Perhaps a couple finer points:

• When you have archivelogs (archivelog backups), your database backups are self-redundant. Need to restore the database from backup, but you're missing a tape? NO PROBLEM -- just restore from the PRIOR backup, and roll forward with archivelogs. (To that end, archivelogs are *so* valuable, I still recommend that you always back them up *twice*, preferably to separate media pools.) Your backups are also recoverable for (much) longer than they would be if you relied on retaining only online redologs.
• Some people see archivelogs and logminer as a proxy for (or maybe complement to) auditing.

On Tue, Mar 10, 2015 at 1:56 PM, Hans Forbrich <fuzzy.graybeard_at_gmail.com> wrote:

> On the flip side:
>
> If you have the luxury of a cold backup, say daily or weekly, and you have
> sufficient disk space, you can keep enough online redo logs to keep your
> environment safe between backups. Then, if your backup is complete, plus
> all of the related redo, you should be able to accomplish a point in time
> recovery. Sort of a PITA PITR. Rare, but certainly possible.
>
>
> Some of the benefits of archive logs:
> - as noted, allows live backup
> - supports traditional PITR
> - fallback for standby database log shipping, especially data guard
> - historical data mining using log miner (or golden gate?)
>
> I'm sure others will add more
> /Hans
>
>
> On 10/03/2015 11:39 AM, kyle Hailey wrote:
>
>>
>>
>> Does any one know of a good document or blog that argues strongly for
>> archive log?
>>
>> Most of the stuff I see says you can use archive log if you want but you
>> don't have to and if you don't it just means you have to take cold backups
>> and can't do point in time recovery
>>
>> The way I look at it is point in time recovery is crucial because you
>> will corrupt your database at some point without archive log it's just
>> matter of time, a ticking time bomb.
>>
>>
>>
>> - Kyle
>>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Mar 10 2015 - 19:08:50 CET