When the RMAN brand is backup incremental level1 obsolete?

Hi all

On a server Oracle 10.2.0.2 particular (with ODG), I implemented a strategy of incremental backup. A level 0 backup is available and all level 1 next backups are getting recovered to this first copy of data file. So far so good.

The problem is that all these incremental backups at level 1 stay in my box of flashback and are not cleaned by RMAN. The retention policy is set on a window of 1 day.

When the RMAN will start scoring these backups to level 1 as being obsolete? I guess that these backups are obsolete right after that they were applied to the copy of the data file? This has something to do with the size of the parameter area flashback, which means that it will not begin to remove level 1 backups when RMAN runs into problems of free space on the disk?

Any help is appreciated!

JM

Hi JM,

This is expected behavior, because you have changed the default retention of redundancy strategy 1.
You can find this on My Oracle Support note + incremental backup strategies: Merge [ID 745798.1] +.

The extract of this says:
>
When using Oracle-Suggested policy or a daily incremental backup merged and using a Flash recovery area and then keep the retention policy of RMAN for redundancy 1. This will ensure that the Oracle space management will automatically remove incremental backups at level 1 of the FRA after they have been applied to the image based on the pressure of space in the FRA copy. If you increase the redundancy or set a window of recovery space is is automatically retrieved by Oracle. This works only when the retention policy is set to the default value of redundancy = 1. If the configured retention policy is set to the window of recovery or > 1 redundancy, RMAN cannot satisfy the retention policy if there is only one copy of database and it's at a later point in time. Thus, in order to satisfy political retention Oracle keeps all the incremental backups and archivelogs since the creation of the database because ideally a data file can be re-created and archivelogs can be applied to meet the retention policy (although not followed in the practical case).
>

To have made them obsolete automatically, you must add the 'UNTIL TIME 'SYSDATE-2' ' clause to the COPY of RECOVER sentence, for a 1-day recovery window.

The order having to RETRIEVE it after the BACKUP, you will have the current copy image, and you should only apply the archivelogs if you need to recover instead of use the last day of Level0 backup now level1.

Kind regards.
Nelson

Tags: Database

Similar Questions

  • The RMAN catalog database backup

    Version: 10.2.0.1.0

    We have created a database to host our RMAN catalog. This catalog contains info backup more RMAN stored scripts for 5 production databases. Now, we have to save this the RMAN catalog database.

    I'm going to use the control as the catalog file (IE. NOCATALOG) for our the RMAN catalog database. This should be good. Right? Best practices should I follow this topic?

    The catalog database can be saved as a BACKUP when COLD, if not in use for other purposes. Simple and easy backup and restore.

    Otherwise, you can make backups RMAN, but the this backup catalog database Controlfile.

    (You can even take copies to export the schema from the RMAN catalog!)

    Hemant K Collette

    Published by: Hemant K grapple on July 8, 2010 14:45

  • RMAN backup with the smallest size of backup

    Oralce 11g 2 on Redhat 5. Disk space is our the tighter resource, and we want an incremental backup with Level0 Sunday and level 1 every day of the week and on Saturdays. I'm using the comamnds to do the job
    --Sunday
