MAA Best Practices for Oracle Database 19c
7 likes4,661 views
The document outlines best practices for Maximum Availability Architecture (MAA) for Oracle Database 19c, detailing improvements across various configurations (bronze, silver, gold, platinum) to enhance high availability, disaster recovery, and data protection. It discusses the cost implications of database downtime, highlights the features and configurations of MAA solutions, and emphasizes the importance of aligning architectures with customer service level requirements. Additionally, it covers enhancements in backup strategies, application continuity, and pluggable databases to support modern database management needs.
MAA Best Practices for Oracle Database 19c
- 1. Maximum Availability Architecture ā Best Practices for Oracle Database 19c Markus Michalewicz Senior Director of Database HA & Scalability Product Management @OracleRACpm http://www.linkedin.com/in/markusmichalewicz http://www.slideshare.net/MarkusMichalewicz Copyright Ā© 2019 Oracle and/or its affiliates. Lawrence To Senior Director of MAA Development
- 2. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, timing, and pricing of any features or functionality described for Oracleās products may change and remains at the sole discretion of Oracle Corporation. Statements in this presentation relating to Oracleās future plans, expectations, beliefs, intentions and prospects are āforward-looking statementsā and are subject to material risks and uncertainties. A detailed discussion of these factors and other risks that affect our business is contained in Oracleās Securities and Exchange Commission (SEC) filings, including our most recent reports on Form 10-K and Form 10-Q under the heading āRisk Factors.ā These filings are available on the SECās website or on Oracleās website at http://www.oracle.com/investor. All information in this presentation is current as of September 2019 and Oracle undertakes no duty to update any statement in light of new information or future events. Safe Harbor Copyright Ā© 2019 Oracle and/or its affiliates.
- 3. Program Agenda ā¢ Motivation & Benefits ā¢ Improvements in Bronze ā¢ Improvements in Silver ā¢ Improvements in Gold ā¢ Improvements in Platinum ā¢ Cloud MAA Copyright Ā© 2019 Oracle and/or its affiliates.
- 4. Average cost of downtime per hour Average cost of unplanned data center outage or disaster Average amount of downtime per year Percentage of companies that have experienced an unplanned data center outage in the last 24 months Impact of Database Downtime 91% $10M$350K Source: Gartner, Data Center Knowledge, IT Process Institute, Forrester Research 87 hours Copyright Ā© 2019 Oracle and/or its affiliates.
- 5. Oracle Maximum Availability Architecture (MAA) Reference Architectures Deployment Choices HA Features, Configurations & Operational Practices Customer Insights & Expert Recommendations Production Site Replicated Site Platinum Gold Silver Bronze Replication Data Protection Flashback RMAN + ZDLRA Continuous Availability Application Continuity Global Data Services Generic Systems Engineered Systems DBCS ExaCS/ExaCC Autonomous DB Active Replication Active Data Guard GoldenGate 24 Scale Out RAC ShardingASM Copyright Ā© 2019 Oracle and/or its affiliates.
- 6. Provide the best HA, Disaster Recovery and data protection solutions for the Oracle databases x Continue to enhance validated Maximum Availability Architecture (MAA) solutions Your success is truly our success!!! Copyright Ā© 2019 Oracle and/or its affiliates.
- 7. MAA Solutions: On-Premises to Cloud On-Premises On-Premises Exadata and Recovery Appliance DBCS/ExaCS/ExaCC Autonomous Database MAA Reference Architectures and Best Practices MAA integrated Engineered Systems (config practices, exachk, lowest brownouts, HA QoS, data protection) Adding MAA Config and Life Cycle Operations, Shifting Admin Ownership to Oracle with MAA SLAs Copyright Ā© 2019 Oracle and/or its affiliates.
- 8. Oracle MAA Reference Architectures Align Oracle Capabilities with Customer Service Level Requirements Business Critical Mission Critical Dev, Test, Prod Extreme Critical Single Instance with Restart Online Maintenance Validated Backup/Restore Silver + Physical Replication Comprehensive Data Protection Gold + Logical Active/Active Replication Advanced HA Options GOLD BRONZE SILVER PLATINUM Bronze + Database HA Active/Active Clustering Application Continuity Copyright Ā© 2019 Oracle and/or its affiliates.
- 9. Maximum Availability Architecture ā Best Practices for the Database 19c Improvements in Bronze Copyright Ā© 2019 Oracle and/or its affiliates.
- 10. Copyright Ā© 2019 Oracle and/or its affiliates. Outage Matrix Unplanned Outage RTO / RPO* Recoverable node or instance failure Minutes to hour Disasters: corruptions and site failures Hours to days. RPO since last backup or near zero with ZDLRA Planned Maintenance Software/hardware updates Minutes to hour Major database upgrade Minutes to hour Single Instance Database Primary Availability Domain Secondary Availability Domain Local Backup Replicated Backups Dev, Test, Prod - Single Instance Database with Backups ā¢ Single Instance with Clusterware Restart ā¢ Advanced backup/restore with RMAN ā¢ Optional ZDLRA with incremental forever and near zero RPO ā¢ Storage redundancy and validation with ASM ā¢ Multitenant Database/Resource Management with PDB features ā¢ Online Maintenance ā¢ Inherent corruption protection ā¢ Flashback technologies BRONZE * RPO=0 unless explicitly specified
- 11. MAA Score Card MAA architectural readiness and configuration practices Database and Exadata Health Checks Assessment Report Health Score, Summary, Findings Findings & Recommendations How to Solve the problem? Automated Orachk/Exachk Healthcheck (Doc ID 107954.1) updated frequently
- 12. Recovery Appliance Recommended Cloud Storage Remote Replica Tape End-to-End Oracle Recovery Validation Near Zero Data Loss for DR Day 1 Full a Day 2 Changes Day N Changes Virtual Full Backup EM Real-Time Protection Status & Space Monitoring Day 1 StateDay 2 StateDay N State Databases Transactional Block Changes No More Full Backups, Incremental Forever Oracle DB 12c-19c on Any Platform Copyright Ā© 2019 Oracle and/or its affiliates.
- 13. RA SF normally replicates to RA Austin When Primary Appliance (RA SF) is not available, backups and redo are redirected to Replica Appliance (RA Austin) ā¢ Virtual fulls are created as normal ā full recoverability supported ā¢ Size Replica per Recovery Window Goal (RWG) requirement: 1x full backup + N RWG days of incremental and redo/arch log backups Bare minimum: 1x full backup + 1 day redo/arch logs backups. When Primary is back online, Replica backups are transferred ā¢ Backups are ingested and processed into virtual fulls ā¢ Normal backups to upstream can be restarted immediately ā¢ Virtual fulls for new backups are created after all transferred backups have completed processing X High Availability for Backup & Recovery RA SF Replication RA SF RA Austin RA Austin Replication RA SF RA Austin Backups to Replica Appliance Replica Appliance Backups transferred to Primary Configuring High Availability ZDLRA Client for Backup and Recovery (Doc ID 2432144.1) Copyright Ā© 2019 Oracle and/or its affiliates.
- 14. Maximum Availability Architecture ā Best Practices for the Database 19c Improvements in Silver Copyright Ā© 2019 Oracle and/or its affiliates.
- 15. Copyright Ā© 2019 Oracle and/or its affiliates. Prod/Departmental SILVER Bronze + ā¢ Real Application Clustering (RAC) ā¢ Application Continuity Unplanned Outage RTO/RPO* Recoverable node or instance failure Seconds Disasters: corruptions and site failures Hours to days. RPO since last backup or near zero with ZDLRA Planned Maintenance Software/hardware updates Zero Major database upgrade Minutes to hour Outage Matrix RAC Database Primary Availability Domain Secondary Availability Domain Local Backup Replicated Backups * RPO=0 unless explicitly specified
- 16. Oracle RAC Provides Active-Active HA ā¢ RAC provides scalability by actively using resources across all nodes ā¢ Zero-downtime planned maintenance for typical software patches (DB, GI, OS) ā¢ Node and instance failures are automatically & transparently handled ā¢ Supports all applications that are supported on single instance databases Copyright Ā© 2019 Oracle and/or its affiliates. Only with Oracle BB Private Network B Private Network Failover
- 17. Transparent Application Continuity ā¢ Failures in the database stack & network lead to ā¢ Interruptions or timeouts in user sessions ā¢ Unknown state of transactions ā¢ Application Continuity masks errors from applications by recovering session state and replaying in-flight requests ā¢ Replay performed on a surviving RAC instance or Data Guard standby ā¢ Eliminates the need to create custom exception code ā¢ Application Continuity extends Oracleās HA capabilities from bottom-to-top ā from infrastructure to applications Copyright Ā© 2019 Oracle and/or its affiliates. Preserving and Replaying Database Requests Across Outages 1 2 3 4 5 6 UCP, JDBC, ODP.Net, OCI Session Pool, Tuxedo, WebLogic ā
- 18. Checklist for Achieving Zero Application Downtime 1. Use Oracle Clusterware Service (never use default service) 2. Use Recommended Connection String 3. Configure FAN for Connection Pool 4. Drain your service for maintenance 5. Use (Transparent) Application Continuity Copyright Ā© 2019 Oracle and/or its affiliates. Application Checklist for Continuous Service for MAA Solutions Using RHPhelper to Minimize Downtime During Planned Maintenance on Exadata (Doc ID 2385790.1) Fleet Patching and Provisioning incorporates MAA practices documentation
- 19. Maximum Availability Architecture ā Best Practices for the Database 19c Improvements in Gold Copyright Ā© 2019 Oracle and/or its affiliates.
- 20. Copyright Ā© 2019 Oracle and/or its affiliates. Outage Matrix Unplanned Outage RTO/RPO* Recoverable node or instance failure Seconds Disasters: corruptions and site failures Seconds. RPO zero or seconds Planned Maintenance Software/hardware updates Zero Major database upgrade Seconds Primary Region Secondary Region Local backup Remote Standby Primary Local Standby Local backup AD2 AD1 Mission Critical Silver + ā¢ Active Data Guard ā¢ Comprehensive Data Protection MAA Architecture: ā¢ At least one standby required across AD or region ā¢ Primary in one data center(or AD) replicated to a Standby in another data center ā¢ Local backups on both primary and standby GOLD * RPO=0 unless explicitly specified
- 21. Data Guard: Real-time Data Protection & Availability Primary Data Center DR Data Center Data Guard Broker (Enterprise Manager Cloud Control or DGMGRL) Copyright Ā© 2019 Oracle and/or its affiliates.
- 22. Active Data Guard Provides Active-Active Disaster Recovery (DR) Zero data loss at any distance Automatic Block Repair DML Redirection Copyright Ā© 2019 Oracle and/or its affiliates. ā¢ Synchronous zero data loss replication ā¢ Database rolling upgrade to reduce downtime for planned maintenance ā¢ Automatic failover for High Availability Primary Open Read-Write Standby Open Read-Mostly Multi-instance Redo Apply for RAC (In Memory supported)
- 23. DML Redirect / Updates on Standby ā¢ Updates on Standby are automatically performed from an Active Data Guard standby to the primary database without compromising ACID ā¢ New documented parameter ADG_REDIRECT_DML controls DML Redirection ā¢ New alter session ADG_REDIRECT_DML allows for per-session override ā¢ New ADG_REDIRECT_PLSQL commands ā¢ Supported with Oracle Database 19c ā¢ Targeted for āRead-Mostly, Occasional Updatesā applications Copyright Ā© 2019 Oracle and/or its affiliates.
- 24. (Active) Data Guard Features 19c 19c Data Guard Hidden Gems ā¢ New Parameters for tuning automatic outage resolution with Data Guard ā¢ Flashback Database enhancements with Data Guard ā¢ Buffer Cache on Active Data Guard preserved after role transition for RAC ā¢ Improved Data Guard Multi-Instance Redo Apply (with in-Memory) Copyright Ā© 2019 Oracle and/or its affiliates.
- 25. Multi-Instance Redo Apply Performance ā¢ Utilizes all RAC nodes on the Standby database to parallelize recovery ā¢ OLTP workloads on Exadata show great scalability Lower Latency Active Data Guard Standby Databases 190 380 740 1480700 1400 2752 5000 0 1000 2000 3000 4000 5000 6000 7000 1 Instance 2 Instances 4 Instances 8 Instances Batch OLTP Standby Apply Rate MB/sec Copyright Ā© 2019 Oracle and/or its affiliates.
- 26. Data Guard Best Practices at a Glance Creation ā¢ 12.1.0.2 or higher: use āRMAN restore from service methodā ā¢ Creating a Physical Standby using RMAN Duplicate (RAC or Non- RAC) (Doc ID 1617946.1) ā¢ Assessing and Tuning Network Performance for Data Guard and RMAN (Doc ID 2064368.1) Network Performance Use oratcptest tool to: ā¢ Assess network bandwidth prior to deployment ā¢ Tune ASYNC transport ā¢ send_buffer_size ā¢ recv_buffer_size ā¢ OS socket limits ā¢ Determine network roundtrip latency with SYNC transport Async Transport ā¢ Push ASYNC performance to provide near zero data loss protection. ā¢ Best Practices for Asynchronous Redo Transport - Data Guard and Active Data Guard: ā¢ https://www.oracl e.com/technetwo rk/database/avail ability/async- 2587521.pdf Sync Transport ā¢ Size online log file properly ā¢ Avoid frequent log switches ā¢ Configure single member standby redo log on fast storage ā¢ Best Practices for Synchronous Redo Transport - Data Guard and Active Data Guard ā¢ https://www.oracle .com/technetwork /database/availabil ity/sync- 2437177.pdf Copyright Ā© 2019 Oracle and/or its affiliates. Ć
- 27. Why Pluggable Databases for High Availability? ā¢ Pluggable Databases are an inherent database feature ā¢ Enable common lifecycle operations in an online fashion ā¢ Integrated with other Oracle High Availability (HA) features
- 28. De-support of Non-Container Database Architecture ā¢ The Oracle Database non-CDB architecture will be de-supported from Oracle Database 20c onwards ā¢ To ease the migration to this architecture, from Oracle Database 19c onwards, the multitenant architecture supports up to 3 user-created Pluggable Databases of any type ā¢ The Multitenant Option is required for 4 or more user-created PDBs
- 29. De-support of Non-Container Database Architecture ā¢ āThe Questionā: ā¢ How to migrate / upgrade to 20c supporting PDBs only? ā¢ Answers: 1. https://mikedietrichde.com/2019/08/13/database-migration-from-non-cdb-to-pdb- the-minimal-downtime-challenge/ 2. Using Transient Logical Rolling Upgrade for Database Migration (Doc ID 2350945.1)
- 30. PDB Failover: Normal Operation PDB1 PDB2 CDB 1 Read-Write CDB 1 Standby Read- OnlyData Guard CDB 2 Read-Write PDB4 PDB2 PDB3PDB1 PDB3 Copyright Ā© 2019 Oracle and/or its affiliates.
- 31. Unplug/plug PDB2 from CDB1 standby to CDB2 and failover application connections PDB Failover after PDB 2 Outage PDB1 Data Guard PDB4 PDB2PDB1 PDB2 PDB3 PDB3 PDB2 CDB 1 Read-Write CDB 1 Standby Read- Only CDB 2 Read-Write Copyright Ā© 2019 Oracle and/or its affiliates.
- 32. Copyright Ā© 2019 Oracle and/or its affiliates. Multitenant āGoldā MAA Unplanned Outages Key Features for Solution RTO RPO Recoverable node or instance failure Real Application Cluster (RAC) Application Continuity (AC/TAC) Secs Zero Disasters: corruptions and site failures Active Data Guard Fast-Start Failover Secs Zero or Secs PDB unrecoverable failure or āsickā PDB (NEW) PDB Failover (unplug/plug) Another target CDB on the same cluster required (MOS 2088201.1) Secs Zero or Secs Planned Maintenance Solution RTO Software and hardware updates RAC, AC or TAC Zero Major database upgrade Active Data Guard DBMS_ROLLING Secs Migration to remote CDB (NEW) PDB Relocate Mins Migration plus upgrade (NEW) PDB Relocate + Upgrade Mins Updated MAA Best Practices Papers: Best Practices For Database Consolidation On Oracle Exadata Database Machine
- 33. Refreshable PDB Switchover Per-PDB replica with only two CDBs to manage! Server1 CDB1 CDB2 Server2 1. create pluggable database Red; 4. create pluggable database Brown; 6. create pluggable database Grey from Grey@CDB2_Link refresh mode every 2 minutes; 2. create pluggable database Red from Red@CDB1_Link refresh mode every 2 minutes; 3. create pluggable database Gold; 5. create pluggable database Grey; Copyright Ā© 2019 Oracle and/or its affiliates.
- 34. Refreshable PDB Switchover Planned switchover Server1 CDB1 CDB2 Server2 1. alter pluggable database Grey refresh mode every 2 minutes from Grey@dblink switchover; Copyright Ā© 2019 Oracle and/or its affiliates.
- 35. Refreshable PDB Switchover Unplanned switchover Server1 CDB1 CDB2 Server2 1. alter pluggable database Grey refresh; 2. alter pluggable database Grey refresh mode none; 3. alter pluggable database Grey open read write; Does not interoperate with Data Guard Fast-Start Failover, auto- block repair, DB rolling upgrade so NOT part of Gold MAA Copyright Ā© 2019 Oracle and/or its affiliates.
- 36. Database Rolling Upgrade Database Rolling Upgrade with DBMS_ROLLING ā¢ Pre-checks and early problem detection ā¢ Fault tolerant, resumable and rollback capabilities ā¢ Three Role Transition Steps: Start, Switchover, Finish ā¢ Potential Maintenance Window: Hours ā¢ Potential Database and Application Downtime: Seconds Copyright Ā© 2019 Oracle and/or its affiliates. Automated Database Upgrades using Oracle Active Data Guard and DBMS_ROLLING
- 37. Maximum Availability Architecture ā Best Practices for the Database 19c Improvements in Platinum Copyright Ā© 2019 Oracle and/or its affiliates.
- 38. Copyright Ā© 2019 Oracle and/or its affiliates. Gold + ā¢ GoldenGate Active/Active Replication ā¢ Optional: Edition-Based Redefinition MAA Architecture: ā¢ Each GoldenGate āprimaryā replica protected by RAC and Active Data Guard ā¢ Primary in one data center (or AD) replicated to another Primary in remote data center (or AD) ā¢ Oracle GG & Edition-Based Redefinition for zero downtime application upgrade ā¢ Local backups on both sites ā¢ Achieve zero downtime through custom failover to GG replica Extreme Critical PLATINUM Primary Region Secondary Region Local backup Local backup AD2 AD1 GG Replication AD1 AD2 Standby StandbyPrimary Primary Outage Matrix * RPO=0 unless explicitly specified ** application failover is custom Unplanned Outage RTO/RPO* Recoverable node or instance failure Seconds Disasters: corruptions and site failures Zero** Planned Maintenance Software and hardware updates Zero Major database upgrade, application upgrade, migration Zero**
- 39. De-support of Non-Container Database Architecture ā¢ āThe Questionā: ā¢ How to migrate / upgrade to 20c supporting PDBs only? ā¢ Answer: 1. GoldenGate can provide Zero Downtime Migration.
- 40. Oracle Sharding for a New Generation of Apps Copyright Ā© 2019 Oracle and/or its affiliates. Using standard MAA techniques to improve availability Linear Scalability Add shards online to increase database size and throughput. Online split and rebalance. Extreme Availability Shared-nothing hardware architecture. Fault of one shard has no impact on others. Geographic Distribution User defined data placement for performance, availability, DR or to meet regulatory requirements. ā¦ ā¦ ā¦ ā¦ ā¢ Oracle RAC and Data Guard meet most application needs preserving application transparency. ā¢ Some large scale applications want to shard data across independent databases and are willing to modify the application to do so and for getting the benefits listed above.
- 41. Maximum Availability Architecture ā Best Practices for the Oracle Database 19c Cloud MAA Copyright Ā© 2019 Oracle and/or its affiliates.
- 42. MAA Evolution from On-Premises to Autonomous On-Premises On-Premises Exadata Exadata Cloud Autonomous Database ā¢ Architecture ā¢ Database Management (Tooling) ā¢ Configuration, Tuning ā¢ Lifecycle Operations (Tooling) ā¢ Application Performance ā¢ Choosing the SLA policy ā¢ Application performance ā¢ Infrastructure Management ā¢ Architecture ā¢ Database Management ā¢ Configuration, Tuning ā¢ Lifecycle operations ā¢ Application Performanceā¢ Infrastructure Management ā¢ Architecture ā¢ Configuration, Tuning ā¢ Database Management ā¢ Lifecycle Operations ā¢ Application Performance ā¢ Blueprints ā¢ Feedback to products & features ā¢ Blueprints ā¢ Exadata is the best integrated MAA DB platform ā¢ Oracle owns and manages the best integrated MAA DB platform ā¢ Cloud automation for provisioning and life cycle operations ā¢ Oracle owns and manages Infrastructure ā¢ Policy driven deployments ā¢ MAA Integrated cloud ā¢ Fully automated Self- Driving, Self-Securing, Self-Repairing Database Customer Oracle Copyright Ā© 2019 Oracle and/or its affiliates.
- 43. MAA Deployment Automation in the Cloud ā¢ Simple UI / CLI / REST interfaces configured with MAA in mind ā¢ Databases are provisioned with MAA parameter configurations ā¢ MAA made easy in the Cloud ā¢ Oracle Cloud Infrastructure (or) ā¢ Cloud at Customer Primary Region#1 Standby Region#2 GOLD(DR) AD#1AD#2 PLATINUM(HA) GG replication Primary FSFO FSFO Standby BRONZE Single Instance DB Backup Service RAC SILVER(HA) DB Backup Service Copyright Ā© 2019 Oracle and/or its affiliates.
- 44. Cloud Configuration Best Practices - Exadata Cloud deployment has built-in Exadata and MAA best practices - Target: 100% MAA Healthscore at deployment time Copyright Ā© 2019 Oracle and/or its affiliates. ExaCS and ExaCC are Deployed with Exadata and MAA Best Practices Oracle Exadata Database Machine EXAchk or HealthCheck (Doc ID 1070954.1)
- 45. Cloud Life Cycle & MAA Life Cycle Operations MAA Practices Create Cloud Databases Uses Exadata MAA templates or MAA templates if done via UI or Cloud APIs Do NOT use custom scripts or DBCA Migration to Cloud Zero Downtime Migration (ZDM) uses MAA practices with Data Guard Logical migration can use GG hub which will be available in ZDM in the future Infrastructure Software Updates Zero Database Downtime Zero Application Downtime requires Continuous Availability - Application Checklist for Continuous Service for MAA Solutions DB/GI Software Updates Zero Database Downtime Zero Application Downtime requires Continuous Availability - Application Checklist for Continuous Service for MAA Solutions MAA collaborating with cloud to add more prereqs and Data Guard support Fleet Patch and Provisioning in the Cloud Copyright Ā© 2019 Oracle and/or its affiliates.
- 46. Cloud Life Cycle & MAA Life Cycle Operations MAA Practices Exadata OS Updates How to update the Exadata System Software (DomU) to 19c from 18c on the Exadata Cloud Service in OCI (Doc ID 2521053.1) How to update the Exadata System Software (DomU) on the Exadata Cloud Service in OCI (19.x to 19.x) (Doc ID 2566035.1) Backup/Restore Use Automatic Backup/Restore with MAA practices Oracle Cloud Infrastructure Exadata Backup & Restore Best Practices using Cloud Object Storage Health Checks Oracle Exadata Database Machine exachk or HealthCheck (Doc ID 1070954.1) Real Time Monitoring and Alerting Enterprise Manager Oracle Enterprise Manager for Exadata Cloud, Exadata Health and Resource Utilization Monitoring - Exadata Database Machine KPIs and Exadata Health and Resource Utilization Monitoring - Adaptive Thresholds Copyright Ā© 2019 Oracle and/or its affiliates.
- 47. Autonomous Database Cloud ā¢ Exadata in a single AD with nightly backup replicated across other ADs ā¢ Protects from the common sources of downtime such as hardware failures, software crashes, and quarterly software updates ā¢ Service Uptime SLA per Month: 99.95% < 22 minutes of downtime* ā¢ Suitable for test, development and non-mission critical production databases High Availability Policy * SLA excludes AD or Region failures, data corruptions and certain planned maintenance tasks like major upgradesDB Backup Service Region #1 Database Backups Primary Database Copyright Ā© 2019 Oracle and/or its affiliates.
- 48. Autonomous Database Cloud ā¢ Exadata with Active Data Guard and Backup ā¢ Protection from hardware failures, crashes, corruptions, patches, upgrades, disasters ā¢ Service Uptime SLA per Month: 99.995NRX% (NRX = No Ridiculous Exclusions) ā¢ 99.995% Uptime = at most 2m 12s of downtime per month ā¢ Goal is for application impact from any one event to be well under 30 seconds ā¢ Suitable for Mission Critical production databases Extreme Availability Policy Primary Database Region #1, AD #1 Region #1, AD #2 Backup Standby Database Active Data Guard Copyright Ā© 2019 Oracle and/or its affiliates.
- 49. Provide the best HA, Disaster Recovery and data protection solutions for the Oracle databases x Continue to enhance validated Maximum Availability Architecture (MAA) solutions Your success is truly our success!!! Copyright Ā© 2019 Oracle and/or its affiliates.
- 50. Thank you! Markus Michalewicz ([email protected]) Senior Director of Database Product Management @OracleRACpm www.linkedin.com/in/markusmichalewicz www.slideshare.net/MarkusMichalewicz