RE: Backup best practice
- From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
- To: "rstorey@xxxxxxxxxxxxxxxxxx" <rstorey@xxxxxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 20 Oct 2011 18:03:54 +0000
Best practice I believe is to use both the recovery catalog, which you've
hopefully replicated to another server in preferably another data center, and
having it in the control file. We do routine restores of production databases
to different machines every 6 months and intentionally don't use the recovery
catalog. Here are the steps we follow:
rman TARGET / NOCATALOG
set dbid 3836706798;
run
{ set CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK
TO 'oracle8:[backup.tcprd1]tcprd1_%F.';
restore controlfile from autobackup;
}
alter database mount;
Obviously the dbid and file locations will be as per your environment, but this
does work.
Richard Goulet
Senior Oracle DBA/Na Team Leader
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Storey, Robert (DCSO)
Sent: Thursday, October 20, 2011 1:25 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Backup best practice
Okay, looking at a best practices kind of question.
I am setting up a machine to hold the catalog/repository for RMAN backups of my
dbs. And, I even will schedule the backups of the backup machine to be done by
RMAN.
However, what is the best practice for storing this machines backup metadata?
It would seem that you have to store it in the controlfile and use other
methodologies to safeguard the information. To me, you can't use the catalog
because if it dies, how do you do a restore of your backup machine if your
metadata and such about the backup....is in the dead machine?
A suggestion in my class to day was that you could still use RMAN to restore
the backup machine using the DUPLICATE command, as long as you had access to
the the proper backup set pieces.
Thanks.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