backup incremental level 0 tag 'level_0' database plus archivelog;
--Other days
backup incremental level 1 database plus archivelog delete all input;
    I don't think that it is the best practice or produce smaller backup files.

    What are you comments and opinions. Thank you

    RMAN backup except for the backup copy will only backup blocks used, which is quite efficient. Backup incremental level 1 are set by default and the smallest of the incremental backup.

    However, you can enable compression reduce the size of the backupset (Oracle 10 g and more). You can also enable the block track the changes in the database only once, so that backup incremental level 1 do not need to analyze the data files for the changes - this allows saving a lot of time and IO.

    SQL > ALTER DATABASE ENABLE BLOCK CHANGE TRACKING;

    RMAN > run {sql 'alter system switch logfile' ;}}
    RMAN > BACKUP AS BACKUPSET INCREMENTAL LEVEL 0 COMPRESSED DATABASE MORE ARCHIVELOG DELETE ALL ENTRIES;
    RMAN > ACE COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 DATA BACKUP MORE ARCHIVELOG;

    I would prefer not to delete the archivelogs after each incremental backup of level 1 in order to make a point in time recovery without the need to restore the archivelogs.

    And don't forget to:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    I hope this helps.

  • backup incremental update feature

    Hi all

    can you explain this feafure when you take the copy of the image and then backup incremental and when
    data file is corrupted I have to restore the copy of the data file, and then apply an incremental backup.
    I do this planning, but I do not write the COPY OF THE file of DATA WITH TAG RECOVER command

    I take a copy of the image and then make this table spaces and make sure is the default value for the data base and ten make change
    DML, stop immediately and drop datafile can restore and recover
    restore the data file 5
    recover datafile 5


    without any incremental update command, feature and now my database is up-to-date? can you explain to me an example please?


    Thank you very much

    We must use the control switch that will make the controlfile to point to the backup of the data on the disk files.
    For example: you lost the data user 6 file

    RMAN > switch datafile 6 to copy;
    RMAN > recover datafile 6;
    RMAN > alter database datafile 6 online;

    The problem with incremental updates, is that, after any failure, as above, if restore us it, it will change the name and location of the data file. After restoration manual you rename them to original location.

    In case of failure of the database

    RMAN > switch database to copy.
    RMAN > restore database;
    RMAN > alter database open

    Published by: renee_mathieu on August 5, 2012 07:54

  • How can I make the hour, Minute, second information in the RMAN log?

    DB version: 11.2.0.3

    Platform: Oracle Enterprise Linux 6.2

    An excerpt from log RMAN backup file.

    As indicated by the arrows below, the RMAN backup log only information hour, Minute, and second. It was just the date 14 October 13

    archived journal entry thread = 1 sequence = RECID 10946 = STAMP 21079 = 828801629

    archived journal thread = 2 sequence = 10137 entry RECID = STAMP 21081 = 828801794

    archived journal thread = 1 sequence = 10947 entry RECID = STAMP 21080 = 828801731

    CH01 channel: from song 1 to 14 October 13-> we need some time here as 17:28:43

    channel ch00: finished piece 1 to 14 October 13

    piece handle = al_9306_1_828819222 tag = comment TAG20131014T190816 = Version of the API 2.0, MMS Version 5.0.0.0

    channel ch00: complete set of backups, time: 00:14:55

    channel ch00: archived deletion or newspapers

    .

    .

    < snipped >

    How can I set up the equivalent of below declaration for registration of RMAN?

    ALTER session set nls_date_format = 'YYYY-MM-DD HH24:MI:SS ";

    Hello

    We recommend that you always set you variable NLS_DATE_FORMAT so tah you see the hou, minute and second components of the date when the RMAN command. IF you be wrapped a gall newspaper during backup, restore and recovery controls, then this will ensure that a component of timestamp is disapled. This cabin can be useful when you are trying to solve the problems of RMAN.

    If you do not set NLS_DATE_FORMAT, then you will not see the hour, minute, and the second component of the date columns. Excerpt from the output of a list without set NLS_DATE_FORMAT command:

    Time of accomplishment of TIME TYPE LV SIZE DEVICE TYPE ELAPSET BS keys

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

    201 full DISCK 18.66 M 03:00:00 January 1, 13

    Here is the result even when the NLS_DATE_FORMAT is set. Notice how the hours, the minutes and the seconds are now displayed:

    Time of accomplishment of TIME TYPE LV SIZE DEVICE TYPE ELAPSET BS keys

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

    201 full DISCK 18.66 M 03:00:00 January 1, 13 12:11:25

    You can check the value of NLS_DATE_FORMAT of your operating system with the echo command environment. ON UNIX, use echo as follows:

    $echo $NLS_DATE_FORMAT

    Here is an example of Windows to display NLS_DATE_FORMAT using the echo command:

    c:\>echo % NLS_DATE_FORMAT %

    To disable an OS variable, simply make it void. For example, to unset NLS_DATE_FORMAT in an environment of the UNIX C shell, use the OS unsetenv command:

    $unsetenv NLS_DATE_FORMAT

    IN an environment of the UNIX KORN shell, use export OS as follows:

    $export = NLS_ADTE_FORMAT

  • Merger of the RMAN incremental backups

    Hi all

    I have a confusion.

    Sunday I L0 scheduled backup (backup as compressed).
    Then next 6 days (MON - sat) I incremental backup Level1 (differential).

    So let's assume that if I need to restore the Thursday, I need Sunday L0 and L1 of (MON, TUE, WED).

    Is it possible to merge L0 and L1 (until WEDNESDAY).

    Please specify.

    Thanks in advance.

    Kind regards
    Bikram

    As long as you use differential incremental backups, you need all of them between the last level 0 backup and recovery at the time point. It is exactly the concept of cumulative incremental backups to change this behavior. In the case of cumulative backups you would only need the full backup and the incremental backup from Wednesday.

    Werner

  • How to restore the Rman incremental level 0 backup if the SID is different?

    Hi Experts,
    I had a little problem with restore rman backup of level 0. I have backup rman for oracle 11.2.0.1.0 - 64 bit and restore the server to Test 11.2.0.1.0 - 64 bit.

    Problem:
    Sid = prd production server
    Sid = prderp test server

    Operating system is Oracle linux 5 on both servers.

    How to restore Rman if the SID is different?

    Hello

    Refer to this http://shivanandarao.wordpress.com/2012/04/19/duplicating-primary-database-to-a-new-host-without-connecting-to-the-primary-database-in-oracle-10g11g/

    You need to restore it under the same name as you have in the production and later change the dbname using the NEST.

    If you don't want to go with this method, then I suggest you to go with the method of double RMAN.

    http://www.Oracle-base.com/articles/11g/duplicate-database-using-RMAN-11gr2.php
    http://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmdupdb.htm

    rman target sys/@prod auxiliary sys/@tst
