Restore db outside of Recovery Window

Hello,
I'm still familiarizing myself with rman and don't have the luxury of a db environment to restore to.
Say my retention policy is 7 days and have deleted all obsolete backups. If I have a copy of a db 10 days ago and I want to restore it, how do I go about it in rman? The metadata in the control file would think this backup is no longer available right?
Many thanks!
Giovanni

You can restore the controlfile from that backup first and then use it for the recovery. Since you want to recover the database to a past point in time (i.e. as of 10 days ago), you are not doing a COMPLETE Recovery but an INCOMPLETE Recovery.
Hemant K Chitale

Similar Messages

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 window retention policy deletes archive logs before a backup?

Hi All,
Oracle 11G on Windows 2008 R2
This afternoon, I changed my RMAN retention policy from 'RETENTION POLICY REDUNDANCY 3' to RETENTION POLICY RECOVERY WINDOW OF 3 DAYS'
However, i checked tonight and after my daily backup ran, all the archive logs prior to the backup had been deleted! Thus meaning i dont think i can restore to any point in time, prior to my daily backup. All the .arc logs were there after the backup. So i tried another test and kicked off the daily backup again. During the backup process, the archive logs got deleted again! Now i don't have any archive logs..
Is this proper behaviour of RETENTION POLICY RECOVERY WINDOW?? I thought it would keep all the files needed for me to restore to any point in time for the previous 3 days. When i used REDUNDANCY, with my daily backups, it kept 3 days worth of backups+ archive logs so i could restore point-in-time to any point. How can i use RECOVERY WINDOW so that i can actually restore to any point-in-time for the 3 days??
I wanted to change to RECOVERY WINDOW since i read that by using REDUNDANCY it only keeps X copies of a backup (so if i ran the backup 3 times in a day, i would only have those 3).
Thanks in advance.

Hi All,
Here is the SHOW ALL output:
RMAN> show all;
RMAN configuration parameters for database with db_unique_name MMSPRD7 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
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 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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA
D TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\DATABASE\ORA11G\DATABASE\SNCFM
MSPRD7.ORA'; # default
Here is the RMAN script:
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Jan 20 23:03:12 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: XXX (DBID=)
RMAN> CROSSCHECK ARCHIVELOG ALL;
2> CROSSCHECK BACKUPSET;
3> CROSSCHECK BACKUP;
4> CROSSCHECK COPY;
5> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
6> DELETE NOPROMPT EXPIRED BACKUPSET;
7> DELETE NOPROMPT OBSOLETE;
8> BACKUP CURRENT CONTROLFILE;
9> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT;
Also, not sure if you needed the whole RMAN output, but here is the deletion part:
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           1392   15-JAN-14
Backup Piece       1392   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP
Backup Set           1393   15-JAN-14
Backup Piece       1393   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP
Backup Set           1397   16-JAN-14
Backup Piece       1397   16-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP
Backup Set           1400   17-JAN-14
Backup Piece       1400   17-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP RECID=1392 STAMP=836938856
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP RECID=1393 STAMP=836940124
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP RECID=1397 STAMP=837025228
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP RECID=1400 STAMP=837111700
Deleted 4 objects

What's the difference between redundancy and recovery window for retention?

Hello all,
I'm still trying to get a grip on this concept for RMAN backup planning.
I recently ran into a situation as follows.
I have the backups set to a redundancy of 1.
I have instance1, which had GRID jobs to run RMAN backups as follows
Incremental database level=0 weekly at Wed at 2:30am
I have daily backups, incremental level=1 each evening
I have archive log backups through the day.
What happened, was that apparently on a Tues some time, the development team deleted data from almost every table in their schema.
The didn't discover this till midday or so on Wednesday.
I went to try to restore...and RMAN couldn't do it. I had found a SCN for early the Tues they did it...but I got the following error:
RMAN> RUN
2> {
3> SET UNTIL SCN 4590383198282;
4> RESTORE DATABASE;
5> RECOVER DATABASE;
6> }
executing command: SET until clause
Starting restore at 28-APR-10
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=639 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: NMO v4.5.0.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=638 device type=DISK
creating datafile file number=1 name=+DATADG/instance1/datafile/system.284.697137287
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 04/28/2010 15:53:00
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DATADG/instance1/datafile/system.284.697137287'
From what research I did...it appears that since I did not have a level=0 incremental from before, it could not reset the database back in time. The previous one had been deleted since, I guess I had a redundancy of 1.
So, I thought I had a week backup they way I have it set..but that assumes that errors are found pretty quickly before the next level=0 backup.
I want at least 1 to 1.5 weeks worth of backups. I do have the problem that we do not have many tapes in rotation, so I cannot go for too long...may 2x weeks tops.
I'm trying to rethink my strategy, but I'm confused as I read as to the difference between setting RMAN retention with redundancy vs recovery window.
Can someone give me an explanation how you understand it? I'm reading on the web and in oracle books, and for some reason, it just isn't clear to me what is the best way to go....especially when I see that redundancy and recovery window might both be set??
Thank you in advance,
cayenne

