RMAN Retention policy 5 days but v$backup_set shows unexpected return
ORACLE 10.2
RMAN NOCATALOG
Windows Server 2003
Hi All,
Just trying to get to grips with RMAN.
I have the Retention policy set to 5 with Auto Backup Control File.
I use a scheduled task to take a full backup every night due to small size of database.
With a 'delete noprompt obsolete' after the backup to remove old backups.
When I query the v$backup_set I get a return from a backupset from over 10 days ago? (this does not exist in my backup location) other than that the return is as expected.
Can any one tell me why this is displaying and how to remove the invalid returns.
Best Regards and Happy Xmas
Neil
Message was edited by: removed para due to believe it was incorrect statement
So i beieve this is stored in the control file which has a default retention of 7 days (CONTROL_FILE_RECORD_KEEP_TIME)
Neil Hunter
Hi,
Slimmed down RMAN report shows me the following, Sorry struggling with layout...
BS Key Type LV Size Device Type Elapsed Time Completion Time
26 Full 6.80M DISK 00:00:00 14-DEC-07
28 Full 6.80M DISK 00:00:00 15-DEC-07
30 Full 6.86M DISK 00:00:00 16-DEC-07
32 Full 6.86M DISK 00:00:01 17-DEC-07
34 Full 6.86M DISK 00:00:01 18-DEC-07
I have dates when selecting from v$backup_set from the 7,12,13 Dec? as well as the above..... extract as below
COUNT B CON INCREMENTAL_LEVEL PIECES START_TIM COMPLETIO ELAPSED_SECONDS BLOCK_SIZE INP KEE KEEP_UNTI KEEP_OPTIO
1 640712259 640712258 2 D NO 1 07-DEC-07 07-DEC-07 1 8192 NO NO
2 640712260 640712259 3 D YES 1 07-DEC-07 07-DEC-07 1 16384 NO NO
3 640712625 640712625 4 D NO 1 07-DEC-07 07-DEC-07 0 8192 NO NO
4 640712626 640712626 5 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
5 640712648 640712648 6 D NO 1 07-DEC-07 07-DEC-07 0 8192 NO NO
6 640712649 640712649 7 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
7 640713224 640713223 8 D NO 1 07-DEC-07 07-DEC-07 1 8192 NO NO
8 640713225 640713225 9 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
9 640713657 640713282 10 D NO 1 07-DEC-07 07-DEC-07 375 8192 NO NO
10 640713668 640713667 11 D YES 1 07-DEC-07 07-DEC-07 1 16384 NO NO
This could have been when I was setting up RMAN and testing taking a backup? how do I delete or will they expire....
Reference you previous emails the KEEP fields are blank......
Regards
Neil
Message was edited by:
Neil Hunter
Message was edited by:
Neil Hunter
Similar Messages
-
Hi,
on 10g R2 on AIX6.1 , I have the followings :
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;My backup script :
RMAN> run
allocate channel t1 type disk;
backup as compressed backupset format '$dir/df_%d_%T_%s_%p' database;
sql 'alter system switch logfile';
backup as compressed backupset format '$dir/al_%d_%T_%s_%p' archivelog all delete input;
backup as compressed backupset format '$dir/ctl_%d_%T_%s_%p' current controlfile;
crosscheck backup;
delete noprompt obsolete;
delete noprompt expired backup of database;But I have the backup files of 3th of March yet :
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1 recid=171 stamp=744800219And the only file it deletes is :
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 13404 18-MAR-11
Backup Piece 13408 18-MAR-11 /appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1
deleted backup piece
backup piece handle=/appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1 recid=331 stamp=746072971
Deleted 1 objectsShould not RMAN delete the backup files of before 15 of March ? Why it does not ?
Thank for explanation ? Or more.Thank to all.
We backup it every night (FULL at WE and incremental in week).
list backup of database;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
7145 Full 571.86M DISK 00:01:55 03-MAR-11
BP Key: 7151 Status: AVAILABLE Compressed: YES Tag: TAG20110303T085658
Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1
List of Datafiles in backup set 7145
File LV Type Ckp SCN Ckp Time Name
1 Full 75445711 03-MAR-11 /data01/bases/MYDB/system01.dbf
2 Full 75445711 03-MAR-11 /data01/bases/MYDB/psundots01.dbf
4 Full 75445711 03-MAR-11 /data01/bases/MYDB/psdefault.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
19112 Full 772.42M DISK 00:03:05 01-APR-11
BP Key: 19118 Status: AVAILABLE Compressed: YES Tag: TAG20110401T121403
Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110401_60_1
List of Datafiles in backup set 19112
File LV Type Ckp SCN Ckp Time Name
8 Full 152751106 01-APR-11 /data01/bases/MYDB/ptprc.dbf
10 Full 152751106 01-APR-11 /index01/bases/MYDB/pttbl.dbf
15 Full 152751106 01-APR-11 /data01/bases/MYDB/pttlrg.dbf
19 Full 152751106 01-APR-11 /data01/bases/MYDB/ptprjwk.dbf
20 Full 152751106 01-APR-11 /data01/bases/MYDB/ptaudit.dbf
24 Full 152751106 01-APR-11 /data01/bases/MYDB/amlarge.dbf
26 Full 152751106 01-APR-11 /data01/bases/MYDB/apapp.dbf
27 Full 152751106 01-APR-11 /data01/bases/MYDB/aparch.dbf
34 Full 152751106 01-APR-11 /data01/bases/MYDB/aucapp.dbf
35 Full 152751106 01-APR-11 /data01/bases/MYDB/auclrge.dbf
37 Full 152751106 01-APR-11 /data01/bases/MYDB/bdapp.dbf
38 Full 152751106 01-APR-11 /data01/bases/MYDB/bdlarge.dbf
40 Full 152751106 01-APR-11 /data01/bases/MYDB/bilarge.dbf
42 Full 152751106 01-APR-11 /data01/bases/MYDB/caapp.dbf
50 Full 152751106 01-APR-11 /data01/bases/MYDB/cuaudit.dbf
54 Full 152751106 01-APR-11 /data01/bases/MYDB/cularge.dbf
58 Full 152751106 01-APR-11 /data01/bases/MYDB/dpwork.dbf
60 Full 152751106 01-APR-11 /data01/bases/MYDB/eobfapp.dbf
64 Full 152751106 01-APR-11 /data01/bases/MYDB/eocmwrk.dbf
71 Full 152751106 01-APR-11 /data01/bases/MYDB/eoecwrk.dbf
74 Full 152751106 01-APR-11 /data01/bases/MYDB/eoepapp.dbf
75 Full 152751106 01-APR-11 /data01/bases/MYDB/eoeplrg.dbf
77 Full 152751106 01-APR-11 /data01/bases/MYDB/eoewapp.dbf
81 Full 152751106 01-APR-11 /data01/bases/MYDB/eoiulrg.dbf
84 Full 152751106 01-APR-11 /data01/bases/MYDB/eoltapp.dbf
85 Full 152751106 01-APR-11 /data01/bases/MYDB/eoppapp.dbf
88 Full 152751106 01-APR-11 /data01/bases/MYDB/eotplrg.dbf
93 Full 152751106 01-APR-11 /data01/bases/MYDB/faapp.dbf
95 Full 152751106 01-APR-11 /data01/bases/MYDB/fawork.dbf
101 Full 152751106 01-APR-11 /data01/bases/MYDB/fgwork.dbf
107 Full 152751106 01-APR-11 /data01/bases/MYDB/fowork.dbf
109 Full 152751106 01-APR-11 /data01/bases/MYDB/fsapp1.dbf
112 Full 152751106 01-APR-11 /data01/bases/MYDB/glapp.dbf
122 Full 152751106 01-APR-11 /data01/bases/MYDB/inlarge.dbf -
RMAN Retention Policy - redundancy vs recovery window
Hi All,
I'm wondering what the most commonly used rman retention policy is, to provide point-in-time recovery. We have 2 oracle servers, one using redundancy policy (3) and the other using recovery window (2 days). I would like to standardize them but am not confident in which direction I should go in.
I'm tempted to lean towards redundancy but wanted to pose the question to a wider, experienced audience for any things to think about/watch out for. Also, I assume the restore process would the same for either.
Thanks in advance.Redundancy based retention policy means how many backups of each datafile must be retained and Recovery windows based retention policy is a period of time which starts with current time and goes backward in time upto the point of recoverability.
Oracle suggests and its Best practice is "Recovery Window" .( I don't know the reason though)
Two things you need to consider:
1) You might need more space in case of "recovery window" because it depends upon the schedule of the backup. In "redundancy" , your space consumption will be same.
2) You need to keep "recovery window" time less than the value of "control_file_Record_keep_time" so your backup records won't be overwritten in controlfile.
We use "Recovery Window" -
Query on RMAN Retention Policy
Hi, I have my Retention policy set to Redundancy 2
I have taken 3 backups so far ( 2 Backup Sets, 1 Image Copy )
When I check report obsolete I get the following
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 1 05-SEP-13
Backup Piece 1 05-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp
Backup Set 2 05-SEP-13
Backup Piece 2 05-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp
Backup Set 3 05-SEP-13
Backup Piece 3 05-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp
Backup Set 4 05-SEP-13
Backup Piece 4 05-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp
Backup Set 5 27-SEP-13
Backup Piece 5 27-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp
Backup Set 7 27-SEP-13
Backup Piece 7 27-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp
Archive Log 305 10-OCT-13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc
Archive Log 306 10-OCT-13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc
Archive Log 307 10-OCT-13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc
Archive Log 308 10-OCT-13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc
Backup Set pieces 1,2,3,4 basically equate to my oldest backup - hence under redundancy of 2, I can see why that is obsolete
5 and 7 were simply Control File/SPFILE backups from Auto Backup and the 2 newer backups of these have been taken since ( i.e. backupset pieces 9 and 10 )
Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
any advice appreciated,
JimQ. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
- Yes you can get the database to the date which ever you want , using recover database until time.
Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
- can you please provide the output of below command
RMAN> show all;
Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
- You can restore the database back to two days or 5 days based on your requirement. You nee to recover the database using until time option.
Thanks,
http://gssdba.wordpress.com -
Hi,
I have doubt on RMAN retention policy.
we are taking daily cumulative backup and weekly Full database backup.
And our retention policy is "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS"
My assumption is that RECOVERY window of 3 days will hold the backups of 3 days and delete the previous backups,since we are taking cumulative backups,and using them database can be recovered.
we used below commands to take cumulative backup.
backup incremental level 1 cumulative as COMPRESSED BACKUPSET tag '%TAG' database include current controlfile;
backup as COMPRESSED BACKUPSET tag '%TAG' archivelog all not backed up;
Regards,
mannuThanks for reply.
A recovery window is a period of time that begins with the current time and extends backward in time to the point of recoverability. The point of recoverability is the earliest time for a hypothetical point-in-time recovery, that is, the earliest point to which you can recover following a media failure. For example, if you implement a recovery window of one week, then this window of time must extend back exactly seven days from the present so that you can restore a backup and recover it to this point. You implement this retention policy as follows:
In our case:
Jan 24---Level 0 Full backup
Jan 25-Cumulative backup
Jan 26-Cumulative backup
Jan 27--->Cumulative backup
Jan-28 ----->cumulative backup
What would be my point of recoverability? How my recovery window period of 3 days work here.
Regards,
Mannu -
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 -
RMAN RETENTION POLICY configuration.
Currently I am doing RMAN backup once a day and save the copy to tapes through TSM. If I want to keep 15 copies of the db (NOT 15 same copies. It will be one copy from every day backup, so each copy will be different). How should I configure the RETENTION POLICY? Shall I do
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 15 DAYS;
Or shall I do
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
Also do I need to configure anything on the TSM side?
Thanks.To keep the last 15 full backups use redundancy 15.
You don't need to do anything on TSM if:
- you use RMAN to backup directly to tape device and
- you use RMAN DELETE OBSOLETE statements to purge old backups.
See http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV8400 -
The RECOVERY WINDOW and REDUNDANCY options of the RETENTION POLICY parameter are mutually exclusive. I have to set one or the other. However, if I set REDUNDANCY = 3 and then RECOVERY WINDOW = 21 DAYS, I've been told that the recovery window of 21 days will be enforced and RMAN will keep only 3 backup copies within this window period? Is this correct?
Can you specify a maximum number of backups to keep within a window period of N amount of days?You can not set them both. It is one or the other.
If you set recovery window = 21 days, then it will keep as many backups as necessary to restore back to 21 days.
If you set redundany=3, then it will only keep the most recent 3 backups. -
Rman Retention policy to recovery window
Hi,
I have few basic doubts in RMAN backup policy
1 . Is that possible to set Retention policy to recovery window in minutes??
2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
Regards,
0071) Syntax is .... TO RECOVERY WINDOW OF integer DAYS ... no other time statement.
2) Backups become obsolete when no longer needed to fulfil a retention policy. In a (theoretical) scenario, you perform a level 0 backup and then only incremental backups, the starting level 0 backup must be kept for ever (even if it WOULD be possible to define a recovery window in minutes).
Werner -
Appropriate RMAN Retention Policy
Hi All,
We have enabled ARCHIVELOG on a Production database, and the size allocated for the same is 4GB. There are situations when the archivelog size touches the maximum point, which results in no-connectivity to the database untill we delete old logs via RMAN.
At the moment, we have scheduled a task to delete archivelogs on a daily basis, but I agree, this is not an appropriate practice to follow.
I will really appreciate it, if someone can help me in defining a retention policy, or any other appropriate method, where we can handle this over-flow in a much better way.
Specs are as follows:
===========================================
OS: Windows Server 2003 Standard Edition
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0
===========================================
Thanks
Noman Amir JamilThats nice you are moving the archivelogs to antoher partition ,i presume you had
archivelogs at the same destination where database resides isnt?
neednt to schedule turn the retetnion policy which match to yours own policy ,you just have to include delete obsolete within yours backup scripts and as i laredy given you link that
"Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups. First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
log backups that are older than the oldest datafile or control file backup that must be retained."
run
backup database;
backup archivelog all;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
Please advise me, if my approach(logic) here is
appropriate, or is there any other way of doing this
more efficiently.it alls depend on yours SLA
i would rather suggest you move yours alls FRA area to another drive which is seperate from yours database residence.
Khurram -
RMAN retention policy really long
Hi,
we are planning to have an RMAN backup policy really long, around 7 years, with all the backup piece stored on a shared drive.
I would like to ask if there are problems or concern to have a recovery windows of around 2500 days, and if I have to change other Oracle parameter like control_file_record_keep_time.
The oracle version is 10.2.0.4, on a Solaris box, the customer don't want you a Catalog.
thanks for your time
NunzioI Nikolay,
thanks for you answer.
Nikolay Ivankin wrote:
Nunzio Cafarelli wrote:
What do you mean for huge!? and, in your experience, we should expect some hi decrease of performance, or are we speaking of something like 1%.I can't say - I don't know db size, user's activity, amount of redo information, backup strategy.
You are right, it's not easy to have an idea of what will happen.
Except that 2 points, there are no other functionality concerns!?Aren't enough? I would say, those 2 points are enough to refuse to keep rman info in CF, but catalog db.
Honestly no, if I will have a big (supposing 40 Mb) control file, and I'll have a performance decrease of around 1% or 2% is my opinion that that 2 points are not enough to refuse to proceed in this way.
I'll be scared if I know that ORACLE can't manage that amount of days as recovery window, and I'll have problem if I need to recover the database in a point in time that, for example, is more than 3 years ago.
Anyway, thanks.
Regards
Nunzio -
RMAN RETENTION POLICY FOR ORACLE8I
Dear all,
How to config RETENTION POLICY for oracle8i(CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;), same 9i ?
Thanks for advance !
CharaIn ORACLE 8i, there are NO stored RMAN parameters (I believe, 9i was the first version to add this feature).
Instead, in ORACLE 8i you had to specify all channel parameters, formats etc in a run block ... So, the good news is, in ORACLE 8i these parameters should be already "hardcoded" in the RMAN scripts ... in other words, nothing to transfer on a database level ... -
Firefox showed my pictures on my ebay auctions previously, but I noticed yesterday morning that while using Firefox, I had no pictures. Went to Internet Explorer & pictures show up fine. Help? Something is wrong. What & how do I fix it? I have emptied my cache. Turned the computer off & back on. Don't know what else to try.
Checkout this article, particularly the first step regarding site permissions.
[https://support.mozilla.com/en-US/kb/Images+or+animations+do+not+show Images or animations do not show]
Edit: If your eBay pictures are hosted on a different site, you would need to unblock that site. If that site is not blocked, then you may have blocked all "third party" images, i.e., images hosted on a different site. This article has more information about how to restore normal loading: [http://kb.mozillazine.org/Permissions.default.image permissions.default.image - MozillaZine Knowledge Base]. -
RMAN backups does not match its retention policy
Hello,
I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
I have clear retention policy and set to 14 days again but does not seem to work.
I would appreciate suggestion(s) regarding the strange issue.
Thanks a lot.
Best RegardsJohn-MK wrote:
Hello,
I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
I have clear retention policy and set to 14 days again but does not seem to work.
I would appreciate suggestion(s) regarding the strange issue.
Thanks a lot.
Best Regards
We would need to know what kind of backups and when they were taken. Consider this scenario:
retention policy of 7 days.
Incremental level 0 backup taken on Sundays
Incremental level 1 backups taken Mon through Sat.
Let's say Oct 1 is a Sunday, so we take an inc-0 backup on Oct 1, and again on Oct 8.
Now let's say we are at Oct 10. Our 7 day retention policy dicatates that we be able to recover to any day back to Oct 3.
The only way we can recover to Oct 3 is to begin with that inc-0 backup from Oct 1.
All recovery begins with the last inc-0 backup prior to the point in time to be recovered. In a normal, regularly cycling schedule of backups, you will actually end up with backups 1 day short of being twice as old as your retention period.
Let's take a more extreme example. Same 7-day retention period, but after a single inc-0 backup, you don't take any more backups for 3 months. That one single backup is still needed to enforce your recovery window, and so is not obsolete, despite the fact it is 3 months old and your recovery window is only 7 days.
Also, you mention 'expired'. In terms of oracle backups, 'expired' is not the same as 'obsolete'.
"Obsolete" means 'no longer needed to enforce recovery policy'.
"Expired" is a bit more complex.
when a backup is taken, or an archivelog is written, a record of that is written to the repository. when you do an rman 'crosscheck', those repository records are compared to reality -- to see if the recorded backup file or archivelog file actually exists. Maybe someone used an OS command to delete them. Any file found to have 'gone walkabout' have their repository records marked as 'expired'. An rman 'delete expired' then removes those records from the repository. -
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
Hi Guys
Can you please put some light on the 0 days. what is the meaning on 0 days and how does this work.
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS; If I take full backup every night how many backup will it contain and how will it obsolete the backup.
RMan 9i R2
Soalris 5.9
I understand the concept if recover window is 1 or more days but confuse with 0 days.
Thank you in advance.RECOVERY WINDOW OF 0 DAYS is effective like REDUNDANCY 1.
RMAN> configure retention policy to recovery window of 0 days;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=15 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 0 days
no obsolete backups found
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 0 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 10 09-SEP-07
Backup Piece 10 09-SEP-07 E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
RMAN> delete backup;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
10 10 1 1 AVAILABLE DISK E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
11 11 1 1 AVAILABLE DISK E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 recid=10 stamp=632859727
deleted backup piece
backup piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 recid=11 stamp=632859802
Deleted 2 objects
RMAN> configure retention policy to redundancy 1;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0EIRHB9H_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 12 09-SEP-07
Backup Piece 12 09-SEP-07 E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1
RMAN>
Maybe you are looking for
-
[BUG] Flash plug-in crash with large images, sometimes
Hello, I've been working with using Pixel Bender shaders in Flash and have encountered plugin / browser crashes when using shaders on large images, but only on certain machines. I've been unable to reproduce the crash on any machine I have physical a
-
XSLT - How to pass a Java object to the xslt file ?
Hi , I need help in , How to pass a java object to xslt file. I am using javax.xml.transform.Tranformer class to for the xsl tranformation. I need to pass a java object eg Class Employee { private String name; private int empId; public String getName
-
OSX 10.7, SSDs, TRIM, and so on...
Okay, so I have played with Windows 7 Home Premium on this wonderful little Booklet 3g for some time now. I hate it. I am a Mac guy, through and through, and this will never change. I have been running both Linux Mint 11 and Ubuntu 11.04 for the past
-
Brother HL-4070CDW will not set up to print on my network
It would appear that the printer drivers for Brother HL-4070CDW color laser are not installing. Either that, or the computer is failing to acknowledge they're there. I followed the instructions to install drivers from the Brother CD and then also ins
-
Printing in Classic via 10.4
Having problems printing from a Classic application while running under 10.4.11. I have a new Samsung ML2850 Laser that prints fine with applications under 10.4, but when I try to print from old OS 9 apps I get an error message: <This printer cannot