RMAN>duplicate target database to 'prderp' nofilenamecheck;

    Please close this Re: how to restore the Rman backup if the SID is different? wire by marking as replied.

  • Why the format does not work on my backup incremental level 1 the difference?

    I use following script to make a backup of difference incremental level 1.
    ------------------------------
    Run {}
    allocate channels ch1 disc type;
    Set order id "Monday_INC_1_df";
    backup as compressed backupset database incremental level 1
    format ' / opt/oracle/rman/bk/incr1_df_%d_%U'
    tag "Monday_INC_1_df".
    database more entered archivelog delete;
    output channel ch1.
    }
    -------------------------------

    According to this scenario, all the rman output files are placed in "/ opt/oracle/rman/bk / '...  And his label is 'Monday_INC_1_df'.

    But at the bottom of the newspaper, I find the archived log rman output files located in "/ opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02 / '. And his label is "TAG20141202T210529".
    Also, at the bottom of the newspaper, the output data files rman files was partly on the right path "/ opt/oracle/rman/bk / '. And it seems that the data files has been supported for 2 times. The second time datafile rman output files was badly located in the path "/ opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02 / '. And his label is "TAG20141202T215627".


    ================================================ Detail Log ===================================================================================
    channel ch1: compressed boot archived log backup set
    channel ch1: specifying the newspapers archived in the backup set
    archived journal entry thread = 1 sequence = 36706 RECID = 2773 STAMP = 865282473
    archived journal entry thread = 1 sequence = 36707 RECID = 2774 STAMP = 865282476
    archived journal entry thread = 1 sequence = 36708 RECID = 2775 STAMP = 865282478
    archived journal entry thread = 1 sequence = 36709 RECID = 2776 STAMP = 865282482
    archived journal thread = 1 sequence = 36710 entry RECID = STAMP 2777 = 865282486
    archived journal entry thread = 1 sequence = 36711 RECID = 2778 STAMP = 865285528
    channel ch1: starting piece 1 at 2014-12-02 21:56:20
    channel ch1: finished piece 1 at 2014-12-02 21:56:27
    piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02/o1_mf_annnn_TAG20141202T210529_b7vk8408_.bkp tag = TAG20141202T210529 comment = NONE
    channel ch1: complete set of backups, time: 00:00:07
    channel ch1: archived deletion or newspapers
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36706_b7vc98xc_.arc RECID archived log file = 2773 STAMP = 865282473
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36707_b7vc9cz7_.arc RECID archived log file = 2774 STAMP = 865282476
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36708_b7vc9gn1_.arc RECID archived log file = 2775 STAMP = 865282478
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36709_b7vc9l3f_.arc RECID archived log file = 2776 STAMP = 865282482
    RECID = STAMP 2777 = 865282486 name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36710_b7vc9plj_.arc archived log file
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36711_b7vg8qz5_.arc RECID archived log file = 2778 STAMP = 865285528
    A backup over the 2014-12-02 21:56:27


    From backup 2014-12-02 21:56:27
    channel ch1: from compressed data file backup set incremental level 1
    channel ch1: specification-datafile in the backup set (s)
    Enter a number of file datafile = name=/opt/oracle/oradata/test/undotbs01.dbf 00003
    Enter a number of file datafile = 00005 name=/opt/oracle/oradata/test/hp01.dbf
    Enter a number of file datafile = name=/opt/oracle/oradata/test/cmtspace01.dbf 00035
    Enter a number of file datafile = name=/opt/oracle/oradata/test/sysaux01.dbf 00002
    Enter a number of file datafile = 00001 name=/opt/oracle/oradata/test/system01.dbf
    Enter a number of file datafile = name=/opt/oracle/oradata/test/users01.dbf 00004
    channel ch1: starting piece 1 at 2014-12-02 21:56:28
    channel ch1: finished piece 1 at 2014-12-02 23:48:06
    piece handle tag = / opt/oracle/rman/bk/incr1_df_TEST_1gpp6gcc_1_1 MONDAY_INC_1_DF = comment = NONE
    channel ch1: complete set of backups, time: 01:51:38
    channel ch1: from compressed data file backup set incremental level 1
    channel ch1: specification-datafile in the backup set (s)
    Enter a number of file datafile = name=/opt/oracle/oradata/test/undotbs01.dbf 00003
    Enter a number of file datafile = 00005 name=/opt/oracle/oradata/test/hp01.dbf
    Enter a number of file datafile = name=/opt/oracle/oradata/test/cmtspace01.dbf 00035
    Enter a number of file datafile = name=/opt/oracle/oradata/test/sysaux01.dbf 00002
    Enter a number of file datafile = 00001 name=/opt/oracle/oradata/test/system01.dbf
    Enter a number of file datafile = name=/opt/oracle/oradata/test/users01.dbf 00004
    channel ch1: starting piece 1 at 2014-12-02 23:48:07
    channel ch1: finished piece 1 at 2014-12-03 01:17:22
    piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02/o1_mf_nnnd1_TAG20141202T215627_b7vqsq8y_.bkp tag = TAG20141202T215627 comment = NONE
    channel ch1: complete set of backups, time: 01:29:15
    A backup over the 2014-12-03 01:17:22

    From backup 2014-12-03 01:17:23
    Current archived log
    channel ch1: compressed boot archived log backup set
    channel ch1: specifying the newspapers archived in the backup set
    archived journal entry thread = 1 sequence = 36712 RECID = 2779 STAMP = 865288890
    archived journal entry thread = 1 sequence = 36713 RECID = 2780 STAMP = 865288965
    archived journal entry thread = 1 sequence = 36714 RECID = 2781 STAMP = 865288971
    channel ch1: starting piece 1 at 2014-12-03 01:17:24
    channel ch1: finished piece 1 at 2014-12-03 01:17:49
    piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_03/o1_mf_annnn_TAG20141203T011723_b7vx145d_.bkp tag = TAG20141203T011723 comment = NONE
    channel ch1: complete set of backups, time: 00:00:25
    channel ch1: archived deletion or newspapers
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36712_b7vkkts7_.arc RECID archived log file = 2779 STAMP = 865288890
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36713_b7vkn5v0_.arc RECID archived log file = 2780 STAMP = 865288965
    name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36714_b7vkncv2_.arc RECID archived log file = 2781 STAMP = 865288971

    =============================================================================================================


    When I here is the backup incremental level 0, everything seems good.

    ----------------------------------
    Run {}
    allocate channels ch1 disc type;
    Set order id "Sunday_INC_0";
    backup incremental level 0 compressed backupset
    format ' / opt/oracle/rman/bk/incr0_%d_%U'
    tag "Sunday_INC_0".
    database more entered archivelog delete;
    output channel ch1.
    }
    --------------------------------

    But why my backup of difference in level 1 increntmental would not have good correct rman output path?


    You have specified the keyword 'database' twice in the backup command.  If execution is in the specified format, the second with the default format (to the FRA)

    Hemant K Collette

  • RMAN backup incremental level 1 without level 0-10 gr 2

    Hello

    I'm a bit confused after a few tries.

    The issue: It is mandatory to perform incremental level 0 backup before level 1 using Oracle 10 g 2?

    On Oracle 11.2 is mandatory, but I don't know about Oracle 10.2.0.5.

    11.2 test. If there is no level 0 rman take care on this subject and automatically perform level 0 before level1
    RMAN> backup incremental level 1 database;