Dear Cayenne
AFAIK RMAN doesn't claim that "you haven't enough backup". Please read the error you got carefully
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DATADG/instance1/datafile/system.284.697137287'
and check the following link:
ORA-01180: Cannot create datafile 1 when doing RMAN restore onto 2nd server
Moreover, could you please use LIST BACKUP command and see whether you have enough backups?
Read "Redundancy Based Backup Retention Policy" from the following link:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/strategy003.htm#sthref139

While itunes was restoring my ipad in recovery mode, I got an error message requesing a passcode. What do I do now?

While itunes was restoring my ipad in recovery mode, I got an error message requesing a passcode. What do I do now?

Hi Amandalee498,
It sounds as if your Windows computer is not detecting the iPad in iTunes. Let's see if we can get that fixed up.
I would suggest that you troubleshoot using the steps in this article -
iPhone, iPad, or iPod touch not recognized in iTunes for Windows
Thanks for using Apple Support Communities.
Best,
Brett L

Recovery Window

Am I correct in assuming that if I configure "recovery windows" like this...
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
...that RMAN will keep/store all the datafiles required to restore my database to 7 days ON DISK?
Which means that I need enough physical disk space in order to accomodate 7 days worth of backups?
thanks

if you are at 10g then its recommended to cater yours backup within FRA if not then retention policy also affect non FRA you need to adhere the dedciated size for yours backup stuff for detail please see with FRA FRA capacity planning
The same dedication size may also goes with non FRA using retetnion policy ,to see How retention policy affects non FRA backupset
Khurram

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

When in the bare metal restore process is the Recovery partition made?

When in the bare metal restore process is the Recovery partition made?
When you boot from the Windows OS disks to do a bare metal restore, you get to the point where it asks you where your backup is, you point to it, and it performs the restore. However, when you are finished, there is also a Recovery partition ahead of
the OS partition. When did the Recovery partition get made, before it asked where the backup is, or after? Respond only if you know.
Thanks!

Hi ,
Could you please let me know the size of the partition you mentioned? Is it 0KB(256KB) partition or 100MB(350MB) Reserved partition or 1.5 (or above) GB parititon? Please capture a screenshot of the disk management.
If it is the 256KB partition, please see:
http://support.microsoft.com/kb/2853247/en-us
If it is the 100MB (350MB) partition, please see:
http://technet.microsoft.com/en-us/magazine/gg441289.aspx
If the size is larger than 1GB, it may be the recovery partition contains the recovery data or OEM partition.
Thanks.
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.

Recovery Window-Based Retention VS Redundancy-Based Retention

Hi Experts,
We'd like to know your take on the use of Recovery Window-Based Retention Policy e.g.
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;against the use of Redundancy-Based Retention Policy, e.g.
CONFIGURE RETENTION POLICY TO REDUNDANCY 7;Do you have any recommendations or preferences to which should be used? Is there a preferred method by oracle?
We're currently setting up RMAN for a client that's using Oracle 11.1.0.7 standard edition, so is there a preference to what's better suited for the standard edition? The plan is to back up data to Disk, and this data will be then backed up to tape.
Thanks

REDUNDANCY 7 is 7 backups -- irrespective of the number of days.
If you are running only 1 backup a day, you'd assume that it is equivalent to 7 days. However, if one day you run a backup twice, then the 7-day old backup becomes redundant ! If, the next day, you again run the backup twice, the 5-day old backup becomes redundant ! (Conversely, if you don't run a backup for 2 days, then even the 9 day old backup is not redundant !).
So, be aware (or beware) that any adhoc backup runs or changes to the backup frequency would change your retention duration (and if this happens 6 months from now, the IT Manager / DBA onsite may not know that retention has changed !)
Hemant K Chitae

Using a System Image to Restore an HP Computer in Windows 8

Hello everyone,
I would like to bring to everyone's attention, the latest HP Help video for PSG. It demonstrates how to use a System Image to restore an HP Computer in Windows 8.
Learn how to restore your HP computer using a system image in Windows 8. With Windows 8, you can backup every file and setting on your computer at once and save it as a system image. If you ever have a software problem, you can restore your PC back to exactly as it was when you created the system image.
For other helpful videos go to hp.com/supportvideos or youtube.com/howto4u.
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓
This question was solved.
View Solution.

