RMAN Recovery Window 7 days setting - shows no obsolete backups

Hi All. Quick question about RMAN retention policy....
I have the current backup strategy:
Full backup (0) -> Sunday
Incremental backup (1) -> Monday - Saturday
Archive log backups -> every hour
This is a new database I just started taking backups on last month. (1st full backup was run October 4th)
I currently have not deleted any of them.
The old RMAN RETENTION POLICY was set to REDUNDANCY = 1
REPORT OBSOLETE lists all of them up to the last full which ran this past Sunday (Nov 1st)
I just switched the RMAN RETENTION POLICY to RECOVERY WINDOW of 7 DAYS
REPORT OBSOLETE lists no backups obsolete...
Shouldn't I see all the backups prior to a week ago or does it only take affect for backups run under the new policy?
Any help/replies are apprecitaed.
Thanks

Ran crosscheck with no problems:
Crosschecked 200 objects
But still same results for:
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
no obsolete backups found
Am I missing something here? Or like I mentioned is this expected behaviour because all of my other backups were run with REDUNDANCY = 1 retention policy?
Thanks

Similar Messages

RMAN Recovery window and Redundancy

Hi,
I am using Oracle 11g (11.2.0.1) in windows 2003 server. In RMAN is it possible to set both the below mentioned configuration in effect or anyone of the configuration can only be used?
RMAN>CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
Regards,
007

No it is not possible.
007 wrote:
hi oradb,
Thanks for your reply. i want both the RMAN configuration policy to be applied. Is the possible???
regards,
007hi oradb,
Thanks for your reply. i want both the RMAN configuration policy to be applied. Is the possible???
regards,
007

How can i set password for a backup?

::I am using 10g xe
I am gettin gbackup through RMAN, how can i set password for each backup? I want to protect my backup so that no one other could use it if he copies the backup files.
Faheem

Just use "SET ENCRYPTION ON IDENTIFIED BY password ONLY" command in your RMAN scripts. Look at the advanced backup manual for details: http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmbackp006.htm#sthref632
Daniel

Not set configure retention policy to recovery window of 7 days

HI all,
if parameter "" configure retention policy to recovery window of 7 days "" is not set
then i am taking weekly and inreamental cumulative backup any effect of backup
i think in this case delete obsolete is not working.
currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

HI all,
if parameter "" configure retention policy to recovery window of 7 days "" is not set
then i am taking weekly and inreamental cumulative backup any effect of backup
i think in this case delete obsolete is not working.
currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

Difference between redundancy & recovery window, rman

Hi All,
i want to know the difference between following two commands i.e.
1. configure retention policy to redundancy 1;
2. configure retention policy to recovery window of 1 days;
we are taking rman based FULL backup every night, so just want to keep one day old backup, would like to know which one of the above is more appropriate.
Regards,

Nayyares,
You should read this section of the docs,
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1008093
Redundanc is nothing but the number of copies. So you decide that you want to keep all the time , 3 copies of the backup of your db, you are going to use this. This serves the purpose that you can use this backup for whatever period of time in the past. Any copies before than these mentioned copies, will be marked obsolete by oracle. So if the number is 2 and , for example, you took first backups with tags A, B. Now when you will take the next backup with TAG C , A will be marked as obsolete. The most recent number of copies are kept irrespective of the time.
Recovery window is that for how long , you want to go back in the past and be assured that the backup you have is sufficient for the recovery of db. This puts no limitations on the number of copies as like the Redundancy setting. So depending on your SLA, you may use the window timings.
Both the settings are mutually exclusive so you don't have the liberty to go for both of them. As per your requirement, recovery window should work.
As Sybrand mentioned, this all what I wrote is already in the docs(link mentioned by me above) so take some time and read it. Also, I would like to point you to this presentation which should make use of RMAN more clear.
http://blogs.oracle.com/alejandroVargas/gems/RmanHandsOn.pdf
HTH
Aman....

Backup with retention policy to recovery window of N days

Hello,
I've issued command to create database incremental backup with configuration:
run
configure retention policy to recovery window of 14 days;
backup incremental level 1 cumulative
tag daily_incr_14_days
database
plus archivelog delete all input;
All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
BR
Patrycjusz.

TenakaKhan wrote:
Mahir,
thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
Yes it is.
Maintaining RMAN Backups and Repository&nbsp;Records
keepOption
backup retention policy
A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
recovery window
A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
Regards
Mahir M. Quluzade

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,
007

1) 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

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>

Retention policy to recovery window of 31 days means

