Anthony Key
asked on
Using Control File as repository for RMAN. I am not seeing old backups from 4 or more days ago. How do I see at least 4 - 7 days of backup?
Hi, I'm using the control file as my RMAN repository and I have done 7 or more backups on my development database. When I go into RMAN and do a 'list backup' I only see 3 days worth of backups. I did some reading and I came across a parameter called 'CONTROL_FILE_RECORD_KEEP_ TIME' and found (show parameter CFRKT(shorten) that the value set in my database is 7 for seven days which is the default setting to keep reusable records which include backup records. After doing some more reading I found out that the 'CFRKT' parameter doesn't really relate to RMAN. My question is how do I maintain at least 7 days of backup records in the Control file without the use of a recovery catalog? And is there a way for me to add back the backups if I can restore them to their old backup location? I'm getting ready to start testing some recovery scenarios and it will look bad it I can't go back a few days ago, this problem will justify the continued use of hot backups instead of moving forward to 11g.
Thanks,
7Souls
Thanks,
7Souls
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>>And is there a way for me to add back the backups if I can restore them to their old backup location?
Yes. You can put them back by re-cataloging them (after changing the CFRKT as above).
Look up the RMAN "CATALOG" command.
catalog backupset, backuppiece or start with ... for a wildcard.
Yes. You can put them back by re-cataloging them (after changing the CFRKT as above).
Look up the RMAN "CATALOG" command.
catalog backupset, backuppiece or start with ... for a wildcard.
ASKER
Hi mrjoltcola and slightwv,
I quess what I will do to cover myself is:
This way I would be covered when I start testing the recovery next week. I've read about the 'retention policy' but I am not able to make a clear distinction between 'recovery window of 7 days' and 'redundancy 7' which one will retain the backup rows needed to allow me to recover my database within the 7 day window? Would I need to have backup files at the backup location at all times or can I put the files back when I'm ready to do the recovery?
Thanks,
7Souls
I quess what I will do to cover myself is:
1. Change the 'CONTROL_FILE_RECORD_KEEP_TIME' to 10 as suggestedl
2. 2 Configure the retention policy to redundancy 7;
This way I would be covered when I start testing the recovery next week. I've read about the 'retention policy' but I am not able to make a clear distinction between 'recovery window of 7 days' and 'redundancy 7' which one will retain the backup rows needed to allow me to recover my database within the 7 day window? Would I need to have backup files at the backup location at all times or can I put the files back when I'm ready to do the recovery?
Thanks,
7Souls
>>I am not able to make a clear distinction between 'recovery window of 7 days' and 'redundancy 7'
You don't want redundancy 7. Window of 7 days is what you want.
You don't want redundancy 7. Window of 7 days is what you want.
Consider, if you use REDUNDANCY 7, and backup once a day, you'll retain 7 days worth. But if you backup once a week, then you'll retain 7 weeks worth.
ASKER
Hi mrjoltcola,
Thanks for the response about seting the CFRKT parameter. What I need to set is the redundancy for 'Window of 7 days' what is the statement for that?. The reason I ask is that I am working remotely from my reference materials.
Thanks,
7Souls
Thanks for the response about seting the CFRKT parameter. What I need to set is the redundancy for 'Window of 7 days' what is the statement for that?. The reason I ask is that I am working remotely from my reference materials.
Thanks,
7Souls
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
mrjoltcola, gave me the correct solutions.
Thanks,
Thanks,
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#i1008093
Your script you are using might be deleting obsolete backups.
I don't know of a way to make obsolete deleted backups usable again.