Starting backup at 29-APR-11
using channel ORA_DISK_1
no parent backup or copy of datafile 1 found
...
channel ORA_DISK_1: starting incremental level 0 datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
...
    Docs said:
    Incremental backups capture only blocks that change between backups in each data file.
    In a typical incremental backup strategy, an incremental backup of level 0 is used as a starting point. A level 0 backup captures all the blocks in the data file.

    So, on Oracle 10.2.0.5 happens not like 11.2:

    Parade level 1 without level 0 backup:
    RMAN> list backup;


RMAN> backup incremental level 1 database;

Starting backup at 29-APR-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DG_ORCL/db10g/datafile/system.260.749756975
...
channel ORA_DISK_1: starting piece 1 at 29-APR-11
channel ORA_DISK_1: finished piece 1 at 29-APR-11
piece handle=+DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421 tag=TAG20110429T190340 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 29-APR-11
channel ORA_DISK_1: finished piece 1 at 29-APR-11
piece handle=+DG_FRA/db10g/backupset/2011_04_29/ncsnn1_tag20110429t190340_0.262.749761449 tag=TAG20110429T190340 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
Finished backup at 29-APR-11

RMAN> backup archivelog all delete input;

Starting backup at 29-APR-11
current log archived
using channel ORA_DISK_1
...
Finished backup at 29-APR-11

