RE: What am I missing with my RMAN archivelog backups
- From: Alfredo Abate <alfredo.abate@xxxxxxxxx>
- To: Michael Schmitt <mschmitt@xxxxxxxxxxxx>
- Date: Fri, 2 May 2014 12:40:13 -0500
Any difference in how you are connecting to RMAN (catalog versus control
file) in your scheduled backup jobs versus manually?
Alfredo
On May 2, 2014 12:22 PM, "Michael Schmitt" <mschmitt@xxxxxxxxxxxx> wrote:
> Hi Alfredo,
>
>
>
> I only run the following crosscheck commands on a schedule as part of the
> script:
>
>
>
> crosscheck archivelog all;
>
> crosscheck backup device type disk;
>
>
>
> I just ran a manual "crosscheck backup device type sbt_tape;" now.
> Everything came back as available and it didn't change the obsolete info at
> all.
>
>
>
> Thanks,
>
> Mike
>
>
>
> *From:* Alfredo Abate [mailto:alfredo.abate@xxxxxxxxx]
> *Sent:* Friday, May 02, 2014 12:01 PM
> *To:* Michael Schmitt
> *Cc:* ORACLE-L
> *Subject:* Re: What am I missing with my RMAN archivelog backups
>
>
>
> Are you performing a crosscheck at any point?
>
>
>
> Alfredo
>
>
>
> On Fri, May 2, 2014 at 11:57 AM, Michael Schmitt <mschmitt@xxxxxxxxxxxx>
> wrote:
>
> Hello,
>
>
>
> I am trying to figure out why my rman archivelog backups to tape are not
> getting removed. This worked correctly at some point, so I am not sure if
> it was when we changed scripts or version changes with oracle that I did
> not catch at the time. This example is for an 11.1.0.7 instance which was
> created recently, but we are running all versions from 10g to 11204. I
> have not looked into it enough to tie the behavior to a certain version
> yet. I am listing output of most of the information that I think is
> relevant.
>
>
>
> RMAN> report obsolete; <--- *This is showing nothing found as obsolete.
> I would expect my archivelog backups to show as obsolete based on the
> information below*
>
>
>
> RMAN retention policy will be applied to the command
>
> RMAN retention policy is set to recovery window of 7 days
>
> no obsolete backups found
>
>
>
> RMAN> list backup summary; <------ *We have archivelog backups that are
> older than our oldest database backup. I would expect these to report as
> obsolete, or to at least get caught in the delete obsolete*
>
>
>
> List of Backups
>
> ===============
>
> Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
>
> ------- -- -- - ----------- --------------- ------- ------- ---------- ---
>
> 131 B A A SBT_TAPE 06-MAR-14 1 1 NO
> TAG20140306T132627
>
> 132 B A A SBT_TAPE 06-MAR-14 1 1 NO
> TAG20140306T132627
>
> 175 B A A SBT_TAPE 07-MAR-14 1 1 NO
> TAG20140307T000012
>
> 283 B A A SBT_TAPE 07-MAR-14 1 1 NO
> TAG20140307T080324
>
> 284 B A A SBT_TAPE 07-MAR-14 1 1 NO
> TAG20140307T080324
>
> 335 B A A SBT_TAPE 07-MAR-14 1 1 NO
> TAG20140307T090010
>
> 375 B A A SBT_TAPE 08-MAR-14 1 1 NO
> TAG20140308T000013
>
> ...........................
>
>
>
> RMAN> show all; <---- Retention is set to 7 days and default device type
> is tape
>
>
>
> RMAN configuration parameters for database with db_unique_name XXXX are:
>
> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
>
> CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
>
> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
>
> CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
>
> ........
>
>
>
> * All of the database backups are full level 0 backups.
>
>
>
> * Archivelogs are backed up with the following command " backup format
> 'XXXX_ARCH_%M%D_%u.bkp' archivelog all not backed up 3 times;"
>
>
>
> Thanks in advance for any help
>
>
>
>
>
>
>
Other related posts:
