oracle maximum availability architecture · oracle maximum availability architecture: maa cloud...

Oracle Maximum Availability Architecture:MAA Cloud Architectures and Life Cycle Best Practices

April, 2020

Safe harbor statement

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.

2 Copyright © 2020, Oracle and/or its affiliates

Program Agenda

MAA Evolution: On-Premises to Cloud

Cloud MAA Goals

Cloud MAA Architectures

Cloud MAA Configuration Best Practices

Cloud MAA Life Cycle Operations

Cloud MAA with Autonomous Database

1

2

3

4

5

6

Copyright © 2020 Oracle and/or its affiliates.3

Program Agenda


Cloud MAA Goals





1

2

3

4

5

6



On-Premises

On-Premises Exadata and Recovery Appliance

Database / Exadata Cloud

Autonomous Database

MAA Blueprints 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 SLOs


Program Agenda


Cloud MAA Goals





1

2

3

4

5

6


Cloud MAA Goals

• Provides best HA and DR Solutions and Service Levels in the cloud• MAA Reference Architectures to meet customer’s SLAs • Configuration Best Practices for Stability and Reliability• MAA Life Cycle Operations integrated with Cloud APIs and Cloud Console• Evolving and improving with new MAA best practices and capabilities

• Autonomous Database (ADB) provides fully managed MAA solution:• Exadata MAA & Validated Cloud Infrastructure • MAA Cloud Life Cycle Operations • Cloud and Product Enhancements and Fixes


Program Agenda


Cloud MAA Goals





1

2

3

4

5

6


Oracle Maximum Availability Architecture(MAA) Solution Options


Copyright © 2020 Oracle and/or its affiliates.

February 2020: 21 Regions Live, 15 Planned Oracle Cloud Infrastructure Global Footprint

ASHBURNPHOENIX

SYDNEY

CHICAGO

TORONTO

VINHEDO

TOKYOSEOUL

MUMBAI

OSAKA

MELBOURNE

AMSTERDAM

HYDERABAD

JEDDAHDUBAI

LONDON

SAN JOSE, CA

SINGAPORE

SAUDI 2UAE 2

SANTIAGO,CHILE

ISRAEL

FRANKFURTZURICH

MONTREAL

CHUNCHEON

JOHANNESBURG

US GOV

EUROPE

ASIA

SAO PAULO

NEWPORT,WALES

Commercial

Government

Commercial Planned

Government Planned

Microsoft Azure Interconnect Planned

Microsoft Azure Interconnect

10

Oracle Cloud Topology and Terminology

• Fault Domains• Isolated Power &

Network

• Availability Domains• Independent data

centers

• Regions• Geographical separation

< 1ms Latency

Latency varies

DR Protection From AD fault


FD1 FD2 FD3

11

MAA Architecture Building Blocks

Cloud Infrastructure

Backup/Restore Options RAC ADG DB Replication across ADs/Regions

OCI (BM) Backup to OCI Object Storage (manual/automatic)Automatic backup copies across Availability Domains (ADs)

✓ Across ADsAcross Regions via VCN peeringOCI (VM) (with SI or

RAC)✓* ✓

Exa-OCI (X6/X7,X8) ✓ ✓

ExaCC (X6, X7, X8) Backup to NFS, Local Object Storage, ZDLRA, Cloud Object Storage

✓ ✓Across ADs and regions where available


What’s available where?

* RAC VM node are now in separate fault domains.

12

MAA Deployment Automation in the Cloud

Simple UI / CLI / REST interfaces being configured for MAA topologiesDatabases are provisioned with MAA parameter configurationsMAA made easy in the Cloud

• Oracle Cloud Infrastructure (or) • Cloud at Customer


MAA Database Deployment Made Easy

Primary

Regi

on #

1

Standby

Regi

on #

2

GO

LD (D

R) A

D #

1A

D #

2

PLAT

INU

M (H

A)

GG replication

Primary

FSFO

FSFO

Standby

BR

ON

ZE

Single Instance

DB Backup Service RACSI

LVER

(HA

)

DB Backup Service

13