RMAN> shutdown abort;
Oracle instance shut down
    Delete all (except SPFILE) ASM files.
    ASMCMD> cd +DG_ORCL/DB10g
ASMCMD> ls
PARAMETERFILE/
spfiledb10g.ora
    So we will perfom a database restore
    oracle@butao:/home/oracle> rman target /
Recovery Manager: Release 10.2.0.5.0 - Production on Fri Apr 29 19:06:52 2011
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
connected to target database (not started)
RMAN> startup nomount
Oracle instance started

Total System Global Area     293601280 bytes
Fixed Size                     2095872 bytes
Variable Size                 92275968 bytes
Database Buffers             192937984 bytes
Redo Buffers                   6291456 bytes


RMAN> restore controlfile from '+DG_FRA/db10g/backupset/2011_04_29/ncsnn1_tag20110429t190340_0.262.749761449';

Starting restore at 29-APR-11
using channel ORA_DISK_1

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
output filename=+DG_ORCL/db10g/controlfile/current.263.749761699
output filename=+DG_FRA/db10g/controlfile/current.263.749761699
Finished restore at 29-APR-11

RMAN> startup mount

database is already started
database mounted
released channel: ORA_DISK_1

RMAN> restore database;

Starting restore at 29-APR-11
Starting implicit crosscheck backup at 29-APR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 29-APR-11

