Disaster Recovery solution: Update

I tested our previously mentioned DR solution a few days ago. Here's what I did:

First, I took a hotbackup of our production database (PROD) and moved it to our test server.

I then created a new stand-by instance on the test server, started it up in nomount specifying the pfile, and altered it's DBID to match the DBID of PROD. This allows the DR database to apply the archived redo logs.
RMAN> SET DBID XXXXXXXXXXXX;

Next, I restored the controlfile from PROD's backup and mounted the stand-by database.
RMAN> restore controlfile from '/oback/control_PROD_ctl';
RMAN> alter database mount;
RMAN> exit;

The next step was to restore the PROD datafiles.
RMAN> restore database;

After some archived redo logs appeared on PROD, I copied them to the test server and applied them using RMAN.
RMAN> recover database;

The database recovered using all of the available archived redo logs. It did throw an error saying it was looking for the next log which had not been created yet. This can be ignored. I then opened the database using resetlogs.
RMAN> alter database open resetlogs;

Comments

Post a Comment

Popular posts from this blog

Auditing user logon and logoff in Oracle

To track when a user logs on or off Oracle, enable auditing and audit CONNECT in your database.  Then you can query DBA_AUDIT_TRAIL to find logon and logoff info. alter session SET NLS_DATE_FORMAT = 'DD-MM-YYYY HH24:MI:SS'; select username, action,action_name,timestamp,logoff_time from dba_audit_trail where action_name = 'LOGON' and username = '&user'; Here are some more helpful links: http://itechshare.blogspot.com/2010/06/oracle-how-to-track-logon-logout-in.html http://itechshare.blogspot.com/2010/06/oracle-why-dbaaudittrail-shows-more.html
Read more

RMAN Restore vs. Recovery - what's the difference?

RESTORE is used to restore the datafiles from a backup. You can restore up to the time of the backup or a point before using SET UNTIL . You would lose any changes made to the database after the backup by performing only a RESTORE. RECOVER is used to roll the database forward after a RESTORE by applying the redo logs. In essence, RECOVER = RESTORE + redo logs. The following example assumes you have lost your control files and datafiles, but still have your redo logs. $ rman target / nocatalog RMAN> startup nomount; RMAN> restore controlfile from '/oback/controlfile'; RMAN> alter database mount; RMAN> restore database; RMAN> recover database; RMAN> alter database open resetlogs;
Read more