© ViSolve.com All rights reserved. Privacy Statement April Oracle Disaster Recovery Implementation A Non-Technical Overview (Setting-up Oracle Disaster Recovery Environment on x86-64 Linux) ViSolve Migration Team visolve.com (408)

Present the Disk HA/DR Server Present the Disk Standby Instance Standby Database Restored Database New Disk Linux IA64 Linux x86-64 DB Instance Backup Files RMAN Backup Data Guard Configuration (Redo Log Shipping) Production Database Source Machine Target Machine Backup Disk/Tape 2. Backup the production database to the new disk using RMAN Backup. 5. Dismount the backup disk from the source machine. Mount the backup disk on the target machine. 6. Start the DB instance on the target machine. Restore the backup database using RMAN Restore. 7. Configure Oracle Data Guard on the source and the restored database for High Availability and Disaster Recovery. 1. Add/mount a new disk on the source machine. Oracle Disaster Recovery Environment (Using Oracle Data Guard) 4. Manually create a DB Instance on the target machine. DB Instance The Disaster Recovery Environment is now setup using Oracle Data Guard 2 RMAN Restore 3. Configure the Production Database as the Primary Database (require few minutes of downtime). Primary Database Data Sync 8. In a migration environment, switch the role of standby database to primary. Move the application database connection (require database downtime) to the new primary database to complete the migration process. 9. Bring down the source machine. Setting-up a Disaster Recovery Environment During a Migration 10. Build an additional server for HA/DR in the new environment using the same tools and process. We can show you a demo of this approach. Call us today to get access to our Oracle migration sandbox.

Disaster Recovery Environment (Using Oracle Data Guard) 3 Source Machine Linux IA64 Production Database DB Instance Standby Database Linux x86-64 Standby Instance Data Guard Configuration (Redo Log Shipping) 1) The production system goes down 3) The standby database takes over as primary database with the last transaction intact 1) The production system takes over as the primary database 2) The HA/DR server will switch over as standby database Data Sync DB Instance Primary Database Scenario: System failure/planned downtime When the failed or downed system is back in production 2) Oracle Data Guard syncs the data between the servers HA/DR Server NO PRODUCTION LOSS. BUSINESS CONTINUES AS USUAL. 2) Data Sync stops

ViSolve, Inc. 4010, Moorpark Avenue, #205, San Jose, California Thanks for your time! Contact ViSolve today to know how we can help you (408)