Starting implicit crosscheck copy at 29-APR-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 29-APR-11

searching for all files in the recovery area
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: +dg_fra/DB10G/BACKUPSET/2011_04_29/ncsnn1_TAG20110429T190340_0.262.749761449
File Name: +dg_fra/DB10G/BACKUPSET/2011_04_29/annnf0_TAG20110429T190442_0.264.749761485

using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DG_ORCL/db10g/datafile/system.260.749756975
restoring datafile 00002 to +DG_ORCL/db10g/datafile/undotbs1.261.749757085
restoring datafile 00003 to +DG_ORCL/db10g/datafile/sysaux.262.749757095
restoring datafile 00004 to +DG_ORCL/db10g/datafile/users.264.749757107
channel ORA_DISK_1: reading from backup piece +DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421
channel ORA_DISK_1: restored backup piece 1
piece handle=+DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421 tag=TAG20110429T190340
channel ORA_DISK_1: restore complete, elapsed time: 00:00:26
Finished restore at 29-APR-11

RMAN> recover database;

Starting recover at 29-APR-11
using channel ORA_DISK_1

starting media recovery

archive log thread 1 sequence 27 is already on disk as file +DG_FRA/db10g/onlinelog/group_3.259.749756971
archive log thread 1 sequence 28 is already on disk as file +DG_FRA/db10g/onlinelog/group_1.257.749756963
archive log filename=+DG_FRA/db10g/onlinelog/group_3.259.749756971 thread=1 sequence=27
archive log filename=+DG_FRA/db10g/onlinelog/group_1.257.749756963 thread=1 sequence=28
media recovery complete, elapsed time: 00:00:02
Finished recover at 29-APR-11

RMAN> alter database open resetlogs;

database opened

RMAN>
    See that I don't need level 0 backup to restore the level 1.

    Thank you
    Levi Pereira

    Levi,

    Please visit: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm

    If no level 0 backup is available, then the behavior depends on the setting of compatibility mode. If compatibility is > = 10.0.0, copies all blocks changed since the file was created RMAN and stores the results as a level 1 backup. In other words, the CPN at the time the incremental backup is taken is the creation of SCN file. If compatibility<10.0.0, rman="" generates="" a="" level="" 0="" backup="" of="" the="" file="" contents="" at="" the="" time="" of="" the="" backup,="" to="" be="" consistent="" with="" the="" behavior="" in="" previous="">

    Same info is here:

    http://www.Pythian.com/news/287/level-1-incremental-backup-in-Oracle-10G/

    Concerning

    Grosbois

  • Problems with duplicate DATA when the data file was added after the backup completes

    Hello

    I am facing a problem when running of duplicate database with the command of database duplicate RMAN on a 10 g database. If I have the duplication from a full backup that is missing a data file that has been added to the database after the full backup of preforms, I get the following error message:
    Starting restore at 10-10-2009 18:00:38

released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/10/2009 18:00:39
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06100: no channel to restore a backup or copy of datafile 43
    Redo log which was Pond at the time of the creation of 43 of the data file is also available in the backups. It seems that RMAN cannot use the log information archived redo to restore the content of the data file 43. I guess that because failure is already reported in the RESTORATION and not in the RECOVERY phase, so again the archived logs are not available yet. I get the same message even if I do another backup of the data file 43 (so a backup that is not in the same backupset as the backup to all the other data files).
    The script, the command duplicate product, I guess that RMAN reads the contents of the source database controlfile and trying to get a backup that contains all the data files to restore the database Assistant - if such a backup is not found, it fails.


    Of course, if I try to perform a restore/recovery of the source database, it works without problem:
    RMAN> restore database;

Starting restore at 13.10.09
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK

