Backup Optimization vs redundancy of 3.

backup optimization
A configuration enabling RMAN to automatically skip backups of files that it has already backed up. You enable and disable backup optimization with theCONFIGURE command.
Redundancy is set to 3.
So , day one i have the following backup plus archive log
Backup 1
All DB File
Arc_1
Arc_2
Second day
Backup 2
All DB File
Arc_3
Arc_4
Third day
Backup 3
All DB File
Arc_5
Arc_6
Fourth day
Backup 4
All DB File
Arc_7
Arc_8
If I only had the last backup but was asked to restore to the to a point in time of yesterday, would my redundancy 3 not mean that everything from backup 3 be on my backup 4 ?
I believe that only the files added since backup 3 completed is on backup 4.

Thank you.
What you say makes sense. As my one friend said to me , if you planning on being able to restore backup 3's archvied files and you dont have your backup duplexed, then you cannot restore backup 3 archived files. So, if optimization is turned on, duplex to 2 tapes.
Weighin in on the likelyhood of the situation.
Ron

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.

"Backup optimization on" is not working for "backup database"

Hi,
I am using a windows environment and my database info is like this:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Productionnow, I change my configuration for backup optimization on and then make example tablespace offline and also make example datafile offline. After that I run 2 times "Backup Database" command but 2 backup has same size and have example tablespace too... Backup archivelog all is working bur backup database is not!
according to this link it must not backup example datafile for second: http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV113
is there something that I missed ?
rman configuration:
CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'HIGH' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\APP\ABC\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFORCL.ORA'; # default

If you enable backup optimization, then the BACKUP command skips backing up files when the identical file has already been backed up to the specified device type.
1. In case of datafile RMAN compares the DBID, checkpoint SCN, creation SCN, and RESETLOGS SCN and time as a datafile already in a backup. If they are identical then skip to take backup again.
2. In case of archived redo log RMAN compares thread, sequence number, and RESETLOGS SCN and time.
3. In case of backupset RMAN compares recid and stamp.
Backup optimization applies to only commands,
-BACKUP DATABASE
-BACKUP ARCHIVELOG with ALL or LIKE options
-BACKUP BACKUPSET ALL
refer,
http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14191/rcmconc1008.htm
Thanks

Backup Optimization

backup optimization is on ; i execute the following commands twice, and backup happens second time also with a seperate piece, why ? i did not even make any changes, oracle says for a datafile to be identical The data file must have the same DBID, checkpoint SCN, creation SCN, and RESETLOGS SCN and time as a data file in a backup. The data file must be
offline-normal, read-only, or closed normally. My file is already offline with alter tablespace users offline option. I also know that RMAN uses backup optimization when the following conditions are true:
# The CONFIGURE BACKUP OPTIMIZATION ON command has been run to enable backup optimization.
# You run BACKUP DATABASE, BACKUP ARCHIVELOG with ALL or LIKE options, or BACKUP BACKUPSET ALL, BACKUP RECOVERY AREA, BACKUP RECOVERY FILES, or BACKUP DATAFILECOPY.
even if i say backup database, oracle still backs it up 2 times, datafile 4... why ?????
backup format '/u01/back/%U' datafile 4;
backup format '/u01/back/%U' datafile 4;
Edited by: 842638 on 29-Jul-2012 08:28

in addition, if you command RMAN to backup datafile or tablespace exactly, RMAN definitely will back it up. if you run "BACUP DATABASE" command, then you will see that "skipping datafile X" line during backup. (my previos message is still valid, REDUNDANCY condition must be provided)
a specific TABLESPACE or DATAFILE backup command (Backup datafile X or Backup Tablespace Y) wil take backup every time.
Edited by: Mustafa Kalaycı on Jul 29, 2012 8:41 AM

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

CONFIGURE BACKUP OPTIMIZATION ON;

CONFIGURE BACKUP OPTIMIZATION ON;
above cmd only working on "sbt" type device or it is working also "disk".
plz. let me know. sir.
thanx in advance.

From the docs:
Requirements for Backup Optimization
Backup optimization is used when the following conditions are true:
The CONFIGURE BACKUP OPTIMIZATION ON command has been run to enable backup optimization.
You run BACKUP DATABASE, BACKUP ARCHIVELOG with ALL or LIKE options, or BACKUP BACKUPSET ALL.
Only one type of channel is allocated, that is, you do not mix channels of type DISK and sbt in the same backup command.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1008.htm#i1008304

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

