RMAN retention policies

We seek two retention policies for our backups. retention of 30 days for all backups on TAPE and 7 days of retention on all backups on DISK. If we define the retention at 30 policy, drive could not accommodate all the backups on disk at the same time, we need backups on tape for at least 30 days.

Any ideas?

You have a block of code in your script to delete obsolete backups... replace that with two orders (a global and one for the disc). You would still have 30 days retention policy

RMAN TARGET /.
CONFIGURE RETENTION POLICY TO RECOVERY OF 30-DAY WINDOW;
ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;
ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE SBT;
DELETE NOPROMPT OBSOLETE FORCE.
REMOVE THE FORCE NOPROMPT OBSOLETE WINDOW TYPE 7 DEVICE DRIVE RECOVERY DAYS.

Tags: Database

Similar Questions

  • Query on the RMAN retention policy


    Hi, I have my retention set to 2 redundancy policy

    I took 3 backups so far (2 sets of backup, 1 copy of the Image)

    When I check the obsolete report I get the following

    RMAN retention policy apply to the order

    RMAN retention policy is set to 2 redundancy

    Report of obsolete backups and copies

    Making key time filename/handle type

    -------------------- ------ ------------------ --------------------

    Backup 1 05-SEP-13 set

    Exhibit 1 backup /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp 13-SEP-05

    Backup 2 05-SEPT-13 set

    Exhibit 2 backup /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp 13-SEP-05

    Backup 3 05-SEPT-13 set

    Save the song 3 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp 13-SEP-05

    Backup 4 05-SEPT-13 set

    Save the 4-13-SEVEN piece. 05 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp

    Backup 5 27-SEPT-13 set

    Save the song 5-/home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp 13-SEP-27

    Backup the value 7 13-SEP-27

    Save the song 7 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp 27-SEP-13

    Archive newspaper 305 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc

    Archive newspaper 306 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc

    Archive journal 307 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc

    Archive newspaper 308 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc

    Backup 1,2,3,4 set elements are essentially equivalent to my older backup - so under a redundancy of the 2, I can see why it is obsolete

    5 and 7 were simply command file/SPFILE AutoSave backups and the 2 most recent backups of them have since been taken (backupset parts 9 and 10)

    Q. what happens if I wanted to restore the database to the 27/09? What control and SPFILE he would use (assuming that OBSOLETE files had been removed from the FRA)?

    If I have to restore the backup set removed in the FRA, Cross Check and restore the database using RMAN to 27/09?

    Q. Why are some today (10/10/13) archival newspapers marked OBSOLETE?

    Q. If I wanted to be able to restore the database for 2 days, is perhaps a policy of conservation of a day 2 Recovery window might be better than my current redundancy = 2 policy (associated with a daily backup)?

    any advice appreciated,

    Jim

    Yes, the BackupPieces names.

    A BACKUP of the LIST would show the content of BackupSets and BackupPieces.

    Hemant K Collette

  • retention policies different for RMAN

    Hi@all,

    on our DB with RHEL 6 and Oracle 11.2.0.3.0 Server, we create the following backup with RMAN:

    -every day at the level 0 backup 23:00

    -daily at 05:00, 11:00 and 17:00 level 1 backup

    I activated this retention policy:

    CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;


    Each backup is so obsolete after 7 days. We use the control file and catalog any recovery. We get backups so in front of the SLA.


    Now (in front of our physical disk space) I want to spend the retention policy to the following:


    -Fullbackups (level 0) should be obsolete after 7 days

    -incremental backups (level 1) should be obsolete after 2 days

    -arc. redologs should be obsolete after 7 days (I like to use LogMiner and especially I need newspapers in restoring arch in the last 7 days in our society)


    Is this possible in RMAN to set different retention for different types of backup strategies?


    Thanks for your help and best regards,

    David

    David_Pasternak wrote:

    I just tried to have a general question and explain with an example, so once again:

    I just want to know if I am able to set a different RETENTION STRATEGIES for various levels of backups.

    N °

    Now, if you want to know exactly how oracle will include in the scenario you are asking (how to do different types of backups behave in what concerns a retention of "redundancy" policy, I would suggest test you.)  I could knock out this test in 30 minutes approximately.  It would be good for your career (on many levels) for you to perform this test for yourself.

  • RMAN retention policy

    Hello everyone, I think to create a retention policy, but the problem is if I want to have the backup that ran daily from detention for 15 days and each backup run a monthly backup for a year which is the best option to set up the recovery window retention policy, because if I set with 365 days I'm going to keep daily backups for the whole year, suggest or advise

    Hello

    set the retention policy for 15 days (daily policy):

    RMAN > CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 60 DAYS;

    And add keep until 'sysdate + 365' monthly backup.

    RMAN > backup format incremental level 0 '% d.n0.%T.set_%s_%t' TAG data = 'BK_DATA_monthly_20150501' keep until 'SYSDATE + 365' opens a session;

    If you can make backup maintenance with delete obsolete;

    RMAN > remove force noprompt obsolete;


    It works with oracle 9i, 10g and 11g

  • Question on the implementation of the RMAN retention policy

    Version: 11 g
    OPERATING SYSTEM: AIX 5.3


    I intend to implement a differential incremental backup of my database. My strategy is
    Sunday -->     Level 0 backup