creating datafile fno=43 name=F:\ORA10\ORADATA\SOVDEV\SOMEDATAFILE01.DBF
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to F:\ORA10\ORADATA\SOVDEV\SYSTEM01.DBF
.....
    The 43 data file is re-created and then redo is applied to the course.

    So, does anyone know if the duplicate database can use archived redo logs to recreate the contents of a data file, as does a normal restore/recovery? If this is the case, then it is necessary to perform a full backup before each duplicated if a data file has been added after such a backup database.

    Thanks in advance for any answers.

    Kind regards
    Swear

    Hi swear,.

    I got exactly the same problem during replication.
    Because we backup archive logs every 6 hours with rman, I added an additional block of running this script.
    run
    {
    backup incremental level 0
    format "% d_ % s_ %%t p_ bk_ '.
    filesperset 4
    database not saved;
    }

    (I also hit a bug in the catalogue which was resolved by patching up the dbs catalog 11.1.0.6, 11.1.0.7 for.)

    This will restrict the data not making file not part of any backup rman 6 hours while jumping for which there is already a backup of data files.

    Kind regards

    Tycho

  • If time machine is incremental how it removes previous versions when the disk is full, without breaking the chain, so do not be able to restore all changes since the first full file

    If time machine is incremental how it removes previous versions when the disk is full, without breaking the chain, so do not be able to restore the file with any changes made since the full backup first file...

    If the TM drive storage is full TM automatically deletes the version the oldest files for the new incremental backups can be made. Thus, in this case you cannot restore the versions that TM deleted because it takes more storage.

  • Backup Windows XP does not seem to be clear the attribute archive when you perform a normal backup.

    Backup Windows XP does not seem to be clear the attribute archive when you perform a normal backup.

    I do a backup of the 'Normal' at the beginning of the month.  Then, at the end of the first week, I do a "Differential" backup (using the same "backup job" but change to type "Incremental".)

    Well the difference is huge and to study, I see that a lot of files that I don't know that I didn't take the week since the 'Normal' backup have the Archive attribute set.

    Is the 'Normal' compensation not the bit mode backup of archive?  Another thing would be randomly set the attributes to archive?  Is there a ghost in the machine?  Inquiring minds want to know.

    Hello

    Differential backup marks files as having been backed up (in other words, archive attribute is not cleared). This is normal.

    For more information please visit:
    http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/types_of_backup.mspx?mfr=true
    http://msdn.Microsoft.com/en-us/library/aa174458 (SQL.80) .aspx
    http://msdn.Microsoft.com/en-us/library/ms345448.aspx

    Thanks and greetings
    Umesh P - Microsoft technical support.

    Visit our Microsoft answers feedback Forum and let us know what you think.
    [If this post can help solve your problem, please click the 'Mark as answer' or 'Useful' at the top of this message.] [Marking a post as answer, or relatively useful, you help others find the answer more quickly.]

  • I have to keep the older backup sets when I generate a new backup set?

    I have vista Home premium.  I regularly backup my computer.  Whenever I save I now have a new set of disks.  Can I get rid of the old game when the new set is generated. ?

    N °

    Because after the initial backup files, subsequent backups are incremental, which means that the system only save new files and files that have changed since the last backup.

    You must keep the heap.
    However, later you will be asked to make a new, full backup. Then, you can delete older backups, but only after you have a new, full backup.

  • Backup incremental level 2,3,4 RMAN.

    Hello guys,.

    Can someone let me know what is the meaning / usage of incremental backup of level 2,3,4.

    Kind regards.

    Wikipedia can have an easy to understand the reason for several additional levels:

    A backup of level 1 decision Monday would only include changes made since Sunday. A backup of level 2 decision Tuesday would only include changes made since Monday. A backup of level 3 Wednesday would only include changes made since Tuesday. If a level 2 backup taken Thursday, it would include all changes made since Monday because Monday was the most recent level n - 1 backup.

    https://en.Wikipedia.org/wiki/Incremental_backup

    What is RMAN?

    The Oracle documentation refers only to additional 0 year 1. What I understand, RMAN never supported incremental backups multilevel at 3 levels (0-4). Apparently, people often had trouble understanding the logic for levels 3 and 4. RMAN provides the clause 'cascading', which also existed in 9i and is usually an easier to understand the backup strategy. RMAN also provides or has provided an option to perform incremental backups cumulative at level 1 or higher. For simplicity, the la documentation documentation since 10 g mentions only level 0 only a 1 an other levels is deprecated.

    BACKUP INCREMENTIELLE from LEVEL 1 (differential by default, changes made since the last level 0 or 1)

    BACKUP INCREMENTIELLE LEVEL 1 CUMULATIVE (changes since the last last level 0)

    Below some info from http://docs.oracle.com/cd/E11882_01/backup.112/e10643/obs_comm.htm#RCMRF910

    RMAN version 10.0.1: levels other than 0 and 1 are deprecated.

    If you make an additional workforce 1 backup, incremental or cumulative, and there is no previous level 0, RMAN automatically performs an incremental backup of level 0. BTW, a full backup is identical to a level 0 incremental backup but excluded a strategy of backup incremental level.

  • Understand RMAN until the time - why a backup always kept.

    Hi all

    I take more than one database system and is now looking to its backup policy.

    The system performs full backup every Monday at level 0 and level 1 differential accrued daily. As well the full or incremental backup runs at 00:40

    The backup retention policy is set to 1 day.

    CONFIGURE RETENTION POLICY TO 1 DAY RECOVERY WINDOW;

    Every day, there is a call from script "delete_obsolete.sh" who works at full 00:25.

    In the script, there are 3 lines that follow below

    cross-checking of backup;

    delete expired backup noprompt.

    remove obsolete until 'sysdate-6 ";

    T1) so I think that, with the 'until TIME', he will crush the retention policy and only delete previous backup then ' sysdate - 6 "- right?".

    However in RMAN summary list, assuming today ' today is 09/04/2015 (Friday) and the delete_obsolete.sh script is run at 00:25 hours that day.

    The script removes actually backs up earlier then sysdate - 6, equivalent to 29 Aug 15 00:25:00

    Backup list

    ===============

    S LV TY Device Type delay #Pieces compressed #Copies Tag key

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

    2211797 B 0 A DRIVE 24 AUGUST 2015 02:55:04 2 1 YES SEC_FFF1_STBY_2NDRMAN_BACKUP

    2211798 B 0 A DRIVE 24 AUGUST 2015 03:31:28 3 1 YES SEC_FFF1_STBY_2NDRMAN_BACKUP

    2211799 B 0 A DRIVE 24 AUGUST 2015 03:53:10 3 1 YES SEC_FFF1_STBY_2NDRMAN_BACKUP

    2217710 B 1 A DISK 28 AUGUST 2015 00:55:38 1 1 YES SEC_FFF1_STBY_2ND_LV1_BACKUP

    2217711 B 1 A DISK 28 AUGUST 2015 00:56:51 1 1 YES SEC_FFF1_STBY_2ND_LV1_BACKUP

    2217712 B 1 A DISK 28 AUGUST 2015 00:57:52 1 1 YES SEC_FFF1_STBY_2ND_LV1_BACKUP

    2217713 B F A DISC AUGUST 28, 2015 00:58:15 1 1 no TAG20150828T005753

    2219520 B 1 A DISK 29 AUGUST 2015 00:56:23 1 1 YES SEC_FFF1_STBY_2ND_LV1_BACKUP

    2219521 B 1 A DISK 29 AUGUST 2015 00:56:47 1 1 YES SEC_FFF1_STBY_2ND_LV1_BACKUP

    2219522 B 1 A DISK 29 AUGUST 2015 00:57:56 1 1 YES SEC_FFF1_STBY_2ND_LV1_BACKUP

    2219523 B F A DISC 29 AUGUST 2015 00:58:25 1 1 no TAG20150829T005803

    (* q2) so if RMAN is said to remove obsolete older then 29 Aug 15 00:25:00, why is 28 - Aug backup is not deleted?

    Q3) is 24 August 15 backup not deleted because it is a 0 level and it is necessary to restore the backup of lvl 1 29 August 2015 which still does more then category "August 29, 2015 00:25:00.

    Kind regards

    Noob

    Yes, your understanding is correct now, with the output you posted

    No problems encountered,

Maybe you are looking for