Outage MatrixUnplanned Outage RTO / RPO Service Level Objectives (f1)

Recoverable node or instance failure Minutes (f2)

Disasters: corruptions and site failures Hours to days. RPO since last backup or near zero with ZDLRA

Planned Maintenance

Software/hardware updates Minutes (f2)

Major database upgrade Minutes to hour

SingleInstance or Multitenant

Database

ExaCC/ExaC

S

Primary Availability Domain Secondary Availability Domain

Cloud Backup

Replicated Backups

Dev, Test, Prod - Single Instance or Multitenant Database with Backups

• HA infrastructure for storage and network

• Single Instance with Clusterware HA Management

• MAA cloud backup/restore

• Cloud object storage backups with copy across AD for public cloud

• ZDLRA with incremental forever and near zero RPO for Exadata Cloud@Customer

• Multitenant Database/Resource Mgmtwith PDB features

• Online Maintenance

• Some corruption protection

• Flashback technologies

BRONZE

f1 : RPO=0 unless explicitly specifiedf2 : Exadata systems has RAC but Bronze Exadata configuration with Single Instance database running with Oracle Clusterware has highest consolidation density to reduce costs14

Cloud MAA Bronze Customer Next Steps

• Key Customer Actions

• Use automatic cloud backup (defaults sectionsize=64GB, RMAN parallelism 4/node, LOW compression) or evaluate ZDLRA with Cloud@Customer for lower RPO

• Adjust HugePages after adding or removing Instances/Databases• Refer to MOS 1302539.1 for MAA cloud setting recommendations and cautions

• Operational Practices

• Cloud Test/Dev/UAT resources and real world testing recommended• Update DB and security software as recommended and pick up new cloud

infrastructure software to leverage new features and incorporate MAA practices • Run exachk monthly and validate restore quarterly


https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1302539.1

Backup and Restore Performance Improvements

Default: 18 TB/hr

Default: 2 TB/hrTuned: 8.31 TB/hr

Default: 2.8 TB/hr Tuned: 8 TB/hrOracle MAA Best Practices for Oracle Cloud Backups


https://www.oracle.com/technetwork/database/features/availability/twp-oracledatabasebackupservice-2183633.pdf

Prod/Departmental

SILVER

Bronze +• Real Application Clustering (RAC)• Application Continuity

Unplanned Outage RTO/RPO Service Level Objectives(f1)

Recoverable node or instance failure Single digit seconds (f2)

Disasters: corruptions and site failures Hours to days. RPO since last backup or near zero with ZDLRA

Planned Maintenance

Software/Hardware updates Zero (f2)

Major database upgrade Minutes to hour

Outage Matrix

RAC or RAC One

Database

ExaCC/ExaC

S

Primary Availability Domain Secondary Availability Domain

Cloud Backup

Replicated Backups

f1: RPO=0 unless explicitly specifiedf2: To achieve zero downtime or lowest impact, apply application checklist best practicesCopyright © 2020 Oracle and/or its affiliates.17

Reducing Blackouts & Brownouts for Exadata Cloud

Available only in Exadata and with GI 18.3 and higher. Refer to MOS 2385790.1.

No Service DrainingTPS vs Time

23 seconds blackout

With Automatic Service Draining and New Exadata OptimizationsTPS vs Time

< 1 sec brownout



Cloud MAA Silver: Next Steps

• All Practices of Bronze +

• Key guidelines:

• Follow Continuous Availability - Application Checklist for Continuous Service for MAA Solutions

• If you want lower downtime for instance and server failures, evaluate lower FAST_START_MTTR_TARGET setting after evaluating performance impact

• Operational Practices

• Evaluate HA or performance impact with test system that is identical or similar to production. Ensure application switches over transparently and with minimal impact

• Do not use ACFS for database files or dump directories


https://www.oracle.com/technetwork/database/options/clustering/applicationcontinuity/adb-continuousavailability-5169724.pdf

Outage MatrixUnplanned Outage RTO/RPO Service Level Objectives (f1)

Recoverable node or instance failure Single digit seconds (f2)