Monday -->     Level 1 backup
Tuesday-->     Level 1 backup
Wednesday-->     Level 1 backup
Thursday-->     Level 1 backup
Friday-->     Level 1 backup
Saturday-->      Level 1 backup

Again, the new weekly backup cycle starts
Sunday -->     Level 0 backup
Monday -->     Level 1 backup
.
.
    First script to perform the backup of level 0 - this script will be run by a cron job every Sunday morning 02:00
    ==================================================================
    run{
crosscheck backup;
crosscheck archivelog all;
crosscheck copy;
crosscheck backup of database;
crosscheck backup of controlfile;
delete noprompt obsolete device type disk;
}


run {
allocate channel ch1 device type disk;
backup incremental level 0 format '/u07/rman_backup/FULL_%d_%u' database tag "weekly_full";
backup format '/u07/rman_backup/RMAN_CTL%s:%t:%p.bkp' current controlfile;
--release channel ch1;
allocate channel ch1 device type disk;
backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' DELETE INPUT TAG "archivelogs");
release channel ch1;
}
    The second script for differential incremental backup at level 1 for the next 6 days. This script will run every day
    at 02:00 from Monday to Saturday by a cron job. I have 6 scripts like below, the only difference being the tag "Monday-level 1", "Tuesday-level1"... etc.
    =======================================================
    run{
crosscheck backup;
crosscheck archivelog all;
crosscheck copy;
crosscheck backup of database;
crosscheck backup of controlfile;
delete noprompt obsolete device type disk;
}


run {
allocate channel ch1 device type disk;
backup incremental level 1 format '/u07/rman_backup/RMAN_DBF_%s:%t:%p.bkp' database tag "Monday-level1";
backup format '/u07/rman_backup/RMAN_CTL<%s:%t:%p>.bkp' current controlfile;
--release channel ch1;
allocate channel ch1 device type disk;
backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' delete input tag "archivelogs");
release channel ch1;
}
    Question1.
    I want to as backups to become obsolete and deleted as below
    At the end of every week's backup cycle.ie Just after taking a new Sunday's level 0 backup, 