HI all,
according to our company policy we need to restore database from last 7year.
backup happen on SBT TAPE.. we freez that tape for next 7 year.
my doubt is we are taking backup using recovery catalog...daily basis we are taking backup using recovery catalog...but i have one doubt while configuring we have configure retention policy of recovery window 31 days..
i m very much confused about this policy ..if we use this policy then can we able to recover database before 7 year or not..
becacuse we are not firing any delete obsulate backup command on recovery catalog.
we are only deleting archivelog by using delete nopromt archive log sysdate-3..
so please suggest does it possible if renrtion policy to recovery window 31 days...i can able to restore this database before 31 days.
Thanks,

Hi there user12009184
If you do not delete old backups through your rman script, then old backups will have to be deleted through your tape backup software. Unless you have endlessly large tapes ;-)
So, yes you could theoretically restore from backups older than your retention window of 31 days.
You should ensure that your control_file_record_keep_time is set to a value of 31 or larger (set it to your retention window period plus 1). Otherwise your control files will now know about your older backups.
If you want to restore a very old backup, than you will need to restore a spfile and a control file first, then restore, then recover your database.
You really, really need to test this. So that you know exactly how to do it and you have it documented.
hope this helped,
Andrew

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"

Recovery Point Status Report Shows Only One Day

Hello. Our Recovery Point Status Report showed us the last five days until about a month ago and now it only shows us one day. Just happened over a week-end when there was nothing changed on the server. We appear to have recovery points that go back
a week and the recovery point status is set to a month. We are running System Center 2012 R2 DPM.
Any help is appreciated, thank you for your time.
g

Hi,
Check your status report granularity settings for each protection group and make sure it's set for 1 day instead of weekly.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

Hello,
i am working for a scenerio and you can see my restore script below,
RMAN> RUN
2> {
3> SET UNTIL TIME "to_date('24-05-2010 18:00:00','DD-MM-YYYY HH24:MI:SS')";
4> RESTORE DATABASE;
5> RECOVER DATABASE;
6> }
executing command: SET until clause
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 05/26/2010 11:23:24
RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
also you can see my backups,
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
89 B 1 A DISK 24-05-2010 15:36:04 1 1 NO BACKU
P_BISE1DB_000_052410030823
90 B 1 A DISK 24-05-2010 15:36:13 1 1 NO BACKU
P_BISE1DB_000_052410030823
91 B 0 A DISK 25-05-2010 12:01:09 1 1 NO TAG20
100525T113815
92 B 0 A DISK 25-05-2010 12:01:13 1 1 NO TAG20
100525T113815
93 B 1 A DISK 25-05-2010 12:01:55 1 1 NO TAG20
100525T120152
94 B 1 A DISK 25-05-2010 12:04:55 1 1 NO TAG20
100525T120451
95 B 1 A DISK 25-05-2010 13:55:00 1 1 NO TAG20
100525T134431
96 B 1 A DISK 25-05-2010 13:55:09 1 1 NO TAG20
100525T134431
97 B 1 A DISK 25-05-2010 14:01:43 1 1 NO TAG20
100525T140139
98 B 1 A DISK 25-05-2010 14:55:33 1 1 NO TAG20
100525T140356
so i am trying to understand that what is the earliest date that i can restore my database and avoid tihs error, according to the my backup sets?
thank you
Ugur

Please query the following query and specify the RESETLOGS time
SELECT RESETLOGS_TIME FROM v$database;
i cant have result with this, because database is mount state,
And post the result of the following command to provide an information about database incarnations:
RMAN>LIST INCARNATION
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 BISE1DB 4092555014 PARENT 1116016 01-05-2007 16:22:55
2 2 BISE1DB 4092555014 PARENT 1226717 14-12-2007 15:28:11
3 3 BISE1DB 4092555014 PARENT 5783997202 04-05-2010 09:59:11
4 4 BISE1DB 4092555014 CURRENT 5785721070 26-05-2010 10:59:32
thank you

Time Machine wants 16 days to do an initial backup. ps shows PRI = 33 with NI = 0.   But I can not get sudo renice to set PRI less than 15. And renice sets NI directly with strange behavior for PRI. Any suggestions?

Time Machine said it would take 16 days to do an initial backup, and indeed, after many days it is less than a quarter done.   (The problem started when I put in a new bank disk for Time Machine to write to for its backup file.)
Activity Monitor shows that the process name is   backups   with Process ID   6060.
Then putting this PID in Terminal UNIX command ps gave:
EdsMacPro-1:~ ed$ ps -l -p 6060
UID   PID PPID        F CPU PRI NI       SZ    RSS ...
    0 6060     1 1004004   0 33 0 2556488 29040 ...
Wow! A priority of 33!
Don't know how that happened, but the way to fix that (I thought) is with renice.
But renice doesn't work.
After a lot of playing with renice and ps, it looks as though renice can not make the priority better than (no less than) 15.
And the parameter you put in, that according to the man page that is supposed to be priority, turns out to be "nice index", with priority changed by sometimes subtracting or sometimes adding either this number or twice this number - down to a limit of priority no less than 15.
EdsMacPro-1:~ ed$ ps -l -p 6060
UID   PID PPID        F CPU PRI NI       SZ    RSS ...
    0 6060     1 1004004   0 33 0 2556488 29040 ...