Disasters: corruptions and site failures Seconds to 2 minutes. RPO zero or seconds

Planned Maintenance

Software/Hardware updates Zero (f2)

Major database upgrade Less than 30 seconds

Primary Region Secondary Region

Cloud backup

Remote StandbyPrimaryLocal

StandbyCloud

backup

AD2 AD1

Mission Critical

Silver +• Active Data Guard

• Comprehensive Data Protection

MAA Architecture: • Minimum one standby either

across AD or region.• ExaCC/ExaCS primary in one data

center(or AD) replicated to a standby ExaCC/ExaCS in another data center

• Local backups on both sites

GOLD

f1: RPO=0 unless explicitly specifiedf2: To achieve zero downtime or lowest impact, apply application checklist best practicesCopyright © 2020 Oracle and/or its affiliates.20

Capability Physical Block Corruption Logical Block CorruptionDbverify, Analyze Physical block checks Logical checks for intra-block and

inter-object consistency

RMAN, ASM Physical block checks Intra-block logical checks

Active Data Guard

• Continuous physical block checking at standby• Strong isolation to prevent single point of failure• Automatic repair of physical corruptions• Automatic database failover

• Detect lost write corruption, auto shutdown and failover

• Intra-block logical checks at standby

Database In-memory block and redo checksum In-memory intra-block checks

ASM Automatic corruption detection and repair using extent pairs

Exadata HARD checks on write, automatic disk scrub and repair HARD checks on write

Gold – Comprehensive Data ProtectionOracle Data Protection

Run

tim

eM

anu

al

Refer to MOS 1302539.1 for MAA recommendations and current cloud defaults


Oracle Cloud Deployment Model

• Provides HA, data protection and fast failover for database across ADs

• Data Guard synchronous mode possible due to < 1ms between ADs

• Data Guard Fast Start Failover is manual

• VCN Peering required across Regions available today

< 1ms Latency

Latency varies

DR Protection From AD fault


RPO=0 with SYNC with minimal impact. Fast failover with potential < 30 secondsOCI DG Test Results

Example is MAA tuned single instance Data Guard Fast-Start Failover on OCI Bare Metal across ADs


Data Guard Cloud Support MatrixData Guard in the Oracle Cloud

ExaCS ExaCC Gen1 ExaCC Gen 2 Autonomous DB

Hybrid to BM/VM, ExaCSor ExaCC

Console Deployment

Yes Yes Planned Planned No

DBaaS API support Yes Yes Planned Planned No

Role Transition/Reinstate

Monitoring

Console and dbaascli(VCN peeringrequired for cross-regional)

Console and dbaascli

Planned Planned Manual w/ Data Guard Broker

Cloud DG Doc ExaCS Data Guard Doc

ExaCC Gen1 Data Guard Doc

Use ExaCSHybrid Paper to set up Data Guard but limited cloud life cycle support

N/A • OCI BM/VM Hybrid -MAA Whitepaper

• ExaCC Gen1 - MAA Whitepaper

• ExaCS & ExaCC Gen 2 - MAA Whitepaper


https://docs.cloud.oracle.com/en-us/iaas/Content/Database/Tasks/exausingdataguard.htm

https://docs.oracle.com/en/cloud/cloud-at-customer/exadata-cloud-at-customer/exacc/use-data-guard-this-service.html#GUID-FB63CBB2-74E1-4FD6-AFFA-4F902008223C

https://www.oracle.com/technetwork/database/availability/hybrid-dg-to-oci-5444327.pdf

https://www.oracle.com/a/tech/docs/exacc-hybrid-data-guard-final.pdf

https://www.oracle.com/a/tech/docs/hybrid-data-guard-to-exaoci-update-gen2-exacc-exacs.pdf

Cloud MAA Gold: Next Steps

• All Practices of Silver +• Decision:

• Data Guard FSFO across ADs versus Data Guard FSFO across Regions (Site Failover)

• Key Customer Actions• Follow Application Checklist for Continuous Service for Data Guard Fast-Start Failover• Data Guard Fast-Start setup and tuning failover times is manual (refer to updated Oracle Cloud

MAA paper) • Database Rolling Upgrade with Data Guard is also manual. Refer to generic MAA doc