i need all the old level 1 and level 0 backups from the previous week to get deleted.
    The setting persist following should do the trick. Right?
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    Question2.
    Since
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    is defined. When the new backup cycle begins next Sunday, RMAN should delete the backup of level 0 of last Sunday. Ideally, RMAN should remove all its ' (child) of level 1 backups to Saturday because it makes no sense to keep these level 1 backups when its parent 0 level was obseleted and deleted. RMAN removes level 1 level 0 backup child deleted backups Sunday (when the new backup cycle begins)?

    Question3:
    Suggestions that you guys have about the scripts above?

    Published by: resistanceIsFruitful on October 30, 2009 06:04

    You have answered your question yourself in your question, when you understand

    Ideally RMAN should remove all its ' other (children) level 1 backups to Saturday because it makes no sense to keep these level 1 backups when its parent 0 level was obseleted and removed_

    Yes indeed RMAN done, did you check it yourself?

    Khurram

  • vCenter data retention policies when does it take effect

    I'm not enough on my space of vcenter. If I set the data retention policy to 6 months, should I immediately remove tasks and events more than six months, or it marks just all new task and the event should be deleted within 6 months. I just wanted to see if I would get immediate space savings.

    Hey Stan,

    Purge scripts are set to run once a year, once a month, once a week and once per day because there are four procedures that work both to collect and to purge the data. You can manually run the purge by just running the default procedures stored in SQL Management Studio after connecting to your virtual Center DB and that would go very well indeed, and I guess that max age settings are what you would find already set at 6 months in the scripts, if you have already made changes in the GUI!

    Thank you

    one

  • vCenter data retention policies

    Dear team,

    I changed the policy of tensioning of database of vcenter for 1 days instead of 7 days for the task and evetsn, once clicked OK, when I discover the events and tasks yet i m able to see last 7 days logs. When and how this setting will touch.

    I need your assitiance...

    Concerning

    Mr. VMware

    If you set the retention period for a short period of time, then you will not be able to go back to see the tasks and older events. The retention period is a compromise between the amount of newspapers and the size of the database.

  • RMAN retention policy does not log source archive

    Oracle 11.2
    Windows server 2008
    CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED 1 TIME TO THE DISK.

    I ran after command
    TIME BACKUP ARCHIVELOG ' SYSDATE-6' UNTIL ' SYSDATE-1';

    RMAN > ARCHIVELOG BACKUP OF TIME ' SYSDATE-6' until ' SYSDATE-1';

    From backup may 29, 13
    using the control file of the target instead of recovery catalog database
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 386 type device = DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID = 773 type device = DISK
    jump the C:\ARC\ARC0000000564_0808506935.0001 archived log file; already supported
    up to 1 times
    \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
    00000564_0808506935.0001; already saved 1 time
    \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
    00000565_0808506935.0001; already saved 1 time
    jump the C:\ARC\ARC0000000565_0808506935.0001 archived log file; already supported
    up to 1 times
    \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
    00000566_0808506935.0001; already saved 1 time
    jump the C:\ARC\ARC0000000566_0808506935.0001 archived log file; already supported
    up to 1 times
    jump the C:\ARC\ARC0000000567_0808506935.0001 archived log file; already supported
    up to 1 times
    \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
    00000567_0808506935.0001; already saved 1 time
    jump the C:\ARC\ARC0000000568_0808506935.0001 archived log file; already supported
    up to 1 times
    \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
    00000568_0808506935.0001; already saved 1 time
    \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
    00000569_0808506935.0001; already saved 1 time
    jump the C:\ARC\ARC0000000569_0808506935.0001 archived log file; already supported
    up to 1 times
    \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
    00000570_0808506935.0001; already saved 1 time
    jump the C:\ARC\ARC0000000570_0808506935.0001 archived log file; already supported
    up to 1 times
    Backup finished 29 May 13

    RMAN >


    According to policy to delete rman does not delete source archive logs.

    This is the backup... command where the delete command

    obsolete report;

    Confirm if the archivelog you want to remove, then

    remove obsolete;

    so if you had manually deleted archivelogs use below to remove the entry of records controlfile

    overlap archivelog all;

    list expired archivelog all;

    REMOVE EXPIRED ARCHIVELOG ALL;

    edited part-

    read [url http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG]

    This plocy deletion makes these archivelog eligible for deletion. They will be deleted automatocally if they are inside the FRA FRA is short of space.

    Published by: Patricia kebe on May 29, 2013 01:16

  • RMAN: Deletion retention policy policy VS Archivelog

    I am a newbie to RMAN, so I did a lot of reading and experimentation, and I'm stuck on a problem.

    TASK: I want to keep two days of archived newspapers and a days worth of backups.

    SOLUTION: set 1 retention policy, set the deletion policy to archive 2

    (CONFIGURE ARCHIVELOG DELETION of SAVED POLICY 2 TIMES TO THE DISK.)

    and it's my simple backup script

    run

    {

    database backup "nightly_backup" tag more archivelog;

    delete noprompt obsolete;

    }

    PROBLEM: it does not work. Oracle documentation clearly (as clearly as possible the documentation) that "remove obsolete" uses the retention policy to clear logs archived. and deletion policy deletion archivelog to use "delete archivelog all;

    My tests verifies this.

    ISSUE. How remove the database obsolete backupsets ONLY by using the delete command?

    -Mark

    Just for clarity - if other people who have this issue will find this thread-I found the answer.

    Two policies are in effect only when you use the quick recovery for all your backup needs area. The database will automatically manage files according to policies. But as soon as you run manually ' rman > delete noprompt obsolete ' Oracle will only follow the retention policy.

    So as soon as FRA got up to about 78 percent full, he began to delete files, you can see in the alert.log

    Deleted Oracle managed file +FRA/sndbox/backupset/2014_07_23/annnf0_nightly_backup_0.435.853650191

    Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_1_seq_204.439.853668327

    Deleted Oracle managed file +FRA/sndbox/autobackup/2014_07_23/s_853650247.441.853650249

    Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_2_seq_189.434.853668653

    Another consequence of this fun is that Oracle will not automatically manage files outside of the FRA. So, if you save FRA on the disk, Oracle removes only files of FRA. If you must manually remove FRA backups, but which will also remove the FRA files according to the retention policies.

  • can someone explain to me of retention of Rman and optimization policy on or off.

    1. What is the meaning of retention policy redendency 1 or 2?

    2 what is the meaning of the retention policy to retrieve the window?

    3. What is the meaning of optimization and what happens in this case and vice versa?

    4. If optimization is he going to consider read-only and offline table space?

    5. If optimization off is going to be considered read-only and offline table space?

    do not post any documents that I went through the box of documents that someone let me know in words simple or easy to understand for me... give me some examples of real time

    Thank you for your time and patience.   waiting for your answers...

    Thanks and greetings

    Pichon

    Hi Abhishek,

    (1) If you set the retention to redundancy 2 policy, RMAN will keep only two recent backup copies and it will mark the rest obsolete backup copies (which means no need for recovery)

    (2) If you set the retention policy to retrieve the window at 5 days, no matter how much you take, backups RMAN will keep the last backup of 5 days. And the backups before the last 5 days will be marked as obsolete. So that the two retention policies are different, which serve different purposes. We use according to our requirement.

    (3) optimization means determine the most effective way to carry out the instructions. When you turn on the backup optimization, all orders backup will skip backups of any file if it has not changed and she has already been saved on the allocated device type.  A file can be any file dbf, archived redo log or a RMAN "backup set". If you turn off your backup optimization, all files are backup no question that has already been taken.

    (4) if backup optimization is configured, RMAN ignores backups of data files offline and read-only if the most recent backups were made the or after the closest point in the recovery window

    (5) if backup optimization is not configured, RMAN will have all the backups, including read-only and offline tablespaces.

    Hope this helps!

    Kind regards

    Pradeep. V

  • Backups RMAN does not match its retention policy

    Hello

    I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.

    For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.

    DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.

    I have clear and defined retention to 14 days over policy but doesn't seem to work.

    I would be grateful suggestion (s) about the strange.

    Thank you very much.

    Best regards

    John-MK wrote:

    Hello

    I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.

    For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.

    DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.

    I have clear and defined retention to 14 days over policy but doesn't seem to work.

    I would be grateful suggestion (s) about the strange.

    Thank you very much.

    Best regards

    We would need to know what kind of backups and where they were taken.  Imagine this scenario:

    7-day retention strategy.

    Level 0 incremental backup taken on Sunday

    Backup incremental level 1 taken Monday at Sam.

    Let's say that October 1 is a Sunday, so we take an Inc.-0 backup on October 1 and again on Oct. 8.

    Now let's say that we are at 10 Oct.  Our 7-day retention policy dicatates that we can recover any day of return to 3 Oct.

    The only way we can find to 3 Oct is to start with this backup Inc.-0 Oct. 1.

    Recovery all starts with last Inc.-0 backup before the point in time to be recovered.  In a normal life, regularly cycling calendar of backups, actually will end you with backups 1 day far twice also older than your retention period.

    A more extreme example.  Same period of retention of 7 days, but after a single backup Inc. - 0, you don't take any backups of 3 months.  That only a backup is always necessary to apply your window of recovery and therefore is not obsolete, despite the fact it is 3 months old and your recovery window is 7 days.

    Also, you mention "expiration".  Regarding backups oracle, 'expired' isn't the same as "obsolete".

    "Obsolète" means "is more necessary to apply the principle of recovery."

    "Expired" is a little more complex.

    When a backup is performed, or an archivelog is written, an account of which is written in the repository.  When you do a 'crossover' rman, these repository records are compared to reality - to see if the archivelog or saved backup file actually exists.  Maybe someone used an OS command to delete them.  Any file found "go walkabout" have their directory of files marked as "expired".  An rman "expiration to delete" then delete the records in the repository.

  • last available retention policy backup RMAN

    Hi all

    I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 22 days see below
    RMAN> show all;