Ability to "task schedule" via small utilities backup/optimize

Include small utilites with Lightroom that can be used with the system "task scheduler" that will perform catalogue backup and optimize on a user defined schedule.

(Replying to myself here no edit option) Is there a way to optimize the catalog via single command line or in a bat file with sqlite3.exe and/or Contig.exe?

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

RMAN: Backups not exipring after redundancy window.

Hello,
I run backup into sbt_tape and use the below block:
run{
ALLOCATE CHANNEL C1 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C2 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C3 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C4 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
backup incremental level 0 database filesperset=1 format '%d_L0_DF%f_%T_%u.dbf' tag 'DB_L0_DF_#_DT_UNQNO';
backup current controlfile format '%d_L0_CF_%T_%u.ctl' tag 'DB_L0_CF_DT_UNQNO';
backup incremental level 0 archivelog all filesperset=1 format '%d_L0_AL_%h_%e_%T_%u.arc' tag 'DB_L0_ARC#_DT_UNQNO';
crosscheck backup of database;
crosscheck backup of archivelog all;
delete noprompt expired backup of database;
delete noprompt expired backup of archivelog all;
My backups run perfectly, but for some reason my backups don't expire even though my redudancy is set to 7 days.
In my backup dest, I have backups as old as March '13, which should have been expired long time back.
Any ideas what might be wrong?
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name IWTPR are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so, ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
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 NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/IWTPR/snapcf_IWTPR.f';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/iwtpr/snapcf_iwtpr.f';
Thanks in advance,
aBBy.
Env details: 4-Node RAC cluster running 11.2.0.3.4 GI/RDBMS on RHEL 5.6

AB007 wrote:
Hello,
I run backup into sbt_tape and use the below block:
run{
ALLOCATE CHANNEL C1 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C2 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C3 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C4 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
backup incremental level 0 database filesperset=1 format '%d_L0_DF%f_%T_%u.dbf' tag 'DB_L0_DF_#_DT_UNQNO';
backup current controlfile format '%d_L0_CF_%T_%u.ctl' tag 'DB_L0_CF_DT_UNQNO';
backup incremental level 0 archivelog all filesperset=1 format '%d_L0_AL_%h_%e_%T_%u.arc' tag 'DB_L0_ARC#_DT_UNQNO';
crosscheck backup of database;
crosscheck backup of archivelog all;
delete noprompt expired backup of database;
delete noprompt expired backup of archivelog all;
My backups run perfectly, but for some reason my backups don't expire even though my redudancy is set to 7 days.
In my backup dest, I have backups as old as March '13, which should have been expired long time back.
Any ideas what might be wrong?
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name IWTPR are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so, ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
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 NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/IWTPR/snapcf_IWTPR.f';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/iwtpr/snapcf_iwtpr.f';
Thanks in advance,
aBBy.
Env details: 4-Node RAC cluster running 11.2.0.3.4 GI/RDBMS on RHEL 5.6
You are confusing 'expired' with 'obsolete'.
When a backupset is created, a record of that is placed in the control file.
If you perform a 'crosscheck backup', rman checks those records against reaility. If any backup is found to have gone missing, it's record is marked as 'expired'. Follow that up with a 'delete expired backup', and the records of the missing (expired) backups will be removed from the repository.
What you want is 'delete obsolete'. That will delete any backup that is no longer needed to enforce the retention period.
BTW, 'redundancy' and 'x days' are mutually exclusive.

RMAN retention policy - backup spfile and then redundancy = 5 removes it.

I have a database that is Oracle Standard Edition and it is version 9.2.0.6.
The spfile has not changed since November, 2005. A list backup does not show an spfile backup with a tag of "hot_database_spfile_backup_full". I took a close look at the RMAN script log and was shocked to discover that the spfile backup from the current day is being deleted. Is that because of the redundancy = 5? I'm trying to figure out why a backup piece from the current day is being deleted?
Examples follow.
The script deletes obsolete with redundancy = 5, however, I believe the intent was to keep 25 days because one of the configure clauses is set to a recovery window of 25 days. I realize that the redundancy overrides the configure retention policy command. I can fix the script and remove the redundancy = 5.
In the RMAN run statement, I first resync the catalog, backup the spfile, a full backup of the database including current controlfile plus archive log (delete input), resync catalog, switch logfile, and backup any additional archive logs. The backup looks fine.
Then, I allocate a channel for maintenance type sbt. The script then has a "delete noprompt expired backup;" a "delete noprompt obsolete redundancy = 5;" and finally, a crosscheck;
example of backup piece that is later deleted:
Starting backup at 07/18/2006 20:00:14
channel t1: starting full datafile backupset
channel t1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel t1: starting piece 1 at 07/18/2006 20:00:14
channel t1: finished piece 1 at 07/18/2006 20:00:15
piece handle=P*****_2338_1_596145614_FULL comment=API Version 2.0,MMS Version 5.2.0.0
channel t1: backup set complete, elapsed time: 00:00:01
Finished backup at 07/18/2006 20:00:15
deletion:
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
<other lines deleted>
Backup Set 27453 07/18/2006 20:00:14
Backup Piece 27454 07/18/2006 20:00:14
P*****_2338_1_596145614_FULL
deleted backup piece
backup piece handle=P*****_2338_1_596145614_FULL recid=2039 stamp=596145614
Deleted 12 objects
Why is a backup piece created on 7/18 being deleted in the maintenance step?
Thanks in advance!

In the next step in the script, the controlfile and spfile are backed up:
backup
full
skip inaccessible
tag hot_database_backup_full
format '%d_%s_%p_%t_FULL'
(Database
include current controlfile)
Plus Archivelog delete input;
Even though my backup script is redundant by backing up the spfile twice, when I list the backup of the spfile, I would have expected to find 5 backups with a tag of hot_database_spfile_backup_full and 5 with a tag of hot_database_backup_full. That is not the case. I only find spfiles with a tag of hot_database_backup_full. i am still perplexed by RMAN.
I will modify my script - remove the backup of the spfile, and crosscheck before the delete commands. I will also remove the redundancy = 5. The intent is to keep 25 days of backups.
Thanks for your comments

Backup and Redundancy Oracle 11g

Hi,
1. If we set the redundancy to 2, does it mean 2 level 0 backups taken at 2 different points in time one after another or does it mean 2 copies of the same level0 backup?
2. What is the effect of redundancy 2 on incremental backups? Are they also going to be 2 copies?
Thanks & Regards,

Vijay.Cherukuri wrote:
Hi,
Have you read the above link ?
Assume a different case in which REDUNDANCY is 1. You run a level 0 database backup at noon Monday,
a level 1 cumulative backup at noon on Tuesday and Wednesday, and a level 0 backup at noon on Thursday.
Immediately after each daily backup you run a DELETE OBSOLETE. The Wednesday DELETE command does not remove
the Tuesday level 1 backup because this backup is not redundant: the Tuesday level 1 backup could be used to recover
the Monday level 0 backup to a time between noon on Tuesday and noon on Wednesday. However,
the DELETE command on Thursday removes the previous level 0 and level 1 backups.
Also please see : http://web.njit.edu/info/oracle/DOC/backup.102/b14191/rcmconc1007.htm
As far i know RMAN does not delete backups if they are needed for recovery although they are obsolete (crossed retention policy )Not until you issue DELETE OBSOLETE.
Please note that backups are not marked obsolete. They are evaluated for obsolescence when a command that references obsolescence (DELETE ... or REPORT ...) is issued. You can change your retention policy all you want, but until you actually DELETE OBSOLETE, nothing happens to those backups. Then they will be deleted (or not) as per the retention policy that is in effect at the time of the DELETE OBSOLETE command.
That said, it is my understanding that if you keep your backups in the FRA, oracle will automatically delete obsolete backups if needed to free up space for newer backups. I've not personally investigated this so could be wrong. If this is the case, I would imaging that oracle still would not be deleting a backup as soon as it becomes obsolete, as that would require constant re-evaluation, but rather when it determines that it needs to find some space for a new backup.

Unable to restore and recover my Database from RMAN Backup

Dear All,
Iam practicing RMAN in Windows environment.
My configurations are
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
then i tried to startup the DB but it is saying
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
So i tried to restore the Database with my rman backup
RMAN> restore database;
But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
So, i am unable to recover my DB
Please tell me whether i am doing any mistake, what is the solution for my problem.
Thanks in advance
Mahi

All you restored was your datafiles.
Now issue recover database and that will apply the archive logs.
This is in the oracle documentation.
"You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
In this case after issuing restore database in RMAN, then issue this.
"Recover database"
It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;"

Backup Optimization vs redundancy of 3.

Similar Messages

Maybe you are looking for