• Operational Practices• Test complete application + Data Guard role transitions



https://www.oracle.com/technetwork/database/features/availability/oracle-cloud-maa-3046100.html

Gold +• GoldenGate Active/Active

Replication• Optional Editions Based

Redefinition MAA Architecture: • Each GoldenGate “primary” replica

protected by Exadata, RAC and Active Data Guard

• ExaCC/ExaCS primary in one data center (or AD) replicated to another primary ExaCC/ExaCS in remote data center (or AD)

• Oracle GG & Edition-based Redefinition (EBR) for zero downtime application upgrade

• Local/cloud backups on both sites• To achieve zero downtime, custom

failover to available GG replica required

Extreme Critical

PLATINUM Primary Region Secondary Region

Cloud backup

Cloud backup

AD2 AD1

GG Replication

AD1 AD2

Standby StandbyPrimary Primary

Outage Matrix

f1: RPO=0 unless explicitly specified f2: To achieve zero downtime or lowest impact, apply application checklist best practices f3: Application failover is custom or with Global Data Services

Unplanned Outage RTO/RPO Service Level Objectives (f1)

Recoverable node or instance failure Zero or single digit seconds (f2/f3)

Disasters including corruptions and site failures Zero (f3)

Planned Maintenance

Most common software/hardware updates Zero (f2)

Major database upgrade, application upgrade Zero (f3)


Use Oracle ShardingUse Edition-based Redefinition

GoldenGate plus 2 Optional Approaches to Further Protect Your Applications

Use Oracle Golden Gate

Required Optional Optional

Primary Standby

Primary Region

Secondary Region

Cloud backup

Cloud backup

AD1 AD2

GG Replication


Use Oracle ShardingUse Edition-based RedefinitionUse Oracle Golden Gate


Primary Standby

Primary Region

Secondary Region

Cloud backup

Cloud backup

AD1 AD2

GG Replication



Active-Active for Near Zero Downtime Maintenance and Migrations and FailuresUsing GoldenGate to Reduce RTO to Zero

A local GoldenGate replica is used for zero-downtime maintenance and migrationsBi-directional replication enables gradual migration of users to new version of application, database or OSZero downtime requires conflict detection and resolution, otherwise downtime measured in secondsIntegration with Active Data Guard zero data loss protection during unplanned outages

Source & TargetOracle & Non-Oracle Database(s)

Target & SourceOracle & Non-Oracle Database(s)

Capture

Delivery

TrailFiles Pump

TrailFiles Pump

Delivery

Capture

Bi-directional

LAN / WAN / InternetOver TCP/IP

TrailFiles

TrailFiles


Enabled using DBMS_ADM_GOLDENGATE.ADD_AUTOCDR ProcedureAutomatic Conflict Detection and Resolution (Auto-CDR)

• No Application Changes or GoldenGate Configuration Required• Invisible timestamp column added to track row changes automatically populated• Automatic “most recent change” win logic in GoldenGate, no need specify any detection or

resolution logic in OGG. • Auto-purging tombstone table created to handle delete/update conflicts• Supplemental logging for all columns enabled

Key Name

City Enable Auto CDR

Key Name

City

CDR$ROW_TS

Key DeleteTS

Invisible Timestamp ColumnDT$_TAB1

TAB1 TAB1


OGG and Data Guard Integration Example

Observer with FSFO

Primary Database and OGG Source Standby Database

Redo Transport(SYNC or ASYNC)

Integrated Extract LogMining

Server

Trail and Other OGG Files in Primary DBFS

Redo Transport

OCI Connection

File I/OOGG Target

Bidirectional (Active-Active)GoldenGate Replication


Sample Deployment – Post Role Transition

Observer with FSFO

(OLD) Primary Database (NEW) Primary Database

Redo Transport(SYNC or ASYNC)

Integrated ExtractLogMinin

g Server

Trail/Checkpoint/BR FilesIn DBFS

LogMining Server

Redo Transport

OCI Connection

File I/O

GG Replica