RMAN configuration parameters for database with db_unique_name TEST are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 22 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

List of Backup Sets
===
    Published by: user8363520 on September 28, 2011 15:08

    Published by: user8363520 on September 28, 2011 15:09

    user8363520 wrote:
    Hi all

    I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 8 days see below

    RMAN> show all;

RMAN configuration parameters for database with db_unique_name TRGT are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/cont_spfile_%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_ctl_spfile_%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backups/%d_%t_%s_%p_%T';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/112_64/dbs/snapcf_TRGT.f'; # default

RMAN>

    but when I login and backup list... back were taken log time back still shows as AVAILABLE... I thought that it would be marked obsolete or expired... any reason why his does not like that? I had to change my couple of time format is why it dose not match the above... but just that I do not understand why his watch available?

    They are not 'marked' as outdated. They are "evaluated" as obsolete when necessary to meet demand for obsolete series. Notice what happens when I take three backups with a REDUNDANCY 2 retention policy

    RMAN> show retention policy;

using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:25
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:45
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:55
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> list backup;

List of Backup Sets
===================

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
113     Full    94.59M     DISK        00:01:18     27-SEP-11
        BP Key: 113   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T194613
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
  List of Datafiles in backup set 113


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
114     Full    6.89M      DISK        00:00:01     27-SEP-11
        BP Key: 114   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T194739
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp
  Control File Included: Ckp SCN: 1185229      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
