Rman backup optimization question

Hi,
I have come across a RAM related question and would like to understand the answer:
The RMAN configuration has backup optimization set to ON. Which of the following commands will this setting affect?
a) Backup Archivelog with ALL or LIKE options, b) Backup Backupset ALL, c) Backup Tablespace, d) Backup Database
I believe all of the above are affected by backup optimization, however, only a, b and d seems correct, not c. I wonder why tablespace is not affected - it does not say read only, etc.?
Any ideas? Thanks.

Thanks for the quick response!
Meanwhile I did a few tests below, and yes, tablespace does obviously not use backup optimization. But why? Doesn't the same like backup database apply? Isn't using the same retention policy?
RMAN> backup database;
skipping datafile 5; already backed up 2 time(s)
RMAN> backup archivelog ALL;
skipping archived log file /u02/fra/ORCL/ar...; already backed up 1 time(s)
RMAN> backup tablespace example;
input datafile file number=00005
piece handle=/u02/fra/ORCL/backupset....
RMAN> backup tablespace example;
input datafile file number=00005
piece handle=/u02/fra/ORCL/backupset....

Similar Messages

  • 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.

  • RMAN : BACKUP OPTIMIZATION ON

    Hi All,
    I have a doubt about BACKUP OPTIMIZATION ON parameter..
    If Any one worked, can u tell me the exact use of this parameter....
    Regards,
    Prabhu.

    Used to enable or disable backup optimization. Backup file optimization can assist in reducing the space used to backup the database. When performing an RMAN backup, a check is done on the file before backup to see if the file already exists in a backupset with the same information: (dbid, checkpoint, and resetlogs data).
    For archive logs, the same file means the same dbid, thread, sequence, and resetlogs data. If the DELETE INPUT option is used, RMAN deletes all the files that would have been backed up, even when the file is not included due to file optimization.
    The two possible values for backup optimization is ON and OFF as shown in the following example syntax:
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE BACKUP OPTIMIZATION ON;
    Use caution when enabling backup optimization if you use a media manager that has an expiration policy. The media manager can expire tapes containing backups (using its media control software), and RMAN will not make new backups because of optimization. One way to protect from this is to run CROSSCHECK periodically to synchronize the repository with the media manager.
    Also note that you should consider how backup optimization works with regards to the RETENTION POLICY. RMAN will only work with files within the retention period. For example, consider performing a backup with optimization enabled and a retention period of 3 days. RMAN will only compare the datafile with backup sets within the 3 day period - even if the datafile it is about to backup hasn't changed within that 3 days.
    ofcourse the best reference is here

  • RMAN backup Optimization

    Hi gurus
    I would like to know that if I enable backup Optimization on then incremental full backup skip any files which was earlier backup? Because we may know that backup Optimization on ensure skip those files which are already taken backup.
    Database : oracle 10g 10.2.0.3
    Rabi

    None.
    Under OPTIMIZATION, an Incremental Full (i.e. L0) backup would skip a file only if it has not changed since the last L0 backup --- which wouldn't be the case with most database files.
    Even when you run Incremental Differential or Incremental Cumulative (i.e. L1 or higher) backups, the file would not be skipped.
    Hemant K Chitale

  • RMAN backup  tag question

    I am little confused even after I read the RMAN doc. If I have a full level 0 backup tag "mybk$level_0" database, then my level 1 incremental backup tag has to be the same - "mybk$level_1" or "mybk$level_0".
    I just run the incremental backup through the whole weekend and noticed the each run would generated two identical "spfile, controlefile" backup, one before the archivelog backup, one after it. Why?

    The tag name can be the same as what you set. Tag names can be of different names and different formats, does not need to be a specific name. You can replace mybk with myarchive if you think that is more meaningful. You can also attach date and time variable with the tags to make them more meaning full.
    It doesn't have to be this way,
    { backup incremental level 1 cumulative device type disk tag 'mybk%LEVEL_1' database;
    recover copy of database;
    backup device type disk tag 'mrarchive' archivelog all not backed up; }
    If you are calling the rman backup from shell script you can attach the dates to tags as below.
    export TDATE=`date +%a%m%d%y`
    tag="Archive_${TDATE}"
    or
    tag "Archive_${TDATE}"
    Below note if from one of the online resources available:
    Tags for Backups and Image CopiesYou can assign a user-specified character string called a tag to backup sets and image copies (either copies created by RMAN or copies created by an operating system utility). A tag is a case-insensitive symbolic name for a backup set or file copy such as weekly_backup. You can specify the tag rather than the filename when executing the RESTORE or CHANGE command. The maximum length of a tag is 30 characters.
    If you do not specify a tag name, then by default RMAN creates a tag for backups and copies (except for control file autobackups) in the format TAGYYYYMMDDTHHMMSS, where YYYY is the year, MM is the month, DD is the day, HH is the hour (in 24-hour format), MM is the minutes, and SS is the seconds. For example, a backup of datafile 1 may receive the tag TAG20020208T133437. The date and time refer to when RMAN started the backup. If multiple backup sets are created by one BACKUP command, then each backup piece is assigned the same default tag.
    When applied to a backup set, a tag applies to a specific copy of the backup set. If you do not duplex a backup set, that is, make multiple identical copies of it, then a one-to-one correspondence exists between the tag and the backup set. For example, BACKUP COPIES 1 DATAFILE 7 TAG foo creates one backup set with tag foo. However, you can back up this backup set and give this new copy of the backup set the tag bar. So, the backup set has two identical copies: one tagged foo and the other tagged bar.
    Tags do not need to be unique, so multiple backup sets or image copies can have the same tag name, for example, weekly_backup. When a tag is not unique, then with respect to a given datafile, the tag refers to the most current suitable file. By default, RMAN selects the most recent backups to restore unless qualified by a tag or a SET UNTIL command. The most current suitable backup containing the specified file may not be the most recent backup, as can occur in point-in-time recovery.
    For example, if datafile copies are created each Monday evening and are always tagged mondaypmcopy, then the tag refers to the most recent copy (assuming that no SET UNTIL command is issued before restore or recovery). Thus, if complete recovery is desired, this command switches datafile 3 to the most recent Monday evening copy:
    SWITCH DATAFILE 3 TO DATAFILECOPY TAG mondaypmcopy;
    Tags can indicate the intended purpose or usage of different classes of backups or file copies. For example, datafile copies that are suitable for use in a SWITCH can be tagged differently from file copies that should be used only for RESTORE.
    Note:
    If you specify a tag when specifying input files to a RESTORE or SWITCH command, then RMAN considers only backup sets with a matching tag when choosing which backup to use

  • RMAN Backup/Recover question

    Should I be able to back up a db using RMAN in a 10.1.0.2 installation and recover using RMAN in a 10.1.0.3 installation (using same OS, etc.)?

    user13419193 wrote:
    Hii..
    Thanks for reply and I got yr point.
    But Sorry for again questioning, here i want database recovery on same server.
    Than what to do?
    Do i have to create database thriough dbca on same server??
    RegardsWhere are your backup files now? Confirm you still have them and they didn't get dropped as part of your deleting/dropping the database.
    If, as you say, you deleted the entire database, there really is no concept of 'same server'. You want to restore/recover the database onto a server which does not currently have any copy/version of that particular database. Whether or not there ever WAS one on that box is pretty much meaningless, except for the fact there may be some bits and pieces we can use. But the basic technique is the same.
    You haven't state your OS, which is important. If its Windows, you'll need to use oradim to recreate the service. Once that is done, rman can connect to an 'idle' instance and proceed from there.
    Once rman connects to an idle instance, you restore the control file from backup, then mount the database (open the control file) then restore and recover the db. rman will use information in the resotred control file to locate the backupsets and process the rest of the operation. there are details that need to be attended to but that's the overall outline.
    Edited by: EdStevens on Oct 7, 2011 8:37 AM

  • Rman backup Compress question

    Oracle ver 10.2.0.1 -- 24/7
    250G database. I ran the script
    run {
    allocate channel c1 type disk format '/hotbackup/%d/db_%d_t%t_s%s_p%p%c';
    set limit channel c1 kbytes 2024800;
    sql "alter system archive log current";
    backup as compressed backupset
    incremental level 0
    filesperset=20 (database include current controlfile);
    release channel c1;
    # Backup all archive log files
    allocate channel t1 type disk format '/hotbackup/%d/al_%d_%s_%p%c';
    backup as compressed backupset filesperset=20 (archivelog all delete input);
    release channel t1;
    delete noprompt backup completed before 'sysdate-1';
    And the backup file is still around 220G. Is there another way to compress? Anybody have an idea how to make the backup smaller?
    Thank You

    How many CPU's does your server have?
    And why don't you let RMAN choose the default's regarding the files per set, the backup set piece size, etc. Whenever you run a compressed backup, RMAN would normally use at approx.12% of CPU per channel. A 45hr backup time is clearly unacceptable that too when it is a 24/7 database but as your are using a single channel, which might be the culprit. I would suggest to use about 4 channels (depending on your CPU load) and do not put any restrictions on the files per set and backup set piece size.
    We do a compressed backup to disk of a 230G database on a 8 proc server with 4 channels allocated and the backup normally completes in about 1.45 hours and the FULL backup size produced is around 30G ( level 0 is a FULL backup).

  • RMAN Backup Plan Question

    Hello -
    If I'm backing up specific datafiles (say 3 datafiles in one RMAN script) and I have 4 of these scripts - so a total of 12 files being backup up, should I have a separate script that just backs up all of the archived log files? Or should I include a Backup Archivelog all command in each specific script?

    backup each datafile once according to your backup shedule there is no advantage of backup each data file foure times it conversly decrade or slow down your backup working. there is no need to include archive logs in your scripts. I think you should create seprate sript for archived logs.

  • 11g RMAN UNDO backup optimization

    Hi all?
    I have tested 11g RMAN UNDO backup optimization
    1st I fill the undo tablespace by sql manipulations and not commiting
    2nd backed undo_ts up by RMAN (size 24m)
    3rd I made a commit
    Then backed undo tablespace again but backup_size didn’t change     (24m)
    Then I made some more manipulations and backed undo_ts again. This time backup_size reduced. (11m)
    Then I restarted db and backed up undo_ts again. This time backup size became what I expected (600K)
    The question is why 11g rman undo tablespace backup size didn’t reduce after commit?
    according to 11g undo optimization it had to
    SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
    SUM(BYTES)
    13172736
    SQL> begin
    for i in 1..100000 loop
    insert into testundo values(i);
    end loop;
    end;
    2 3 4 5 6
    PL/SQL procedure successfully completed.
    SQL> SQL> update testundo set
    id=2 where id>0;
    2
    update testundo set
    ERROR at line 1:
    ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
    SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
    SUM(BYTES)RMAN> backup datafile 6;
    RMAN> list backup of datafile 6;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    10 Full *24.54M* DISK 00:00:04 10-JUN-10
    BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142437
    Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
    List of Datafiles in backup set 10
    File LV Type Ckp SCN Ckp Time Name
    6 Full 577669 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
    SQL> commit;
    Commit complete.RMAN> backup datafile 6 format 'after commit.backup';
    RMAN> list backup of datafile 6;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11 Full *24.54M* DISK 00:00:02 10-JUN-10
    BP Key: 11 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142541
    Piece Name: /home/oracle/product/11/Db_1/dbs/after commit.backup
    List of Datafiles in backup set 11
    File LV Type Ckp SCN Ckp Time Name
    6 Full 577705 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
    SQL> alter system archive log current;
    System altered.
    SQL> commit;
    Commit complete.
    SQL> select count(*) from testundo;
    COUNT(*)
    100000
    SQL> delete from testundo;
    100000 rows deleted.
    SQL> commit;
    Commit complete.
    SQL> insert into testundo values(1);
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> alter system flush buffer_cache;
    System altered.RMAN> backup datafile 6;
    RMAN> list backup of datafile 6;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    13 Full *11.03M* DISK 00:00:01 10-JUN-10
    BP Key: 13 Status: AVAILABLE Compressed: NO Tag: TAG20100610T143359
    Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
    List of Datafiles in backup set 13
    File LV Type Ckp SCN Ckp Time Name
    6 Full 578410 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
    RMAN>
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 393375744 bytes
    Fixed Size 1300156 bytes
    Variable Size 352323908 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 6197248 bytes
    Database mounted.
    Database opened.
    SQL> RMAN> backup datafile 6;
    RMAN> list backup of datafile 6;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    14 Full *600.00K* DISK 00:00:02 10-JUN-10
    BP Key: 14 Status: AVAILABLE Compressed: NO Tag: TAG20100610T152843
    Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
    List of Datafiles in backup set 14
    File LV Type Ckp SCN Ckp Time Name
    6 Full 580347 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
    Thanks in advance
    Turkel

    Hi Turkel,
    The space used for undo is also related to the undo retention setting.
    As it seems you do a test update and proceed with backups on:
    - 14:24:37 (-> 25M)
    - 14:25:41 (-> 25M)
    - 14:33:59 (-> 11M)
    - 15:28:43 (-> 600K)
    The first two backups probably are still within the undo retention period for the update.
    The third backup shows a partly empty undo (is your setting 900?).
    The last falls outside the retention period for the update resulting in the small backup size.
    Regards,
    Tycho

  • RMAN backup and TSM question

    We have rman backup file name contains the datetime so it is unique and easy to tell. But TSM keeps every file 4 versions, so the backup file (always 1 version because of unique name) will stay on tape forever. I have no idea about TSM, according to your experience, what is the normal solution here?

    Dedicated forum for {forum:id=74}.
    But quickly, in general, "DBA" and "TSM/Storage manager" need to agree on media manager use and setup the system accordingly.
    Edited by: orafad on May 19, 2011 3:00 PM

  • Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

    I will explain my scenario below:
    We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
    Please suggest me the best way forward...
    Many Thanks
    Nukesh

    Hi Asif,
    I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
    RMAN> list incarnation;
    using target database control file instead of recovery catalog
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
    2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
    3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
    RMAN> exit
    TEST1DB-> rman target sys@MYTEST1
    Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    target database Password:
    connected to target database: MYTEST (DBID=2433328848, not open)
    RMAN> reset database to incarnation 2;
    using target database control file instead of recovery catalog
    database reset to incarnation 2
    RMAN> run {
    2> restore database until scn 10000;
    3> recover database until scn 10000;
    4> alter database open resetlogs;
    5> };
    Starting restore at 07-NOV-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/07/2010 11:45:18
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
    RMAN-01007: at line 0 column 2 file: standard input
    RMAN>
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO 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 '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
    RMAN> exit
    SQL> select name from v$database;
    NAME
    MYTEST
    SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    SQL>

  • RMAN backup on RAC

    Hi,
    DB=10.2.0.4 OS=RHL (RAC with 2 nodes db01,db02). Following are the types of automated RMAN backups taken on db01.
    - OCR
    - Voting Disk
    - Talespaces Snapshot
    - Archivelog (every hour)
    - Backup Incremental level 0 (SUNDAY)
    -- backup incrementa level 1 (Mon-SAT)
    - Autobackup of Control file and SPFILE (CONTROLFILE AUTOBACKUP ON)
    Two main questions please. First, are these backups/backup types are enough FOR FULL RESTORE when talking about RMAN backup on RAC environment with 2 nodes? If not please suggest what else I need to backup?
    Secondly, backup home location is /rman which I can see on db01 ONLY. This /rman directory I cannot see on db02. My question is that In case of db02 failure can I restore from this /rman directory? or do I need to automate backup schedules also on db02 separately?
    [root@db01~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                          3.9G  2.9G  814M  79% /
    /dev/sda3             190M   34M  147M  19% /boot
    tmpfs                  16G     0   16G   0% /dev/shm
    /dev/mapper/VolGroup00-LogVol05
                          3.9G  137M  3.6G   4% /home
    /dev/mapper/VolGroup00-LogVol03
                          3.9G  225M  3.5G   6% /tmp
    /dev/mapper/VolGroup00-LogVol02
                          7.8G  3.7G  3.8G  50% /usr
    /dev/mapper/VolGroup00-LogVol04
                          3.9G  379M  3.4G  11% /var
    /dev/mapper/VolGroup00-ORACLE_BASE
                           12G  8.7G  2.6G  78% /oracle
    10.10.28.140:/vol/px4cinconso
                           40G  1.4G   39G   4% /inconso_px
    /dev/mapper/36001ec9000d5ea810000061349015d98
                          1.3T  551G  665G  46% /rman
    [root@db02~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                          3.9G  887M  2.9G  24% /
    /dev/sda3             190M   34M  147M  19% /boot
    tmpfs                  16G     0   16G   0% /dev/shm
    /dev/mapper/VolGroup00-LogVol05
                          3.9G  137M  3.6G   4% /home
    /dev/mapper/VolGroup00-LogVol03
                          3.9G  261M  3.5G   7% /tmp
    /dev/mapper/VolGroup00-LogVol02
                          7.8G  3.7G  3.8G  50% /usr
    /dev/mapper/VolGroup00-LogVol04
                          3.9G  355M  3.4G  10% /var
    /dev/mapper/VolGroup00-ORACLE_BASE
                           12G  6.5G  4.8G  58% /oracle
    10.10.28.140:/vol/px4cinconso
                           40G  1.4G   39G   4% /inconso_px
    [oracle@db01~]$ rman target /
    Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: F1 (DBID=1245145263)
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/f1/fullbackup/%F';
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    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 ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default
    # Script for backup
    level0 ()
    run {
      allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
      allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
      backup incremental level 0 tag = weeklyfull database channel c1
      plus archivelog tag = ARCH_$TODAY delete all input channel c2;
      release channel c1;
      release channel c2;
    run {
      allocate channel c1 type disk;
      delete noprompt obsolete;
      release channel c1;
    }Bundle of thanks.
    Regards,
    Edited by: 910385 on Feb 24, 2012 3:00 AM

    Hi,
    THanks alot for your feedback. Makes my life easier :) . But actually I started studying this all subject because of the following error message in the log file. I found out about this error that doesn't seem to harm. Just wait for the job to finish or it will sort out automatically. Here are the lines from the log file.
    Fehler in Backuplogs gefunden:/oracle/log/fcp11-backup-2300.log: RMAN-00571:
    ===========================================================brRMAN-00569: ===============
    ERROR MESSAGE STACK FOLLOWS ===============brRMAN-00571:
    ===========================================================brRMAN-03009: failure of
    Control File and SPFILE Autobackup command on c1 channel at 02/08/2012
    06:10:41brORA-00230: operation disallowed: snapshot control file enqueue unavailableI studied few important lines from one of my book, Oracle 11g RMAN backup and recovery (Roberg G Freeman) that I am going to write after the following MAIN ISSUE:
    Node 1
    RMAN> show all;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_fp11.f'; # default
    Node 2
    RMAN> show all;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_fp12.f'; # default
    Thing which I just noticed regarding the above RMAN error is that snapcf_fp11.f can be seen on the Node 1 on todays date but snapcf_fp12.f was only on 10th jan.
    [oracle@db01dbs]$ ls -lrth
    -rw-r----- 1 oracle oinstall  20M Feb 27 15:10 snapcf_fcp11.f
    [oracle@db02dbs]$ ls -lrth
    -rw-r----- 1 oracle oinstall  20M Jan 10 13:28 snapcf_fcp12.fTHe few lines from the book which I mentioned above are: (Though you might not need to read those lines):
    "You need to move the snapshot control file to a shared location if you plan to run backups from more than one node. If you do not move the snapshot control file to a shared file system such as OCFS or an ASM disk group, then you must make sure that the local destination is identical on all nodes."
    My question is of course, how to sort out the above log file error. Becuse in our case, backups are run only from one node, and snaphost control file is not being moved to ASM disk groups. Local destination is also same on both the Nodes, isn't it (with different names). Why on Node 2 last snapshot was taken on 10th jan while on Node 1 it is todays date which seems fine.
    Control file and SPFILE which I noticed are stored on ASM disk groups also, so being shared between the two Nodes.
    (Sanme names/same location for control file and SPFILE on Node 1 and Node 2)
    Control file:
    +REDO1/fp1/controlfile/current.256.652803827
    +DATA1/fp1/controlfile/current.441.652869697
    SPFILE:
    +DATA1/fp1/spfilefcp1.oraPlease suggest.
    Thank you.
    Regards,
    Edited by: 910385 on Feb 27, 2012 7:43 AM

  • RMAN Backups with retention policy to redundancy 1 doesn't work fine.

    Hi experts,
    I have a Oracle database with the following system backups:
    Monday:       ArchiveLog Backup
    Tuesday:      Full Backup
    Wednesday:  ArchiveLog Backup
    Thursday:     ArchiveLog Backup
    Friday :         Full Backup
    Saturday:      ArchiveLog Backup
    Sunday:       ArchiveLog Backup
    ArchiveLog Backup = backup tag  'ARCHIVELOG_BACKUP' device type disk archivelog all not backed up delete all input;
    Full Backup = backup tag 'FULL_BACKUP'  device type disk database skip readonly  plus archivelog tag 'FULL_BACKUP_ARCHIVELOGS';
                         crosscheck backup;
                         crosscheck copy;
                         delete noprompt obsolete;    
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 8;
    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 ARCHIVELOG DELETION POLICY TO NONE; # default
    What this system has done until last two weeks? For example:
    Tuesday :     Full Backup
    Wednesday:  ArchiveLog Backup
    Thursday:     ArchiveLog Backup
    Friday :         Full Backup - > After that, Full backup from Tuesday and ArchiveLog backups from Wed, and Thurs, are deleted. (Thanks to Retention policy) .
    What this system do now?
    Tuesday :     Full Backup
    Wednesday:  ArchiveLog Backup
    Thursday:     ArchiveLog Backup
    Friday :         Full Backup - > After that, Full backup from Tuesday are deleted but not ArchiveLog backups from Wed, and Thurs.
    When I execute a crosscheck on RMAN return that all are AVAILABLE.
    My question is: What is right? The system backups before or after?
    Thanks for your help!

    You are confused about the purpose of crosscheck.
    There are two concepts for which you must grasp the distinction.
    - Expired
    - Obsolete
    Expired
    When an archive log is written, or rman makes a backup, a record of that archivelog or backupset is written to the repository in the control file.
    Crosscheck simply checks the existence of the archivelogs or backupsets that are recorded in the repository.  If something went missing (say, if you used an OS command to delete archivelogs), the record of the missing file is marked as 'expired'.  If you follow the crosscheck command with a 'delete expired' command, the repository records that have been marked 'expired' are deleted from the repository, so rman has no more memory of those files.  Note that 'expired' has nothing to do with retention policy.  Also note that if you do not actually issue the 'delete expired' command, the expired records will remain in the repository. 
    Obsolete
    The retention policy deals with when a backupset is obsolete, meaning it is no longer needed to protect the retention period.  Backupset are not marked as obsolete.  They are evaluated for obsolescence at the time of a command that needs it -- "report obsolete" or "delete obsolete", or when FRA maintenance requires an implied 'delete obsolete'.

  • Why are my RMAN backup files still around?

    Environment:
    Oracle 11.2.0.3 EE on Solaris 64-bit
    Good Morning (at least it's morning here at the moment),
    I have a test database that I currently have set up to do an Incremental Level 0 backup every morning at about 03:00.
    I also do an 'archivelog backup all' every 4 hours during the day.
    My archivelog deletion policy is 'backed up 2 times'.
    I have RMAN set up with a recovery window of 8 days (SHOW ALL - seen below).
    I have several RMAN files dated 11 days ago.
    Question: Why are these files still around?
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name APSMDMP2 are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 3;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 5 G;
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
    CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
    CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128';
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11203/db_1/dbs/snapcf_APSMDMP2.f';I do have several entries in V$ARCHIVED_LOG with a BACKUP_COUNT = 1 but they are all dated 21 days ago and have a DELETED status as seen here:
    SEQUENCE# ARC APPLIED   DEL S CTIME                         BACKUP_COUNT
          4625 YES NO        YES D 09-oct-2012 13:21:09                     1
          4626 YES NO        YES D 09-oct-2012 13:21:48                     1
          4627 YES NO        YES D 09-oct-2012 13:22:23                     1
          4628 YES NO        YES D 09-oct-2012 13:22:50                     1I am able to see the contents of the RMAN files but I don't see anything that would cause them not to be deleted during the RMAN runs. Here is an example of one of the files:
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    6493    Incr 0  22.75G     DISK        01:35:54     2012-10-19:04:36:13
            BP Key: 6493   Status: AVAILABLE  Compressed: YES  Tag: FULL_DAILY
            Piece Name: /rman/APSMDMP2/APSMDMP2_20121019_797050819_6508_1
      List of Datafiles in backup set 6493
      File LV Type Ckp SCN    Ckp Time            Name
      2    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/sysaux01.dbf
      4    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/users01.dbf
      5    0  Incr 564035766  2012-10-19:03:00:19 /u01/oradata/APSMDMP2/data_process_dt01_01.dbf
      9    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/gmx_src_dt01_01.dbf
      10   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/gmx_src_ix01_01.dbf
      12   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/adm_data_ix01_01.dbf
      13   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/patrol01_01.dbf
      16   0  Incr 564035766  2012-10-19:03:00:19 /u07/oradata/APSMDMP2/becosp_base_data_01.dbf
      18   0  Incr 564035766  2012-10-19:03:00:19 /u07/oradata/APSMDMP2/becosp_base_data_02.dbf
      27   0  Incr 564035766  2012-10-19:03:00:19 /u06/oradata/APSMDMP2/data_process_dt01_03.dbf
      30   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/adm_data_dt01_02.dbfI do use the 'DELETE NOPROMPT OBSOLETE' after each database and archivelog backup. Here is my Incremental Level 0 command file:
    backup incremental level 0 cumulative database tag 'full_db';
    backup archivelog all not backed up 2 times tag 'full_arch';
    DELETE NOPROMPT OBSOLETE;I know I can remove the files manually and resync everything with a CROSSCHECK but I was trying to figure out why it happened in the first place.
    Any suggestions are most welcome.
    Please let me know if more information is needed.
    Thanks very much!!
    -gary

    garywicke wrote:
    Michael,
    I read Ed's thread and I understand about the timing of the Full (Incr Lvl 0) and the incrementals.
    In my case I'm not doing any incrementals (Incr Lvl 1) of the database, just Incr Lvl 0 every day. I do the archivelog backups during the day to keep the /arch mount point under control.
    So, if I have Incremental Level 0 backups on the 19th, 20th, 21st, 22nd, ..... With an 8 day recovery window I shouldn't need the ones from the 19th or 20th at a minimum and possibly the 21st depending on when the math is done. Right?
    Am I missing something?
    *************** NEWS FLASH ******************
    Whoops!!! Egg on my face! I just checked back in my email logs of the backups and now recall there were some disk space issues around that time that caused the backups to fail and it just so happens that the backups on the 20th, 21st and 22nd all failed.
    I should learn to trust RMAN more. It is obviously smarter than me!! :-)
    Sorry for the red flags. I'll do my homework more completely next time.
    Not a problem. We've all been there, done that.
    I can't tell you how many times I've been stuck on something, run out of ideas on my own research and thrown a question to the forum, and no sooner to I hit the 'send' button that a light goes on and I quickly get my own answer.
    At least I understand the recovery window scenario better.
    Thanks very much for the help and I'll see you the next time.
    Have a great day!
    -gary

  • How to speed up rman backup?

    Hi,
    we are taking backup using rman. my database size is increasing.so rman backup time is increasing. so i want to spped up rman bakup performance. how to speed up rman bakup?
    Thnaks,

    My general request whenever you post the question in forum please start your question something like this:
    Oracle Version : <4 digit version> select * from v$version;
    OS Information with complete version and/or patch whatsoever.
    1. http://www.oracle-base.com/articles/10g/RMANEnhancements10g.php
    2. Re: RMAN Backup Script
    and read the reply of Adith
    You can also use set
    CONFIGURE BACKUP OPTIMIZATION ON
    Additionally review
    Restarting and Optimizing RMAN Backups
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmbackp007.htm#i1006318
    Best Regards
    Girish Sharma

Maybe you are looking for

  • How do I play a video and audio file at the same time on Apple Tv?

    I need to play a video loop (with no audio) on my apple tv and also play some music in the background. Its a video loop with no audio and then I need music to play in the background. The loop needs to repeat all day because its only 5 min long and th

  • Quicktime keeps Accosiating, though i disable it! Help!

    I am beginning to get rather angry at quicktime. It keeps accosiating with files i don't want it too! And it is really beginning to pi..ee me off! It has worked fine a long time ago. But since Itunes need quicktime to play, i really need this to work

  • I book G4 dead

    I left my i book G4 today downloading a tv show off i tunes... I come back 2 hrs later and its sleeping. I hit enter it sounds like its coming back on... Then i look no sleep light - blank screen... I try hitting the power button nothing happens... I

  • I can't start iTunes.

    When I try to open the application it says 'please insert a disk into removeable drive J'.  I have tried to download the latest version of itunes but cannot get it to work.  When I right click and go to 'troubleshoot compatability' it says 'the speci

  • How to install compat-drivers ?

    Ok guys, I am an arch user for a good while now (1 month, ehehe), but I am not even close to a tech savy for now. I wanted to try today the aircrack injection in arch. It works flawlessly in backtrack 5. Now ... I get an error something about mon0 ch