BidirectionalGoldenGate Replication




Primary Standby

Primary Region

Secondary Region

Cloud backup

Cloud backup

AD1 AD2

GG Replication



Edition-Based Redefinition

• Enables application upgrades to be performed online• Code changes installed in the privacy of a new edition• Data changes are made safely by writing only to new columns or new tables

not seen by the old edition• An editioning view exposes a different projection of a table into each edition to

allow each to see just its own columns• A cross-edition trigger propagates data changes made by the old edition into

the new edition’s columns, or (in hot-rollover) vice-versa

Online Application Upgrade




Primary Standby

Primary Region

Secondary Region

Cloud backup

Cloud backup

AD1 AD2

GG Replication



Oracle Sharding

Intelligent partitioning of data across a farm of independent databases using a common key (i.e. shard key)Some Web-scale OLTP applications use database sharding

• Avoid scalability or availability edge cases of a single large system image database

• Willing to customize data model and applications to enable transactions to be automatically routed to the right shard

Oracle Database can shard without losing all the advanced database technologies

One giant database partitioned into many small independent databases (shards)


Use Sharding with Active Data Guard, RAC or Oracle GoldenGate

Sharding Configuration Options

Active Data Guard with Fast-Start Failover

GoldenGate ‘chunk-level’ active-active replicationwith automatic conflict detection/resolution

Optionally – complement replication with Oracle RAC for server HACopyright © 2020 Oracle and/or its affiliates.38

Cloud MAA Platinum: Next Steps

• All practices of Gold +

• Foundation of platinum is Data Guard:

• ExaCS/ExaCC Gen1: Data Guard full support with cloud console and API

• ExaCC Gen2 and Hybrid Data Guard: Manual Data Guard setup

• Primary and Standby are Symmetric

• DG Cloud functionality includes MAA config, DG role transitions, Monitoring

• Expand on Data Guard with GoldenGate (OGG) cloud solution:

• Essential for Platinum and Zero Downtime Migration and Upgrade

• New: Part I Getting Started with Oracle GoldenGate on Oracle Cloud Marketplace

• New: OOW 2019 Presentation: Oracle MAA for Oracle Database, Exadata, and the Cloud

• Optional use of Sharding and Edition-based Redefinition (EBR)


https://www.oracle.com/a/tech/docs/maa-database-migration-to-oci-with-a-goldengate-hub.pdf

https://www.oracle.com/a/tech/docs/tht6608-oracle-maa-for-the-oracle-database-exadata-and-the-cloud.pdf

Program Agenda


Cloud MAA Goals





1

2

3

4

5

6


Oracle Exadata Cloud Best Practices –

- Exadata Cloud deployment has built-in Exadata and MAA best practices- Exachk –profile exatier1 is near 100% after deployment today

- Refer to Oracle Exadata Database Machine exachk or HealthCheck (Doc ID 1070954.1)

- Exachk –profile exatier1 for initial deployment and before/after planned maintenance- Exachk full checks monthly – comprehensive checks including lower priority alerts/warnings

In the Cloud, ExaCS and ExaCC are Deployed with Exadata and MAA Best Practices


Program Agenda


Cloud MAA Goals





1

2

3

4

5

6


Cloud Tip 1 : Sizing, Planning and Deployment

Understand your requirements 1. Database CPU

processing

2. Database Memory*

3. Database Storage capacity and throughput*

Determine all databases to be consolidated based on requirements

Pick the correct Exadata shape

Work with Oracle Sales or Pre-Sales Consultant

*No oversubscription of memory and storage capacity* Performance impact when oversubscribing CPU and storage throughput limits

“Avoid Outages and Poor Performance”

(Including Dev/Test

Environments)


Cloud Tip 2: Cloud Database Creation and Deployment Success Factors

Creating Cloud databases with Exadata and MAA templates1. Install latest cloud software which includes dynamic hugepage adjustments2. Use only cloud console or cloud APIs to create databases to leverage Exadata MAA database

defaults3. Change memory and performance settings for the application 4. Monitor hugepages and memory to accommodate all database and ASM SGAs for each node