115     Full    94.59M     DISK        00:01:38     27-SEP-11
        BP Key: 115   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T194931
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
116     Full    6.89M      DISK        00:00:02     27-SEP-11
        BP Key: 116   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T195116
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
  Control File Included: Ckp SCN: 1185400      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
117     Full    94.59M     DISK        00:01:50     27-SEP-11
        BP Key: 117   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T195228
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
118     Full    6.89M      DISK        00:00:02     27-SEP-11
        BP Key: 118   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T195423
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp
  Control File Included: Ckp SCN: 1185555      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           113    27-SEP-11
  Backup Piece       113    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
Backup Set           114    27-SEP-11
  Backup Piece       114    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp

RMAN> delete obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           113    27-SEP-11
  Backup Piece       113    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
Backup Set           114    27-SEP-11
  Backup Piece       114    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp

Do you really want to delete the above objects (enter YES or NO)? y
deleted backup piece
backup piece handle=/orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp recid=113 stamp=762983174
deleted backup piece
backup piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp recid=114 stamp=762983260
Deleted 2 objects

RMAN> exit

    or note this:

    RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           115    27-SEP-11
  Backup Piece       115    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
Backup Set           116    27-SEP-11
  Backup Piece       116    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp

RMAN> CONFIGURE RETENTION POLICY TO REdundancy 6;

old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 6;
new RMAN configuration parameters are successfully stored

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 6
no obsolete backups found

RMAN> CONFIGURE RETENTION POLICY TO REdundancy 1;

old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 6;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           115    27-SEP-11
  Backup Piece       115    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
Backup Set           116    27-SEP-11
  Backup Piece       116    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
Backup Set           117    27-SEP-11
  Backup Piece       117    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp
Backup Set           118    27-SEP-11
  Backup Piece       118    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp

RMAN> exit

  • doubt window retention RMAN

    Hello, I have RMAN backup in the trail of backupsets on two nodes RAC 11 GR 2 on linux standard edition.
    RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name MGW are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_mgw2.f'; # default

RMAN>
    And now I do not understand why RMAN is not delete backupsets that are older then 24 hours, even though I put
    CONFIGURE RETENTION POLICY TO RECOVERY OF 1 DAYS WINDOW.
    I have in my rman script that runs every day @ 23:00 this:
    backup as COMPRESSED BACKUPSET database FORMAT '/home/oracle/rman/%U' plus archivelog delete input;