EdsMacPro-1:~ ed$ sudo renice 5 -p 6060
EdsMacPro-1:~ ed$ ps -l -p 6060
UID   PID PPID        F CPU PRI NI       SZ    RSS ...
    0 6060     1 1004004   0 28 5 2555964 29028 ...
EdsMacPro-1:~ ed$ sudo renice -5 -p 6060
EdsMacPro-1:~ ed$ ps -l -p 6060
UID   PID PPID        F CPU PRI NI       SZ    RSS ...
    0 6060     1 1004004   0 38 -5 2555964 29028 ...
EdsMacPro-1:~ ed$ sudo renice -15 -p 6060
EdsMacPro-1:~ ed$ ps -l -p 6060
UID   PID PPID        F CPU PRI NI       SZ    RSS ...
    0 6060     1 1004004   0 48 -15 2555964 29028 ...
EdsMacPro-1:~ ed$ ps -l -p 6060
UID   PID PPID        F CPU PRI NI       SZ    RSS ...
    0 6060     1 1004004   0 48 -15 2555964 29028 ...
EdsMacPro-1:~ ed$ sudo renice -n -5 -p 6060
EdsMacPro-1:~ ed$ ps -l -p 6060
UID   PID PPID        F CPU PRI NI       SZ    RSS ...
    0 6060     1 1004004   0 53 -20 2555964 29028 ...
EdsMacPro-1:~ ed$
This is with OSX 10.7.5 and Terminal 2.2.3 on an early 2009 Mac Pro with lots of memory.
What am I dong wrong, and any suggestions for how to fix my Time Machine process?

The backup file size is 1.67 TB.*
That's across the internal bus of a 2009 quad-core Mac Pro - which is pretty fast.
Copying an hour's worth of MPEG-2 HD takes about a minute.
I do a fresh backup from scratch about once a year, and the last time it finished over night.
This time the first Time Machine backup is only about 1/5 complete after many days, and Activity Monitor shows essentially no use of disk drives or of CPU. And in the first note I pointed out what is gleaned by using Terminal to execute the UNIX ps command. The priority of the running Time Machine process looks incorrect to me.
I could be wrong, but I think the problem is process priority, not file size.
I am unable to set priority to 0 or a negative number. Can someone straighten me out on how to do that?
[*The machine has four 1.5 TB disk drives in it plus lots of memory. Two of the physical drives are configured as one 3 TB backup drive (RAID concatanated).]

HT1369 During the updation of 10.7 version of Itunes on my iphone 4s, my phone has gone into recovery mode & is not showing up in i Tunes nor in my computer (windows xp). What shall i do so that my phone gets connected & running??

During the updation of 10.7 version of Itunes on my iphone 4s, my phone has gone into recovery mode & is not showing up in i Tunes nor in my computer (windows xp). What shall i do so that my phone gets connected & running??

Your iPhone is in recoverty mode at the moment so to possibly get it back up and running you would need to do a restore as you have been trying. Follow the steps in the article below for the specific error messages you have been receiving. If after following all steps the issue remains book an appointment at a local Apple Retail Store to have the iPhone evaluated.
Resolve specific iTunes update and restore errors

Mailbox windows re-set themselves, no message shows

Suddenly my Mail program's Inbox/Sender windows, which always showed Senders and their addresses above and then, when I selected a mail, displayed the message below-- with the Address panel still above, shows only a long list of every email I've ever gotten in my Inbox (or whatever mailbox I go to). No message is displayed below. I can only get a message to display by actually clicking to open it.
Perhaps I clicked something by mistake-- like the lower lefthand message window size thingie. But I want it back the way it was, with sender addresses on top and the selected message displayed below. However, I can't find anything to shrink the address panel above and bring back the message panel below. I've tried the Help section, but I think my question must be too stupid for it. I've tried clicking under "Window" and "View", too, but nothing in the pulldown menus seem right. HELP!

Let me help you with that, NannyMoo. Is the icon that you are seeing can be found here: What do the icons on my phone mean? If not, can you send a screenshot for us to further check this? To do that, see: http://www.microsoft.com/en-us/mobile/support/faq/?action=singleTopic&topic=FA140373. The link will work regardless of your location.
BTW, you can add as many accounts as you'd like. Just a gentle reminder, you'll want to pay extra attention to which Microsoft email account you set up first. We will wait for your reply.

RMAN Recovery Window 7 days setting - shows no obsolete backups

Similar Messages

Maybe you are looking for