AVOID!!!1. DBCA or your custom create database scripts 2. Inherent your existing initialization parameters (with undoc parameters, arbritary tracing and

settings that you don’t even remember what is used for) 3. No ACFS for database, backup, DB/GI software, diagnostic_dest, ORACLE_BASE,

audit_file_dest


Cloud Tip 3: Use ZDM for Database Migration to Cloud

Tip 3a: Use ZDM for automated physical migration • Backup/Restore for Instantiation• Encryption conversion can happen in cloud

without impacting on-premise• Data Guard switchover reduces downtime• Refer to www.oracle.com/goto/zdm for demo

and documentation• Refer to MAA practices for ZDM MAA MOS

2562063.1• Evaluate network bandwidth prior to migration

with MOS 2064368.1

Tip 3b: Use MV2OCI for automated logical migration• MV2OCI and MV2ADB uses Data Pump to

instantiation and to re-optimize data• Complete orchestration, prechecks and cloudify

• Encryption conversion will happen in the cloud without impacting on-premise

• ZDM integration coming soon

• GoldenGate solution reduces downtime• Oracle Database Migration with an Oracle

GoldenGate Hub Configuration

• Future ZDM solution with GoldenGate.

• GoldenGate restrictions still applicable


http://www.oracle.com/goto/zdm



https://www.oracle.com/a/tech/docs/maa-database-migration-to-oci-with-a-goldengate-hub.pdf

WorkflowZero Downtime Migration

Data GuardSwitchover

Application

ZDMSSH SSH

SQLnet

• When ready, Data Guard Switchover with seconds to minutes of downtime

• Database is registered as new cloud database so cloud life cycle operations can be enabled

• Application from on-premise or in the cloud connects to new Primary in the cloud

Application


Cloud Tip 4: Prepare for Cloud Infrastructure Software Updates

• Exadata Network and Storage• Zero database or minimum application impact • During window, reduce maximum IO throughput

• Exadata Dom0 updates should occur quarterly• Zero database downtime with RAC Rolling

• Service drain is automatic

• Zero application downtime if Continuous Availability - Application Checklist for Continuous Service for MAA Solutions and MOS 2385790.1 practices

• During window, prepare for reduced DB compute processing

“Oracle manages infrastructure software updates”



https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=59457431891314&id=2385790.1&_adf.ctrl-state=1d4fctfdtq_53

Cloud Tip 5: Prepare for DB Quarterly Software Updates

• Customer is responsible for DB Quarterly Software Updates to maintain stability and security compliance

• Zero database downtime with RAC rolling

• Zero application downtime only if Continuous Availability - Application Checklist for Continuous Service for MAA Solutions is followed.

During window, prepare for reduced DB compute processing.

• Key Practices for Success

• Prerequisites completed prior to planned maintenance window:

• Create software plan (target release + one-off, evaluate test/uat, then standby and then primary) • dbaascli DATABASE MOVE for primary and standby, out-of-place, apply one-offs beforehand, and simpler fallback.

• dbaascli PATCH DB if you want to patch subset of nodes or you want to patch a lot of databases on the same OH with one command

• Download latest tools (dbaascli patch tools apply --patchid LATEST)

• Create new DB Home using cloud tooling

• Apply interim patches to new database home, as required

• Run database move precheck

• Run exachk –profile exatier1

• During patching:

• Dbaacli database move –dname <dbname> -home <oracle_home> • only run datapatch after all databases in DG environment is patched



Cloud Tip 5b: Prepare for GI Quarterly Software Updates

• Customer is responsible for GI Quarterly Software Updates to maintain stability and security compliance

• Zero database downtime with RAC rolling

• Minimum application downtime only if Continuous Availability - Application Checklist for Continuous Service for MAA Solutions is

followed. GI software updates do NOT drain the service today except in the case with Autonomous

• During window, prepare for reduced DB compute processing

• Key Practices for Success

• Prerequisites completed prior to planned maintenance window:

• Create software plan with latest cloud doc

• Download latest tools (dbaascli patch tools apply --patchid LATEST)