delete noprompt obsolete;
    And now I see in my rman backup folder, there is no backupset yesterdey 23:00 and also the day before yesterday 23:00.
    [oracle@data02 rman]$ ls -l
total 51889864
-rw-r----- 1 oracle asmadmin 26454474752 Jul 14 00:19 0bmhcc1s_1_1
-rw-r----- 1 oracle asmadmin     1245184 Jul 14 00:19 0cmhcg84_1_1
-rw-r----- 1 oracle asmadmin 26626334720 Jul 15 00:18 0fmhf0ep_1_1
-rw-r----- 1 oracle asmadmin     1245184 Jul 15 00:18 0gmhf4ih_1_1
-rw-r--r-- 1 oracle oinstall           0 Jul 14 16:52 aa_1_1
    I thoght that if I ran my script, rman today @ 23:00, as this will backup but also delete backup from the night before, because I put
    1-day retention.
    Can you please tell why I'm wrong in this?

    The RMAN retention policy is not just keep the specified number of days. She calculates the interval between the end of the current time and extends in time to the specified number of days.

    So, by example, if you set the retention policy backup on 1 day today. Then RMAN will keep backups for the 15 July, 16 July.
    Then, on July 17, the backup of July 15th will be null and void.

    I.e.

    Current date   Status                                 Recovery Point
-----------------   ---------                                 ------------------------
15th July        available                               15-1 = 14th July
16th July        available                               16-1 = 15th July
17th July        backup of 15th July obsolete  17-1 = 16th July

So your backup for today wouldn't be marked as obsolete until the 17th July.

    5 setting up the RMAN environment

    However, if you have a fixed date of database then you should show the retention policy to redundancy instead of the recovery window.

    RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

  • -Obsolete - RMAN expired

    Dear friends,

    I'm with RMAN to back up my database.

    That means backup obsolete and outdated?

    When they reach such a State?

    Please guide me.

    Thank you

    >
    A backup is obsolete when the REPORT OUTDATED or OBSOLETE REMOVE determines, based on the user-defined retention policy, it is not necessary for recovery. A backup is considered a backup expired only when RMAN performs an overlap and can not find the file. In short, obsolete means that a file is not necessary, whereas expired way, it is not found.
    >

    Please read about the RMAN backup retention policies: http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV99966.

  • Record retention policy keep the emails on the server (pop)?

    24.0 TB

    I have my server settings to remove e-mail messages once they have been downloaded on my PC, because my ISP constantly sending emails of warning I used 90% of the 50 MB allocated to my mailbox.

    However, in some of my folders, I fixed some periods of detention. It overrides settings on my server?

    (I want to apply file retention policies at the local level I don't want to keep anything on the server ISP - a strategy which recommends the ISP.)

    A POP account, whatever you do locally outside the Inbox will not be vain things on the server.
    Assuming that you have the option "Leave messages on server" unchecked in your server settings, messages should not accumulate on the server in the first place.

Maybe you are looking for

  • HP G62 - 121EE Notebook PC: blurry photos

    The webcam on my laptop has blurred images. There seems to be no mention of some sort that can be adjusted or what might be wrong. The image is blurred, either a photo or a video or used for Skype calls. It will not just focus. Is there something I c

  • Re-install the reader software

    I have a PRS650. I replaced just from my old computer and want to install the client software for the reader on the subject. I also want to turn off allow the former. The old man has a dead HARD drive, so no hope to do from there. I have install, but

  • Fingerprint reader driver for HP Pavilion dv6 3049-tx

    My product name is HP Pavilion dv6 3049-tx. OS - 64 bit Windows 8 I upgraded my OS from "Windows 7 64-bit" to "8 64-bit Windows. But after my fingerprint reader stopped working because there is no driver support for Win8, I guess. Please let me know

  • Population of file tree

    Hello world I write the code for the user interface of a test system and I reach the project and test data in files that is already created at the beginning of the program. So I have a reason such as the folders with names of project and test the fil

  • exe file

    I was able to create an exe into a 64-bit windows, but I could not run this file on another pc. An error occurs that she needs some lib files. Please help me with it