BUSINESS CONTINUITY AND DISASTER RECOVERY FOR ORACLE 11g ENABLED BY EMC VMAX 10K AND EMC RECOVERPOINT Technical Presentation EMC Solutions Group 1
Agenda Business case Symmetrix VMAX 10K overview RecoverPoint overview Solution overview Solution architecture Oracle database design Test scenario Solution benefits Summary 2
Business Case Reduce Risk Improve SLAs Business Challenges: Downtime Application and data growth Managing demanding SLAs Budget constraints Symmetrix VMAX 10K delivers: Scalability, availability, and efficiency RecoverPoint is a proven technology: Providing local and remote replication Minimal application degradation 3
Symmetrix VMAX 10K Overview NEW HARDWARE PLATFORM Scalable performance and Tier 1 reliability, availability, and serviceability Virtual Matrix Architecture Up to four engines, 1080 drives, and 1.5 PB of usable capacity Easy to order, bundled software 100 percent virtually provisioned Fully Automated Storage Tiering for Virtual Pools (FAST VP) included Factory pre-configured, built to order Four hours to first I/O Leading replication Integrated EMC RecoverPoint splitter EMC TimeFinder for Symmetrix VMAX 10K 4
RecoverPoint Overview RecoverPoint Family NEW Array-based write splitter for EMC RecoverPoint integrated with VMAX 10K DVR-like recovery to any point in time Dynamic synchronous and asynchronous replication Customized recovery point objectives (RPOs) supporting: Instant access to local and remote point-in-time images using DVR-like recovery Repurposing of recovered images without impact on production activity Replicate from VMAX 10K to VMAX 10K/VNX/CLARiiON WAN bandwidth data reduction of up to 90 percent of changed data Nondisruptive business continuity and disaster recovery testing 5
Solution Overview This solution is based on the Symmetrix VMAX 10K array leveraging a virtual matrix architecture and is designed with simplicity in mind. This solution tests and details the transactional capabilities with disaster recovery (DR) integration of an OLTP Oracle 11g database in a physical environment. The DR testing is enabled by two VMAX 10K arrays and RecoverPoint. Test scenarios include: Site failover and failback Nondisruptive disaster rehearsal Point-in-time database recovery RecoverPoint operation when the VMAX 10K is operating in a degraded mode 6
Physical Environment Oracle 11g database accessing single production database on Symmetrix VMAX 10K array Swingbench load generator Continuous local and remote replication with RecoverPoint using array-based splitters 7
Oracle Database Design ASM disk group Redundancy Capacity Attributes Replicated with RecoverPoint +DATA External 800 GB Data files Yes +REDO External 100 GB Redo log files Yes +TMP External 200 GB Temp files No +FRA External 1,440 GB Archive logs Backup files Yes The benchmark profile is TPC-C like. Oracle database size is 500 GB. Benchmark test duration is 30 minutes and userload is 1,000. 8
Test Scenarios Test scenario 1: RecoverPoint site failover and failback Test scenario 2: RecoverPoint disaster testing process Test scenario 3: RecoverPoint PIT database recovery Test scenario 4: RecoverPoint operation when the VMAX 10K is operated in degraded mode 9
Test scenario 1: RecoverPoint site failover and failback Remote site recovery was enabled by RecoverPoint continuous remote replication (CRR) to improve the business continuity. Fail over production Oracle database to the recovery site using RecoverPoint CRR, Oracle database and applications operations continue at the recovery site Fail back the production database to the production site 10
Test scenario 2: RecoverPoint disaster testing process Do a database consistency check and disaster test on the recovery site using RecoverPoint CRR, without impact on the production application: 1. On the recovery site, after enabling the latest image access on the recovery site, CRR mount host has the read/write access to the remote copy of the production volume. 2. Rescan and remount the ASM disk groups. 3. Start up the database on the recovery site and check consistency. 4. Shut down database on the recovery site. 5. Disable Image Access on the recovery site to close the image access. There is no impact on the production Oracle database or logs during testing. 11
Test scenario 3: RecoverPoint PIT database recovery Oracle database restored in the event of data corruption from the RecoverPoint CDP image RecoverPoint offers very high restore point granularity: Administrators can select: User-defined bookmarks Snapshots generated automatically by RecoverPoint Oracle instance recovery from the crash-consistent image 12
Test scenario 4: RecoverPoint operation when the VMAX 10K operates in a degraded mode By using Symmetrix VMAX 10K and RecoverPoint: No disruption in communications in the event of a failure, the failed I/O is simply transmitted down the alternate path. Symmetrix splitter is able to cope with the loss of a director redirecting split Writes are executed down alternate channels in the event of a director failure, which means a highly available DR solution. After the director is recovered, RecoverPoint automatically returned to normal state without manual intervention. One of the front-end director ports was forced offline, which caused the director to go into a degraded state. 13
Solution Benefits Simplified replication of Oracle OLTP database environments using RecoverPoint. Rapid recovery from unplanned disasters using RecoverPoint with Symmetrix VMAX 10K. Nondisruptive disaster recovery rehearsal using RecoverPoint. Point-in-time Oracle recovery from bookmarked RecoverPoint images. 14
Summary Simplified DR Integration of RecoverPoint splitter technology into the Symmetrix VMAX 10K simplifies RecoverPoint implementation and enables DR standardization across applications protect all applications one way. Granular DVR-like Recovery RecoverPoint is a mature technology, with an intuitive GUI, that enables faster recovery with a granularity not possible with other replication technologies. Nondisruptive DR testing RecoverPoint enables disaster recovery scenarios to be tested without affecting production or interrupting replication, while maintaining consistency across protected consistency groups. 15