Re: controlfile autobackup (was: Re: disaster recovery)

From: joel garry <>
Date: Tue, 20 May 2008 13:02:05 -0700 (PDT)
Message-ID: <>

On May 20, 12:14 pm, wrote:
> On Tue, 20 May 2008 09:25:57 -0700 (PDT), joel garry
> <> wrote:
> >On May 17, 9:55 am, wrote:
> >> On Fri, 16 May 2008 13:02:36 -0700 (PDT), Ben <>
> >> wrote:
> >> >now that we've lost the catalog, spfile, controlfiles, and everything
> >> >else. Is there a way to get the controlfile and spfile out of that
> >> >backup?
> >> If you didn't have controlfile autobackup on, which you didn't
> >> specify, shortly : NO.
> >I have a recently installed hp-ux with autobackup on.  It's
> >just idling along while I do app development on another machine.  This
> >thread made me take a closer look at the autobackup.  I check the
> >alert log, I see it is writing controlfile backups to specific files
> >in directories with each days date on them, makes sense since I'm
> >taking a full backup each day (I haven't set up a repository yet).  It
> >seems to be keeping a weeks worth of these directories, but I only
> >just noticed it only is keeping the latest controlfile backup.  Seems
> >not paranoid enough to me.  I have CONFIGURE RETENTION POLICY TO
> >The script as generated by the customization wizard is this:
> >$rman_script="backup device type disk tag '%TAG' database;
> >backup device type disk tag '%TAG' archivelog all not backed up;
> >allocate channel for maintenance type disk;
> >delete noprompt obsolete device type disk;
> >release channel;
> >";
> >Am I wrong to expect the delete obsolete to keep two of the
> >controlfile/spfile backups?  Or is it just also in the regular backup
> >files?
> >Looking at the rman log, I see what is happening:  It is backing up
> >the controlfile/spfile once for the archivelog backup, then once again
> >for the regular backup, then deleting all the others.  So it is
> >keeping two, from the same time - the log appears to have them before
> >and after the backup, but the unix time is the same (I assume because
> >rman must have closed the files at nearly the same time).

Correction, the two backups bracket the archivelog backup, since there is no activity on the db for now, that just takes seconds.

> >This seems strange, how should I be doing this?  Shouldn't I want to
> >have some spread of controlfile backup times, to avoid just
> >propagating a messed up one when restoring?
> >jg
> Joel,
> I can only investigate this for 9i. I don't think 10g has changed in
> this regard, so that should be OK. I ran into something strange today
> which I need to investigate anyway: my autobackups also seem to
> disappear, though my retention is 9 days.

That's why I said something, I figured either I missed something or there is a consequence one doesn't hear often about and many people might have misapprehensions, or issues waiting to blow, even. I haven't settled on window or redundancy yet.

Must be Frank is right, you do always just want the latest one, the doc I quoted to him may be misleading if there is only effectively one controlfile to choose.

> One question though:
> Do you happen to use backup optimization.

It's the default (off).

> I noticed using backup optimization in 9i you can only backup the
> archivelogs once, whatever you tell it to do. It begins to brag you
> already have a backup of the archivelogs.
> Sounds equally scary.
> The behavior with autobackup controlfile may be the same issue.
> The reasoning might be you have records of multiple backups in the
> controlfile anyway, so you should be OK.

Strange reasoning to me, given that only the controlfile has the records.


-- is bogus.
Received on Tue May 20 2008 - 15:02:05 CDT

Original text of this message