I hope this video helps.
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Help Desperately Needed to restore Photoshop 10 catalog to Windows 8 computer and PSE 11

I am trying to backup my Photoshop Elements 10 catalog from my old computer running Windows 7 and restore to my new computer running Windows 8 and Photoshop Elements 11. I reconnected missing files, optimized and repaired the catalog, then repaired and re-indexed visual similarity date. I backed up to the hard drive on the old computer, copied the files to the external hard drive, copies the files from the external hard drive to the desktop of the new computer. From there I opened PSE 11 organizer and tried to restore. When the restore is almost complete I get the following error: "error encountered while restoring. It's recommended that you contact the disc drive manufacturer and upgrade to the latest available firmware for your specific disc drive before trying again.". I also had disabled the virus protection on both computers. I have contacted the external hard drive manufacturer and they are confident the problem is not with the external hard drive. I have spent countless hours on chat with Adobe Technical Chat. I have done everything that has been suggested to fix the problem and I still get the same error message. They referred me to their 800 number for paid technical support and I was on hold for a total of 4 1/2 hours and after being trransferred several times no one came back on the line to help. I have an open case with them and they still have not returned my calls. I even tried using the same backup catalog file and restored to another PC running Windows 7 (and Elements 10) and it worked. Why can't I restore the catalog to Windows 8? Any help is greatly appreciated!

Please refer to following link:-
http://helpx.adobe.com/photoshop-elements/kb/backup-restore-move-catal og-photoshop.html

CTOERROR.flg on factory restore of Envy 15 with Window 8

I get a CTOERROR.flg when trying to factory reset laptop from USB drive.
ChkErrBB.cmd : Detect some error during PININST_BBV.
ChkErrBB.cmd : Check c:\system.sav\logs\BurnsBootWarn.log
ChkErrBB.cmd : or, check c:\system.sav\logs\BurnBootMerge.log
Critical error condition was detected at BBV1...
Refer the following file if exists.
- c:\system.sav\Logs\BurnBootWarn.log
- c:\system.sav\Logs\BurnBoot.log
Switch to 2nCap's WinPE and show [Recovery Manager]'s Incomplete Dialog.
because RM's dialog can't appear on [Start] screen on Win8 enviroment.
customer may not notice RM already shows Error dialog.
there might be unexpected reboot during BBV Clean ro Last...
The process will cause CTO panic because the image might not be normal...
Is this because the BIOS was updated??? How can I put the BOIS back to factory?

Dear Customer,
Welcome to HP Support Forum and we are glad to assist you.
It looks like you are not able to Boot into the Operating System on your Notebook.
We will surely assist you with this.
Originally the Notebook will have the Recovery Partition and that would give you an option to create a set of Recovery Disk. If you have not created those Recovery Disks when the Notebook was in working condition we cannot do that right now
As of now if you need to recover your Notebook with the new Operating System you can check if the Recovery Partition
is in a working condition or not, If yes you can easily recover/restore your Notebook
If Recovery Partition is corrupted
You need to call HP Technical Support and request for a set of Recovery Disks , So you can recover/restore your Notebook at the earliest
OR
You need call up Microsoft and purchase an Operating System with the License Key, So you can recover/restore your Notebook at the earliest
I strongly recommend you to Contact HP Technical Support over the Phone for further assistance without any delay
Hope this helps, for any further queries reply to the post and feel free to join us again
**Click the KUDOS star on left to say Thanks**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.
Thank You,
K N R K
I work on behalf of HP

Understanding report need backup recovery window ..

Hello,
I have a big database which backed up within several days at night time. The retention policy is "recovery window of 3 days". I've tried to analyze the results of
report need backup;But I noticed than this command return just the list of datafiles having latest backup older than 3 days. I've tried to read again the docs:
>
Reports data files for which there are not sufficient backups to satisfy a recovery window-based retention policy for the specified number of days, that is, data files without sufficient backups for point-in-time recovery to any point back to the time SYSDATE - integer.
>
Please correct me if I'm wrong, but I consider that the ability to make recover to any point in time within 3 days require the backup taken earlier than 3 days ago and archivelogs from the time when backup was taken to the recover PIT. Im I right? If so then how I should interprete the results of report need backup ? I can't find the detailed explanations of this in the docs :(
Thanks in advance,
Constantine

You are correct in your appreciations.
This report is about the need of backups, without considering archivelog backups.
It does not mean that listed files are in an unrecoverable situation.
Regards.

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

Restore db outside of Recovery Window

Similar Messages

Maybe you are looking for