• Run GI patch precheck (dbaascli patch db prereq --patchid <patchid> --dbnames grid)

• exachk –profile exatier1

• During patching:

• dbaascli patch db prereq --patchid <patchid> --dbnames grid

• Patching the Grid infrastructure is a RAC rolling operation which will stop all database instances on a node that at the time it is being patched.



Cloud Tip 6: Prepare for Exadata Quarterly Software Updates

• Customer responsible for Exadata operating system software updates• Zero database downtime with RAC rolling• Zero application downtime only if Continuous Availability - Application Checklist for

Continuous Service for MAA Solutions is followed. Service drain is incorporated• During window, prepare for reduce DB compute processing• Key Practices for Success

• Updating an Exadata DB System (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)

WARNING: Avoid customizations since they will need to be removed prior to software update and added back afterwards



https://docs.cloud.oracle.com/en-us/iaas/Content/Database/Tasks/exatooling.htm

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2521053.1

https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=331123201593265&id=2566035.1&_adf.ctrl-state=12tlr8ck0h_374

Cloud Tip 7: Use MAA Cloud Backup/Restore Best Practices

• Cloud MAA practices integrated with automatic backup and latest tooling

• Refer to Oracle Cloud Infrastructure Exadata Backup & Restore Best Practices using Cloud Object Storage

• Use cloud backup APIs and use ZDLRA for Exadata Cloud@Customer

• Customizing Backup Settings by Using a Generated Configuration File

• Pick least intrusive backup start time (bkup_daily_time)

• For cloud object storage, pick the day you want to level 0 backup (bkup_oss_L0_day)

• All other defaults are good

• Increase RMAN parallelism (bkup_channels_node=4 default) if current backup/restore rate is not acceptable (e.g. 2.1 TB/hour observed). Disable RMAN compression if database uses a lot of HCC compression

• Periodic restore test is recommended


https://www.oracle.com/technetwork/database/availability/oci-exa-br-bp-objectstore-5573845.pdf

https://docs.oracle.com/en/cloud/paas/exadata-cloud/csexa/customize-backup-configuration-using-bkup_api.html#GUID-ADF73049-B959-4753-9877-EE011FBF0A18__CONFIGFILE

Cloud Tip 8: Leverage Exadata Health Checks and Integrate Monitoring and Alerting

• Real Time Monitoring and Monthly Health Checks keep the Exadata Cloud system healthy and sound

• Oracle Exadata Database Machine exachk or HealthCheck (Doc ID 1070954.1)

• Execute monthly and address FAILURES and WARNINGS

• Use Enterprise Manager

• Deploy EM agents in each database server (DomU)

• Monitor cluster, ASM, Data Guard lag, and database

• Refer to 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

• Use Cloud Console to monitor overall state of your cloud targets


https://mosemp.us.oracle.com/DocumentDisplay?parent=DOCUMENT&sourceId=1969085.1&id=1070954.1

http://www.oracle.com/technetwork/database/exadata/em-exadata-cloud-3959023.pdf

https://www.oracle.com/technetwork/database/availability/exadata-database-machine-kpis-3224944.pdf

https://www.oracle.com/technetwork/database/availability/exadata-adaptive-thresholds-3102556.pdf

7-Eleven Puts Disaster Recovery in the Oracle Cloud with Exadata Cloud Service

7-Eleven is a Japanese-owned international chain of convenience stores, headquartered in the US. It operates, franchises, and licenses approximately 65,000 stores in 18 countries with 9,500 stores in the US.

ResultIn a few weeks, 7-Eleven put into production a DR solution using the best DB cloud platform, managed by Oracle, with the benefits of the public cloud.

7-Eleven ObjectiveProtect on-premises systems with an affordable, production-capable DR solution, avoiding data center expansion.

Industry: Retail (convenience stores)Headquarters: US

Exadata Cloud Service

DR

APPLICATIONSE-Business SuiteOracle RetailHyperion DRMOracle PLMOBIEEODI

PROD

Data Guard

7-Eleven data center

ORACLE CLOUDASHBURN


Program Agenda


Cloud MAA Goals





1

