Disaster Recovery solution

My colleagues and I are currently working on a disaster recovery solution that would allow us to bring a mirror up of our production database off campus within minutes of it failing. The best DR solution would be to implement Oracle's Data Guard, however we aren't licensed for it because of the cost.

So...our Unix administrator is going to use a program that will copy an entire mount-point anytime a file is changed, added, or removed. We're going to multiplex the files we want mirrored to a new mount-point so we don't grab a bunch of unnecessary things: the controlfiles, online redo-logs, and archived redo-logs. The datafiles will be copied over every night. We should be able to then recover the stale datafiles using the redo-logs that accumulated during the day. Anything I might be missing?

I'll post an update when we've tested.

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

Use rsync on Unix to backup your archive logs

Rsync is a useful Unix tool for keeping directories in synch between two server.  I use it to copy Oracle archive logs from a production server to a test server. This command runs on my test server from the oracle user's crontab every 5 minutes.  It copies the files via SSH.  New files from the source directory are copied to the test backup directory.  If a file is deleted from the source directory, it is NOT removed from the target directory.  I have it setup this way because I want to control that manually.  I have a separate cronjob that purges archive log files over 3 days old. rsync -rave "ssh -l oracle" sourceServer:/u06/oradata/PROD/arch  /u06/oradata/prodArchBkp Rsync also preserves the timestamp of the source file in the target directory. You can also use rsync to delete files in the target directory that do not exist in the source directory. rsync -rave "ssh -l oracle" --delete sourceServer:/u06/oradata/PROD/arch  /u06/oradata/pr
Read more