Incremental RMAN backup

Dear all,
How could i eradicate the below error ?
1002,07-DEC-07,RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =========
======
1002,07-DEC-07,ORA-19641: backup datafile checkpoint is SCN 1746331111 time 09/19/2007 22:09:11
1002,07-DEC-07,RMAN-03002: failure of recover command at 12/07/2007 22:00:41
1002,07-DEC-07,
1002,07-DEC-07,RMAN-00571: ===========================================================
1002,07-DEC-07,ORA-19642: incremental-start SCN is 1745550838
1002,07-DEC-07,RMAN-00571: ===========================================================
1002,07-DEC-07,ORA-19640: datafile checkpoint is SCN 1746331111 time 09/19/200722:09:11
1002,07-DEC-07,ORA-19639: file +FLASHDG/dws/datafile/usage_events_data.1439.624594417 is more current than this incremental backup
1002,07-DEC-07,Recovery Manager complete.

That could be bug 5417204 (ORA-19639 on RECOVER COPY OF RMAN)
The problem occurs when, while RECOVER COPY OF RMAN is running, the
database is shutdown.
Problem is fixed in 10.2.0.4 and 11g.
Werner

Similar Messages

  • Incremental RMAN Backup to tape.

    Hi,
    We have 2.2 TByte Oracle Dataware House. At weekends, we would like to take inceremental level 0 backup to tape and then incemental level 1 to disk daily.
    So that we expect to reduce disk space for backup. We also handle the cover risk of direct path load by mains of incremental level backup.
    But, I would like to know that, taking incremental level 0 to tape causes performance problems. Rman try to discover changes between the incemental level 0 on the tape and incemental level 1 on the disk.
    Should we take both incremental level 0 and incremental level 1 to disk or tape?
    I need your recomendations.
    Thank you.

    Thank you Satish Kandi for your reply,
    As far as understand accourding to document that you refer,
    if we configure well adjustment for channel of disk and tape io buffers,
    and multiplexing, then we can take backup incemental level 0 to tape.
    We don't want to use encryption and compression in order not to consume CPU resources.
    In fact, we should try and obsorve the performance.
    Thank you.

  • Incremental RMAN backup and compression

    Does RMAN compress the data for the incremental Level 0 and Level 1 backups. More specifically - Can I use Advanced compression if olny use incremental backups ?

    you would use the comfigure command to use zlib which is does not compress as well as bzip2 which does not require the advanced compression option, but zlib does not consume as much cpu as bzip2.
    now for the backup you have 2 options. you can configure backupsets to compress
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET ;
    or it using table
    CONFIGURE DEVICE TYPE sbt BACKUP TYPE TO COMPRESSED BACKUPSET ;
    Then do you backups as backup sets
    database
    backup as backupset incremental level 1 tag hot_1_${DTE} DATABASE NOT BACKED UP SINCE TIME 'SYSDATE - .6';
    archivelogs
    backup as compressed backupset format '${INST_LOWER}_Archive_%d_%s_%p_%t' archivelog all not backed up 1 times ;

  • Restoring RMAN backup

    Hi everyone,
         We have the oracle servers version
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    One is the production server and one is for testing. We are taking incremental RMAN backup in the production server. I need to restore that backup to the testing server from production server once in 3 days. The DB name is same for both database.
    Plese anyone explain me about how to acheive this..
    With thanks & Regards,
    Jai.

    if you would like also refer,
    http://www.akadia.com/services/ora_duplicate_database_rman.html
    http://gavinsoorma.com/recovery-scenarios/
    video tutorial
    http://kamranagayev.wordpress.com/2010/06/25/rman-video-tutorial-series-creating-duplicate-and-standby-database-using-rman/

  • FRA changed but incremental RMAN disk backup failed

    This is a 11.1 test database.
    There was a daily FRA RMAN backup scheduled from database control. Because of the filesystem space pressure we changed FRA destination to a new filesystem and removed old FRA directories.
    But this time RMAN failed because it is trying to access the old files as base. How can I force RMAN to make a new base for daily incremental backup and not loose the already scheduled backup.
    Thank you.
    Connected to Oracle Database 11g Enterprise Edition Release 11.1.0.6.0
    Connected as ODS
    SQL> SELECT output FROM v$rman_output ORDER BY recid;
    OUTPUT
    connected to target database: OWB11 (DBID=373788874, not open)
    using target database control file instead of recovery catalog
    echo set on
    run {
    allocate channel oem_disk_backup device type disk;
    recover
    allocated channel: oem_disk_backup
    channel oem_disk_backup: SID=688 device type=DISK
    Starting recover at 12-JUL-08 02:01:13
    no copy of datafile 5 found to recover
    no copy of datafile 7 found to recover
    no copy of datafile 8 found to recover
    channel oem_disk_backup: starting incremental datafile backup set restore
    channel oem_disk_backup: specifying datafile copies to recover
    recovering datafile copy file number=00003 name=/dwh0/app/oracle/product/flash_r
    channel oem_disk_backup: reading from backup piece /ods01/owb11/flash_recovery_a
    OUTPUT
    released channel: oem_disk_backup
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 07/12/2008 02:01:14
    ORA-19870: error while restoring backup piece /ods01/owb11/flash_recovery_area/O
    ORA-19625: error identifying file /dwh0/app/oracle/product/flash_recovery_area/O
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    exit;
    36 rows selected
    SQL>

    assuming you are using the Oracle provided backup procedure (you are pretty scarce on details) you need to make sure you don't have any backups (crosscheck backup and delete expired backup comes to mind), and run the procedure again. It will make a new level 0 backup and incrementals on the following days.
    Please note if you don't use RMAN to clean up your O/S you will always ruin the RMAN catalog!!!
    Sybrand Bakker
    Senior Oracle DBA

  • Incremental updated RMAN backup help 11gR2

    Dear all,
    My manager ask me to build RMAN scripts to backup the 11gr2 database in redhat Linux.
    Any help how to achieve this using RMAN?
    thank you

    I am not asking you to write a script. I can write it by myself.
    What I need to know:
    1- Incremental level 0 is a must in my case or I can just use the command below and it does everything (Level 0 , level 1 and level 0 incrementally updated)
    backup incremental level 1 for recover of copy tag 'ALL_BACKUP' database;
    2- The TAG must be unique every week, or can be always "ALL_BACKUP" ?
    3- Which retention period is adequate in my case? 8 days are ok ?
    4- Should I update the CONTROL_FILE_RECORD_KEEP_TIME to more than 7 days?
    thank you

  • Rman backup

    Hi,
    I want to take one time RMAN backup with indefinite retention policy. what is the best way. I want to recover the database whenever I want may be after year time.
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    or
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 500 days;
    or
    CONFIGURE RETENTION POLICY TO NONE;
    Regards,
    DBA

    user573035 wrote:
    Hi ,
    Thanks for your reply. I decided to go as below.
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '${BACKUP_DIR}/${THEDBNAME}/cf_%d_%F';
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 6;
    CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE = 20G;
    This way I will have 2 backup and I will stop to take backup from RMAN. If it requires in future I can restore any of them.
    Regards,
    DBAI am confused about what you are trying to achieve here, and without knowing that, we really can't give any good advice.
    What do you mean by "I will stop to take backup from RMAN" ?
    It's sounding like you are planning on only taking one or two backups and never backing up again ..... ?
    Are you running in archive log mode? Are you taking regular full and/or incremental backups? What are you trying to achieve by holding one backup for such a long period of time? How do you think this is better than the usual practice of taking a full backup once every week or so and incremental backups daily, with a retention period specified in terms of recovery window (time) instead of redundancy (number of backups)?
    You may have some very good reasons, or simply haven't described your intent very well, but right now it sounds like you are about to head down the road to database recovery hell.

  • Incrementally updated backup and EMC NMDA

    Hello Everyone,
    I'm kind of a newbie in setting up networker module for oracle, to backup database to tape. We use the oracle's suggested backup strategy to backup DB to Disk first using the incrementally updated backups with recovery set to 3 days (RECOVER COPY OF DATABASE WITH TAG ... UNTIL TIME 'SYSDATE-3') , which helps us to recover DB to any point in time using the backup files in disks vs. going to tape. After backup to disk, we backup recovery area to tape nightly. However, we do want to maintain backup Retention Policy of 1 month. Couple of questions,
    1. If i set RP to recovery window of 31 days in RMAN, then backups don't obsolete at all. this forces me to set RP in networker and they don't recommend setting RP in both RMAN and networker. how is this done generally to obsolete backups from tape as well as rman (catalog in CF) with above strategy. perhaps in this case i should set RP in netwoker and set RP in RMAN to none and rely on crosscheck and delete expired commands to sync with RNAM catalog.
    2. Wondering if nightly backup of recovery area to tape is going to take incremental from previous day and NOT full backup. The reason i ask is, i do not want the tape to do full backup of FRA every day cause full backup datafiles change once in 3 days based on the until time set. is there an option do set in networker to do incremental only or that's the default.
    Thanks in Advance!
    11gR2, 4 Node RAC, Linux, NMDA 1.1, Networker 7.6 sp1

    Loic wrote:
    You do a full backup of the FRA on tape ?No, I do a full backup of the database on tape. Using RMAN together with Veritas NetBackup.
    I mean if you use incremental updated backup it'll not work on tape... Because the level 0 backup that will be updated with the backup of the day after will be on tape and will not be updated.The incrementally updated backup is in the FRA only, on disk (both the image copy and the following backup sets that are used for recovery of the image copy). Never gets written to tape or updated on tape.
    Why don't you use then normal incremental backup ? That will have no problem with the tape backup even if level0, or level1,2 becomes reclaimable... ?I think I do :-)
    Maybe:
    To keep that you can put the redundancy to 2 out of 1 copy. Like this even with one copy on disk and tape it'll say keep the 2 copies.
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;I'll think about that.

  • NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES

    제품 : RMAN
    작성날짜 : 2004-05-20
    NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES
    =======================================================
    오라클 9i RMAN 에서는 백업을 보다 효율적으로 할 수 있는 기능을 보강 했다.
    지금 소개할 "Retention Policies" 기능을 통해서 보다 효율적인 RMAN 백업
    전략을 세울 수 있다.
    1. 백업 화일 최적화 방법 (Backup File Optimization)
    백업 화일 최적화란 백업에 소요되는 공간을 최소화 하는 전략이다. RMAN
    백업시에 같은 정보 (dbid, checkpoint, and resetlogs data 등등) 를 가지고 있는
    화일이 이미 존재하는 백업 셋 내부에 있는지 체크하게 된다. 만일 같은 화일이
    이미 백업 되어 있다면 BACK UP 명령은 해당 화일에 대해서는 백업을 하지 않게
    된다.
    이때 같은 화일이라고 판단하는 기준은 다음과 같다.
    * Datafile: 같은 DBID, checkpoint SCN, resetlogs SCN 과 time. 데이타 화일은
    반드시정상적으로 offline 되었거나, read-only 이거나, 또는 정상적 으로 close
    되어야 함.
    * Archived redo log: 같은 thread, sequence number, 그리고 같은 Resetlogs
    SCN 과 time.
    * Backup Set: 같은 Backup Set recid 와 stamp.
    RMAN 이 백업을 수행하다가 위와 같은 조건의 화일이 이미 존재함을 확인하면
    이것은 건너뛰게 될 화일의 대상이다. 하지만 이때 바로 Skip 을 결정하지 않고
    정해진 Retention Policies 를 조사 한후에 Skip 여부를 결정 하게 된다.
    만일 백업 명령에 DELETE INPUT option 이 사용되면 RMAN 은 백업이 Skip
    되어도 화일을 지우게 된다.
    RMAN 은 모든 화일에 대한 백업이 Skip 되어도 에러메시지나 경고를 보내지
    않는다.
    그러나 만일 데이터 화일에 대한 백업이 recovery policy window 보다 오래
    된 것 이면 RMAN 은 새로운 백업 화일을 만들기 위해서 화일을 백업 하게 된다.
    Note:
    자체적인 expirations policy 를 가지고 있는 media manager 를 사용할 경우에는
    이런 백업 최적화 정책을 사용하는 것에 신중을 기해야 한다.
    백업 최적화 를 사용하기 위해서는 CONFIGURE 명령을 사용한다. CONFIGURE
    명령은 명령 수행 이후에 이루어지는 모든 백업에 대해 적용이 된다.
    예:
    CONFIGURE BACKUP OPTIMIZATION ON; # default 는 OFF
    2. Backup Optimization에 Retention Policies 적용 하기
    Retention Policy 로 백업 최적화를 조절 할 수 있다. 그러나 retention policy를
    사용하지 않기 위해서는 'CONFIGURE RETENTION POLICY TO NONE' 을
    이용해서 명시적으로 retention policy를 사용하지 않는다고 해야 한다. 디폴트로
    REDUNDANCY = 1 이 적용 된다.
         a. Recovery Window 를 이용한 Backup Optimization
    만일 백업 최적화가 enable 되어 있고 Recovery Window 가 retention policy
    적용을 위해서 셋업 되어 있으면 RMAN 은 항상 가장 최근의 백업이 Recovery
    Window 보다 오래된 데이터 화일을 백업한다.
    예를 들면 다음과 같은 조건에서
    o Today is February 21.
    o The recovery window is 7 days.
    o The most recent backup of tablespace tbs2 to tape is January 3.
    o Tablespace tbs2 is read-only.
    2월 21일에 tbs2 테이블 스페이스를 테이프로 백업을 하라는 명령을 내리면,
    RMAN 은 이 화일이 1월3일 이후에 변경 사항이 없는데도 불구 하고 백업을 하게
    된다. 이로써 RMAN 은 최근 7일 동안에 최소한 한번의 백업이 있어야 된다는
    조건을 지키게 된다.
    이러한 작동 방식은 media manager 가 오래된 테잎을 제거 해도 되도록 한다.
    그렇지 않다면, media manager 는 1월 3일의 백업을 무한정 가지고 있게 된다.
    2월 21일에 tbs2 테이블 스페이스의 보다 최근의 백업을 만듦으로 써, RMAN 은
    media manager 가 1월 3일에 백업 했던 테입을 지워도 되도록 한다.
         b. Redundancy 를 이용한 Backup Optimization
    Retention policy 로 Redundancy 를 채택 한 경우에 RMAN 은 Redundancy
    에 1을 더한 갯수를 초과하는 오프라인 또는 읽기 전용 화일의 백업을 건너뛴다.
    이때 'CONFIGURE RETENTION POLICY TO REDUNDANCY n' 명령어로
    Redundancy의 갯수를 정한다.
    아래와 같은 백업 최적화 명령을 내린 경우를 예로 든다:
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    아카이브 테이블스페이스를 한번도 백업을 받은적이 없고 다음의 작업을 1주일
    동안 한다고 하자.
    Day Action Result Redundant Backup
    Monday Take tablespace archive offline clean.
    Tuesday Run BACKUP DATABASE. The archive tablespace is backed up.
    Wednesday Run BACKUP DATABASE. The archive tablespace is backed up.
    Thursday Run BACKUP DATABASE. The archive tablespace is backed up. Tuesday backup.
    Friday Run BACKUP DATABASE. n/a Tuesday backup.
    Saturday Run BACKUP DATABASE. n/a Tuesday backup.
    Sunday Run DELETE OBSOLETE. The Tuesday backup is deleted.
    Monday Run BACKUP DATABASE. The archive tablespace is backed up. Wednesday backup.
    화요일, 수요일, 그리고 목요일의 백업은 아카이브 테이블 스페이스를 복사 해서
    3개의 백업이 반드시 존재 해야 한다는 조건을 충촉 시킨다. (1+Redundancy)
    금요일과 토요일에는 백업 최적화 조건에 의해서 아카이브 테이블 스페이스를
    복사하지 않게 된다.
    RMAN 은 일요일에는 유효기간이 지난 백업 화일을 지우게 된다. 따라서 화요일에
    만든 백업은 삭제 된다. 월요일의 전체 백업은 3개의 백업이 존재 해야 한다는 조건
    때문에 아카이브 테이블 스페이스를 또 다시 백업하게 된다. 이런 방식으로 백업
    사이클이 진행 된다.
    3. RETENTION POLICY NONE vs. DEFAULT
    주의 사항:
    'CONFIGURE RETENTION POLICY TO NONE' 과 'CONFIGURE RETENTION
    POLICY TO DEFAULT' 는 그 의미가 같지 않다. 전자는 RETENTION POLICY
    자체가 존재 하지 않는다는 의미 이며 백업은 expire 되지 않으며 'DELETE
    OBSOLETE' 명령은 사용 할 수 없게 된다. 후자는 디폴트 RETENTION POLICY
    (REDUNDANCY 1) 를 사용하게 된다는 의미 이다.
    'DELETE OBSOLETE' 명령은 RETENTION POLICY 기준으로 expire 된 백업을
    제거 하라는 명령이다.
    보다 자세한 내용은 Oracle9i Recovery Manager User's Guide and
    Reference의 Backup Optimization 부분을 참고 하시기 바랍니다.
    --------------THE END----------------------------------------------

    Hi,
    Backup optimisation = +- do not copy empty space.
    So, when you issue your BACKUP statement, it backs up the datafile. dot. nothing more.
    In order to achieve what you're testing, look into TFM for BACKUP INCREMENTAL LEVEL x .
    Regards,
    Yoann.

  • INCREMENTAL MERGE BACKUP & RECOVERY

    INCREMENTAL MERGE BACKUP & RECOVERY
    =====================================
    1) 개요
    RMAN을 이용하여 database의 Image copy를 Backup하고 그 Backup에 retention policy만큼의 Incremental Backup을 적용하여서 복구의 시간을 단축한 Backup의 방법입니다.
    즉 retention policy에 설정되어있는 시간 전의 최후의 시간까지 Image Copy를 보장하는 방법이며 Disk Space는 Incremental Backup만 사용하는 방법보다는 Image Copy를 사용하는 것임으로 많이 소요됩니다.
    물론 Backup & Recovery 정책에 따라서 Retention Policy를 Recovery Window나 Redundancy 2이상으로 설정할 수 있으나, Incremental Merge Backup & Recovery의 장점을 극대화 하기 위해서는 Redundancy 1 (Default)로 설정하는 것을 권해드립니다.
    2) 장점
    - Recovery 시에 최근 Incremental Backup의 정보들이 적용이 되어있기 때문에 최소한의 시간으로 Recovery 작업을 진행하실 수 있습니다. 물론 장점을 극대화 하시기 위해서는 Retention Policy를 redundancy 1로 설정해 주시길 권해드립니다.
    - Datafile들의 Destination을 Backup된 Image Copy가 있는 곳으로 Switch 하여 Restore하는 시간을 단축하셔서 Recovery를 진행하실 수도 있으나 Recovery 후의 관리의 용이성을 위해 부득히한 경우를 재외하고는 권장하지 않습니다.
    3) Syntax
    - Backup
    RMAN> BACKUP INCREMENTAL LEVEL 1
    FOR RECOVER OF COPY
    WITH TAG WEEKLY DATABASE;
    위 명령어를 사용하시면 WEEKLY라는 Tag로 생성된 Copy가 없을 시에는 Image Copy를 Weekly라는 Tag로 구분하여 Backup을 받게 됩니다.
    * 여기서 Copy라 함은 FOR RECOVER OF COPY라는 구문을 사용하여서 만든 Image Copy를 뜻합니다.
    RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY;
    위 명령어를 사용하시면 현재 받았던 Incremental Backup을 Weekly라는 Tag를 가지고 있는 Database Copy에 적용을 하게 됩니다.
    RMAN> Delete Obsolete;
    위 명령어를 사용하시면 현재의 Image Copy에 적용된 Incremental Backup을 재외한 나머지 Incremental Backup들이 Delete됩니다.
    -Recovery
    RMAN> switch database to copy;
    문제가 발생하셨을 때 위 명령어를 사용하시면 모든 datafile의 pointer들은 image backup copy를 바라보게 됨으로 Restore의 시간을 절약할 수 있습니다.
    4) Retention Policy에 따른 Syntax 변화
    * 기본적으로 INCREMENTAL MERGE BACKUP & RECOVERY의 장점인 Recovery 시간을 극대화 하기 위해서는 Retention Policy를 redundancy 1(Default)로 설정하시는 것을 권장해드립니다.
    하지만 User가 Backup & Recovery 계획을 변경하여 retention policy를 recovery window 또는 redundancy 1 이상으로 설정해 주시면 Obsolete한 Backupset을 Delete하는 부분과 Backupset을 적용시키는 부분을 수정해 주셔야합니다.
    - Recovery Window of 2
    Recovery Window를 2일로 설정해 놓으시면 Backup시에는 똑같은 Syntax를 사용하실 수 있으나 Recover copy of database 명령어는 아래와 같이 바뀌어야 합니다.
    RMAN> BACKUP INCREMENTAL LEVEL 1
    FOR RECOVER OF COPY
    WITH TAG WEEKLY DATABASE;
    RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY until time 'sysdate-2';
    왜냐하면 retention policy에 마춰서 image copy도 2일전의 상태로 보관되어야하며 그에 따라서 2일동안의 Backupset들도 보관되어야하기 때문입니다. 만약 until time을 사용하지 않으시면 incremental backup들이 obsolete 상태로 안변하게 됩니다.
    - Redundancy 2 이상
    Redundancy 2이상으로 설정해 주시면 2개 이상의 Tag를 보관하는 효과로서 역시 예상대로 Obsolete로 안 변하는 현상이 발생됩니다.
    DAY 1)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag DAILY)가 생성됩니다.
    DAY 2)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag WEEKLY)와 한개의 Backupset (Tag DAILY)가 생성됩니다.
    DAY 3)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG MONTHLY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag MONTHLY)와 두개의 Backupset (Tag DAILY, Tag WEEKLY)가 생성됩니다.
    DAY 4)
    RMAN> Delete Obsolete;
    - 위와 같이 실행하시면 DAILY Tag와 관련된 부분이 Delete 됩니다. (최신 2개의 Tag관련 Backup만 보관)
    RMAN> Delete Obsolete redundancy 1
    - 위와 같이 실행하시면 DAYLY Tag와 WEEKLY Tag 관련된 부분이 Delete 됩니다. (Redundancy 1로 설정한 것과 똑같은 효과)
    Reference:
    Article-ID: Note 351455.1
    Title: Oracle Suggested Strategy & Backup Retention
    Article-ID: Note 303861.1
    Title: Incrementally Updated Backup In 10G
    글 수정:
    hunlee

    I would always include an archivelog backup:
    ... with tag 'fullbackup’ database plus archivelog delete all input;
    And at the end:
    delete obsolete noprompt;
    That delete incrmental backups already applied to the basic image copies.
    Your configuration allows only limited point in time recoveries. As soon as an incremental backup is applied to the image copies, you cannot go back in time. To change this you can add a 'until time' clause, for example:
    recover
    copy of database
    with tag 'fullbackup until time 'sysdate-11';
    This creates a recovery window of 10 days, only image copies older than 10 days will be changed.
    Werner

  • Need Advice on RMAN backup script

    Hi;
    Can any one advice if any error or guide to make RMAN backup proper :
    Backup Policy are:
    1.     0 level backup
    2.     current log file is arvhived before backing up
    3.     backup whole database (datafiles)
    4.     backup separate control file
    5.     backup is done on disk
    6.     control file auto backup ON
    7.     only 7 days archive log are need to be preserve ; old need to be deleted
    ### one time paramters seting
    RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    ### Command for weekly 0 level backup
    run {
    allocate channel c1 type disk;
    sql 'alter system archive log current';
    backup incremental level 0 tag = weekly_database format 'o:\rman\backup\full_weekly_%d_%s_%p_%t'(database);
    release channel c1;
    configure controlfile autobackup format for device type disk to 'o:\rman\backup\auto_ctrl_weekly_%f';
    allocate channel c1 type disk;
    backup tag = weekly_arch archivelog until time 'sysdate-7' format 'o:\rman\backup\archive_weekly_%d_%s_%p_%t';
    delete archivelog until time 'sysdate-7';
    release channel c1;
    Regards
    Smith

    Dear Pierre F.;
    Actually, I just added in my backup plan to have daily backup through RMAN, instead of COLD backup.
    I have planned to take cold backup once a week. here is the side of data:
    *** datafile 410
    *** size of database : 86 GM
    *** relog files size : 250MB
    *** daily archive logs are : 250MB * 4(number of files) = 1GM aprox.
    yes, time constraint is there; just because of the size of database. and we r going for 24/7
    Is this script going to run only one per week ?
    Ans: no I this was level 0 backup; i will take level 1 incremental backup with same script daily too.
    Do you have any other RMAN script ?
    ANS: no, I will modify same script for incremental.
    after local copy of backup all backup files (RMAN) will be copy over network to backup server or we can install LTO tape device to copy directly from database server.
    kindly advise me I am new in RMAN.
    regards;
    SMITH

  • RMAN backup files are still exist since long time, how to delete?

    Dear sir;
    I'm using the below script to do daily backup, however there are many rman backup files are still exist and consumes HD size, how could I delete these files in daily bases? some files dated in FEB, MAR, APR,
    ============Daily RMAN script=========
    rman target /<<!
    backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
    backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
    backup current controlfile format '/u15/rman/control_%U.rman';
    delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
    delete noprompt obsolete;
    ================================END
    Thanks and best regards
    Ali

    Hi;
    Our backup policy should have 7 days; however we have here some files from JAN, FEB,MAR, APR /2012 WHICH ARE BEYOND THE RETENTION DATE and these files should be deleted by executing " delete noprompt obsolete; ".
    All files are exist in /u15/rman/
    -rw-r----- 1 oracle oinstall 1151763968 Jan 21 01:36 arc_backup_7kn19h4a_1_1.rman
    -rw-r----- 1 oracle oinstall 1136882176 Jan 21 01:36 arc_backup_7ln19h4q_1_1.rman
    -rw-r----- 1 oracle oinstall 1135984640 Jan 21 01:36 arc_backup_7mn19h5a_1_1.rman
    -rw-r----- 1 oracle oinstall 1126627328 Jan 21 01:37 arc_backup_7nn19h5q_1_1.rman
    -rw-r----- 1 oracle oinstall 880606720 Mar 12 02:53 arc_backup_7nn5ldhp_1_1.rman
    -rw-r----- 1 oracle oinstall 1093043712 Jan 21 01:37 arc_backup_7on19h6a_1_1.rman
    -rw-r----- 1 oracle oinstall 9797632 Dec 15 01:04 control_04mu7tcp_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 3 02:55 control_4cn4tm9k_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 4 02:53 control_4on50ahm_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 5 02:55 control_56n52v1j_1_1.rman
    -rw-r----- 1 oracle oinstall 16252928 Jan 23 01:40 control_8tn1eq3t_1_1.rman
    -rw-r----- 1 oracle oinstall 16252928 Jan 24 01:40 control_9cn1heg0_1_1.rman
    -rw-r----- 1 oracle oinstall 202940416 Dec 15 01:04 full_backup_01mu7t50_1_1.rman
    -rw-r----- 1 oracle oinstall 1097728 Dec 15 01:04 full_backup_02mu7tcc_1_1.rman
    -rw-r----- 1 oracle oinstall 201285632 Dec 14 01:04 full_backup_0nmu58ou_1_1.rman
    -rw-r----- 1 oracle oinstall 5957304320 Feb 29 02:46 full_backup_2ln4g9l1_1_1.rman
    -rw-r----- 1 oracle oinstall 4128768 Feb 29 02:47 full_backup_2mn4gft8_1_1.rman
    -rw-r----- 1 oracle oinstall 6027075584 Mar 1 02:49 full_backup_32n4o6ov_1_1.rman
    -rw-r----- 1 oracle oinstall 4128768 Mar 1 02:49 full_backup_33n4od66_1_1.rman
    -rw-r----- 1 oracle oinstall 6187171840 Mar 2 02:51 full_backup_3gn4qr50_1_1.rman
    -rw-r----- 1 oracle oinstall 4145152 Mar 2 02:51 full_backup_3hn4r1kn_1_1.rman
    -rw-r----- 1 oracle oinstall 6115786752 Mar 3 02:51 full_backup_40n4tfgu_1_1.rman
    above is a short list of contents.
    to do our daily backup we perform the following script (in daily)
    ==================
    backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
    backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
    backup current controlfile format '/u15/rman/control_%U.rman';
    delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
    delete noprompt obsolete;
    ==================
    Thanks and best regards
    Ali

  • Oracle RMAN backup to disk on vbox4.2 shared folders

    [https://forums.virtualbox.org/viewtopic.php?f=7&t=53683]
    Cross posting a virtualbox forum post in case someone has this working.
    [posting snippet]
    Anyone successfully using Oracle 10.2/11.2 RMAN to backup to mounted vbox guest shared folder? I'm thinking there may be some special configuration requirement like there is with NFS share mount options.
    RMAN> backup incremental level = 0 database include current controlfile plus archivelog delete input;
    [lengthy output clipped]
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup plus archivelog command at 01/18/2013 00:03:14
    ORA-19504: failed to create file "/media/sf_backup/vux099/oracle/vux099db/dataS217_P1_T804988992"
    ORA-27040: file create error, unable to create file
    Linux-x86_64 Error: 22: Invalid argument
    Additional information: 2
    RMAN>
    Recovery Manager complete.
    oracle@vux099:vux099db1 [app/oracle]
    $ touch /media/sf_backup/vux099/oracle/vux099db/myfile; ls -l /media/sf_backup/vux099/oracle/vux099db/myfile
    -rw-r--r-- 1 oracle oinstall 0 Jan 18 00:04 /media/sf_backup/vux099/oracle/vux099db/myfile
    oracle@vux099:vux099db1 [app/oracle]
    $ touch /media/sf_backup/vux099/oracle/vux099db/myfile;
    oracle@vux099:vux099db1 [app/oracle]
    $ mount | grep sf_backup
    backup on /media/sf_backup type vboxsf (uid=51115,gid=51116,rw)
    oracle@vux099:vux099db1 [app/oracle/base/admin/vux099db1/bin]
    $ getent passwd 51115; getent group 51116
    oracle:*:51115:51116:Oracle Administrator:/app/oracle:/bin/bash
    oinstall:*:51116:grid,oracle
    oracle@vux099:vux099db1 [app/oracle/base/admin/vux099db1/bin]
    $ printf "show all;\nexit\n" | rman nocatalog target / | grep DISK
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/media/sf_backup/vux099/oracle/vux099db/%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/media/sf_backup/vux099/oracle/vux099db/dataS%s_P%p_T%t';
    oracle@vux099:vux099db1 [app/oracle/base/admin/vux099db1/bin]
    $
    [end]
    Edited by: user12130856 on Jan 18, 2013 8:08 PM

    Hi,
    never tried it, but I know that the shared folders in vbox don't work like normal filesystems.
    I would rather setup an NFS server on the host and mount an NFS share in the guest.
    Regards
    Sebastian

  • How to stop a rman backup in progress?

    OS: AIX 5.3 L and Oracle 10g R2
    I got panic when my scheduled rman backup (incremental level 0 plus archivelog) run too long and I want to stop the process. I could not find the rman doc mentioning how to use any rman command to do that, instead of just shutdowning the database instance.with ps -ef, there were just too many PID of oracle. Is there a way by rman to STOP the process?
    Furthermore, I had no idea why it happened. Last week when I did a full copy backup, it only took 23 minutes for 32G database, Today, I changed the scheme to a level 0 incremental, and it is still running after 5 and half hours. But it already created the archivelog, datafile backupset (checked by the DB control). How to find out what went wrong?

    I did not use any third party application with rman or TSM in my AIX. what is the tdpo? Killing at OS level is probably only thing I can do now. kill -9 PID#
    Message was edited by:
    user508054
    Message was edited by:
    user508054

  • Related to Unused compression in RMAN backup for 10.2.0.4 database

    Hi
    I recently read through one of the document related to Unused compression in RMAN backup for 10.2.0.4 database. According to this
    Unused Block Compression is done, if all of the following conditions apply:
    + The COMPATIBLE initialization parameter is set to 10.2
    + There are currently no guaranteed restore points defined for the database
    + The datafile is locally managed
    + The datafile is being backed up to a backup set as part of a full backup or a level 0 incremental backup
    + The backup set is being created on disk.
    I have two queries
    1) What is meant by "uaranteed restore points defined for the database"
    2) If backup is being directly taken to tape, this feature would not be used
    Rgds
    Harvinder

    1. Normal and Garanteed Restore Points
    2. No

Maybe you are looking for