2

3

4

5

6


One Autonomous Database – Two Choices

ORACLEAUTONOMOUS

DATABASE

DedicatedServerless

Ultra-Simple and Elastic Customizable Private Database Cloud in Public Cloud


Autonomous Database Serverless

• Simple – Oracle automates and manages everything

• Deployment, lifecycle, software updates, etc.

– Customer just chooses database compute, storage, and region

• Elastic– Low minimum size - 1 OCPU– Low minimum time commitment - 1 hour– Automatically scales online for true pay-per-use


Autonomous Database Dedicated

• Provides your own Database Cloud running on dedicated Exadata Infrastructure– Runs all your databases - any size, scale, or criticality

• Highest Isolation– Runs inside Secure Isolation Zone for highest protection

from other tenants– Configure multiple Exadatas or Container Databases for

intra-company isolation

• Customizable Operational Policies– Control of provisioning, updates, availability, density


High Availability Policy

• RAC Database in a single Availability Domain, with redundant storage and networking• Nightly Backup that is replicated across ADs

• Protects from the most common sources of downtime such as hardware failures, software crashes, and quarterly software updates

• Service Uptime SLA per Month: 99.95% - less than 22 minutes of downtime*

• Suitable for test, development and non-mission critical production databases

* SLA excludes AD orRegional Failures, datacorruptions and certainplanned maintenance taskslike major upgradesDB Backup Service

Region #1

Database Backups

Primary DatabaseCopyright © 2020 Oracle and/or its affiliates.58

Autonomous Database Patching

• Quarterly Patching of all components (on-demand for critical security issue)• Firmware, OS, Hypervisor, Clusterware, Database• Usage of Gold Image

• Patches are applied in a rolling fashion with RAC cluster and Exadata Storage• Database is continuously available to application• Applications that implement Oracle Application Continuity best practices will run

without interruption


Uptime Availability Enablers

– Real Application Clusters – provides transparent ,near-zero downtime patching, and near-zero downtime for server failover

– Active Data Guard - provides DB upgrade in seconds, corruption prevention and auto repair, disaster failover, reporting offload

– Redefinition – Online Redefinition provides online changes to table and index definitions

– Other building blocks include ASM, RMAN, Flashback, Multitenant etc.

– Exadata provides hardware fault-tolerance, fastest detection of faults and sick components, lowest brownout

– Maximum Availability Architecture integration provides proven Enterprise Mission Critical Architecture, configuration best practices and life cycle operations

– Cloud Automation – complete automation and testing of full stack from database to disks ensures High Availability and prevents configuration and operator issues

ASM RMAN

Flashback

Redef

RAC

Active Data

Guard

Cloud Automation

Multitenant


Automated Lifecycle Management

Backup & Repair

Data Guard HA/DR Operations

Software Updates (Patching)

Software Upgrades

Monitoring & Notification

Elastic Capacity Management

Migration

End-to-end Security

Notify

Lifecycle

Migration

Optimize Manage


External References

• MAA Home:

• http://oracle.com/goto/maa• On-Premises MAA:

• https://www.oracle.com/database/technologies/high-availability/oracle-database-maa-best-practices.html

• Exadata MAA: • https://www.oracle.com/database/technologies/high-availability/exadata-maa-best-

practices.html• Recovery Appliance MAA:

• https://www.oracle.com/database/technologies/high-availability/zero-data-loss-recovery-appliance.html

• Cloud MAA: • https://www.oracle.com/database/technologies/high-availability/oracle-cloud-maa.html


http://oracle.com/goto/maa

https://www.oracle.com/database/technologies/high-availability/oracle-database-maa-best-practices.html

https://www.oracle.com/database/technologies/high-availability/exadata-maa-best-practices.html

https://www.oracle.com/database/technologies/high-availability/zero-data-loss-recovery-appliance.html

https://www.oracle.com/database/technologies/high-availability/oracle-cloud-maa.html

Our mission is to help peoplesee data in new ways, discover insights,unlock endless possibilities.

oracle maximum availability architecture · oracle maximum availability architecture: maa cloud...

Documents