Oracle Zero Data Loss Recovery ApplianceRMAN, Oracle Secure Backup, Zero Data Loss Recovery...

Copyright © 2016 Oracle and/or its affiliates. All rights reserved. |

Oracle Zero Data LossRecovery Appliance


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, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

2


Oracle Backup/Recovery Portfolio

ZFSGeneral Purpose

Backup

ZDLRABackup Optimized

forOracle Databases

Storage TekTape Backup

Archive

Database Backup CloudCloud-Based Backupfor Oracle Databases

Archive Storage CloudGeneral Purpose Archival Backup


BACKUP IS ONE THING

RECOVERY IS EVERYTHING

4


Key Benefits of ZDLRA

Save Resources – Vastly More Efficient & Scalable

Recover with Confidence – Continuous Recovery Validation

Save Time & Effort – Fully Automated Data Protection

Cost Effective – Storage Efficient, Network Efficient, People Efficient

1

2

3

5

4


The Ultimate in Database Recovery

• Real-time redo transport delivers sub-second RPO

• Virtual full backups enable recovery to any point in time

• Ongoing validation, autonomous self-healing and real-time recovery status/alerting ensure recoverability

• Ready-to-recover full database image at all times

Reduces Overhead

• Offloads backup and archive processes from production resources; eliminates server-based operations and backup agents, reduces network load

• Reduces admin time to manage backups by 1/3

Enterprise-class Data Protection-as-a-Service (DPaaS)

• Linear scalability of compute and capacity up to 10+PBs of capacity and 216 TB/hr restore

• Policy based automation and standardization across all Oracle databases in the environment

6

Zero Data Loss Recovery Appliance for Database Recovery

Gold PolicyCustomer Critical

Silver PolicyInternal Critical

Bronze PolicyDev/Test

Delta

Push

Delta

Store

01001010110100101011010100101001010010101100

Backup is One Thing Recovery is Everything


ZDLRA Architecture Concepts

1. Delta Push – Change Based Backups / Incremental Forever

2. Delta Store – Quasi “database” of changed blocks

3. Real-Time Redo Protection – Remotely Mirrored Redo

4. Virtual Full Backup – Synthetically Generated from the Delta Store

7


Day 0Full

Day 1incremental

Day Nincremental

Delta StoreProtectedDatabases

Restore Database to Day “N”

Day N Virtual Full

Day 1 Virtual Full

Restore Copy to Tape/VTL

Online & Archived Redo

ZDLRA Architecture Delta Store, Incremental Forever, Virtual Full Backups, Remote Logging

Replica

Delta Push


ZDLRA Architecture Concepts (continued…)

5. All database versions (10g+) and all platforms (Windows, Linux, Unix, etc.)

6. Integrated RMAN Catalog / Metadata / Media

7. Single User Interface via OEM (with role separation)

8. ZDLRA Replication – Catalog Backups on Ingest

9. ZDLRA Managed Data Archival – Archive to Tape, VTL, etc.

10. Integral Component of Oracle’s Maximum Availability Architecture

9


Edition-based Redefinition, Online Redefinition, Data Guard, GoldenGate– Minimal downtime maintenance, upgrades, migrations

Active Data Guard– Data Protection, DR– Query Offload

GoldenGate– Active-active replication– Heterogeneous

Active Replica

RMAN, Oracle Secure Backup, Zero Data Loss Recovery Appliance

– Backup to disk, tape or cloud

Enterprise Manager Cloud Control– Site Guard, Coordinated Site Failover

Application Continuity– Application HA

Global Data Services – Service Failover / Load Balancing

RAC– Scalability– Server HA

ASM– Local storage

protection

Production Site

Flashback– Human error

correction

Oracle Maximum Availability Architecture (MAA)

10







1

2

3

11

4


ZDLRA: Save DB Storage & Server ResourcesOffload Backup Processing, Eliminate Expensive Backup Agents, Reduce Network Load

Database Server Today

Performance degrades with backups

Disk / Tape / Dedupe Backup Agents

Backup Operations: Merge, Compress, Validate, Delete,

Full/Tape Backups

Performance improves with backup offload

Database Server with Recovery Appliance

Disk / Tape / Dedupe Backup Agents

Backup Operations: Merge, Compress, Validate, Delete,

Full/Tape Backups

Delta

Push

12


Daily Full Backup

13

Last Backup

Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat

Archived Redo

Backup of Archived Redo

+RMANCatalog

MediaCatalog


RMAN> crosscheck backupRMAN> restore validate

PROD

Full Full FullFull Full Full Full Full Full Full Full Full Full Full Full Full Full Full Full FullFull

Un-Changed DataChanged Data

Inefficient backup, easy recovery

Copyright © 2016 Oracle and/or its affiliates. All rights reserved. | 14

200 Databases150TB Data2% Daily Change2% Daily Redo Generation

US Based Manufacturing

Company

1071

21

1071

3

502

137

570

165

0

200

400

600

800

1000

1200

De-Dupe for Space ZDLRA

Daily Full Backup vs. ZDLRA

Weekly SAN I/O (TB)

Weekly Backup Time (h)

Monthly WAN Transfer (TB)

Space (TB) - 30 day retention


Weekly Full, Daily Incremental

15

Last Backup


Archived Redo

Backup of Archived Redo

+RMANCatalog

MediaCatalog


RMAN> crosscheck backupRMAN> restore validate

PROD

Full Full Full

Incrementals Incrementals Incrementals

Un-Changed DataChanged Data

More efficient backup, slow and more difficult recovery


800 Databases600 TB Data2% Daily Change2% Daily Redo Generation

US based HealthcareCompany

756

84

189

49

1170

365

1051

660

0

200

400

600

800

1000

1200

1400

De-Dupe for Performance ZDLRA

Weekly Full Daily Incremetal vs. ZDLRA

Weekly SAN I/O (TB)

Weekly Backup Time (h)

Monthly WAN Transfer (TB)

Space (TB) - 30 day recovery window


ZDLRA – Superior ApproachIncremental Forever + Remote Logging

17

Last Incremental


Remote MirroredRedo Stream

IntegratedCatalog within ZDLRA

PROD

One Time Full

Daily Delta Push

Day 0Full

Day 1incremental

Day Nincremental

Day N Virtual Full

Day 1 Virtual Full

Zero Data Loss







1

2

3

18

4


High Profile Recovery Failures

State of Virginia (Computer World)

– SAN memory failure, problem mirrored to standby SAN

5-day

outage

American Eagle - Specialty Retailer (Computer World)

– Disk failure, followed by mirrored disk failure. Restore from local backup failed. Restore using copy at DR site also failed

8-day

outage

5-day

outage

Tieto - Cloud Infrastructure Provider (Channel Register)

– Storage array failed, unable to read tape backups used for DR

19

Low Incidence of Failure but Catastrophic Impact


Data Validation & Repair

Points of Validation

– Ingest of Backupsets & Redo Logs

– Indexing Backupsets into Delta Store

– Replicating Backupsets & Redo Logs

–Optimization of the Delta Store

– Timer Based Validation

– Validation during Restore

–Mirror Sync Validation

Automated Data Repair

– Fill redo gaps using FAL

– Repair using source database

– Repair using replicated data

–Mirrored disk repair

Reporting Validation Status– Alerts on Unable to Repair

– Reports on Repair Actions

– Repair Job Execution


Real-Time Recovery Status for All Protected DatabasesDatabase Level Recoverability

Partial screenshot or Recovery Appliance Protected Database Page:

Complete Database Recovery Spectrum at your finger-tips!

Current Point-in-time-recovery (PITR) capability for the database from Recovery Appliance backups

Current Unprotected Data Window for the database

21


Real-Time Redo Protection

General Purpose Backup Appliance

• Backup taken once a day• Periodic Redo Log Sweeps• Data loss exposure: all transactions since last backup

Zero Data Loss Recovery Appliance

• Continuous Real-Time Redo Transport (optional) • Propagate transactions from in-memory buffers• Immediate protection of last transmitted SCN

Protected

Databases

Data loss is inherently bad.Even worse..it creates massive consistency issues across databases







1

2

3

23

4


Database Protection as A Service – Manage Many as One

• Databases are managed as a group (by policy) to define:

– Replication

– Scheduling copy of backup to tape or cloud

• Same or different policy on remote Oracle Recovery Appliance

• Reporting by policy and database

• EM Group(s) may be used to quickly add all databases within the group to the Recovery Appliance

Protection Policy

- Defined Class of Service

• Recovery requirements

− Disk

− Tape or Cloud

• Maximum on disk

retention

• Prioritization of

backups

• Polling local backups

• Unprotected data

window threshold

Business SLAs categorized:- One policy per database tier

Databases


Policy Based Protection – Manage Many as One

Gold Policy – Customer Critical

Disk – 30 daysTape – 90 days

Silver Policy – Internal Critical


Bronze Policy – Test/Dev


Tape

Replica

Replica ApplianceIs also policy based


DBA Friendly – Easy Transition

① RMAN> RESTORE DATABASE

② RMAN> RECOVER DATABASE

③ RMAN> OPEN DATABASE

Virtual Full Backup Constructed & Sent

Retrieve and Apply Redo LogsAny Oracle

Database Version 10g+


Simplify RMAN Scripts

• ZDLRA Eliminates Catalog Management

– 18 RMAN Commands Eliminated

– Fully Integrated into ZDLRA

– Enhanced Functionality

• Eliminate Archive Log Sweeps

–Move to FRA Managed Redo

– Policy Based FRA Data Retention

• Move to Daily Incremental Only– 1 Simple script executes daily (~3 lines of RMAN code, same for every DB)

– Automatically generated script via OEM

– Eliminates complex weekly/daily schedules


Eliminate 3rd Party Agents

• ZDLRA software is part of Oracle DBMS

– Installed by default with Oracle12c

– Simple download for prior releases

– Upgraded automatically as part of Oracle RDBMS software

• No Separate Software

– No separate install

– No separate configuration

–No separate management

– No separate upgrade/patching


Policy Based ReplicationRemote Data CenterLocal Data Center

One Way

Bi-Directional

Hub & Spoke

Tape Library


Unified End-to-End Control

• ZDLRA Admin centrally monitors and manages all database protection activity across all tiers

• Database Admin monitors the protection status of their database from disk, to tape, to replica

–Offloaded replicas and tape backups appear in Recovery Catalog

30

Tape

Remote

Appliance

Enterprise Manager

Tape


Recovery Appliance Home Page in Enterprise Manager

• Sections include:

– Summary of current and recent activity

– Protected database backup/recovery issues

– Daily data sent / received

– Performance

– Media Manager status

– Replication status to / from

– Storage Location status

– Incidents and Events

Dashboard for Current Status of the Backup Environment

31

At-a-Glance Backup Volume & Performance Charts

Days GB

Current Recovery Window of 4.8 Days > Goal of 2 Days - OK

< 1 sec

< 1 sec


Real-Time Database Recoverability & Space Monitoring

34

Enterprise Manager Provides Key Metrics At Your Fingertips

Current Recovery Window: 6 Days

Projected Space Needed for Recovery Window Goal: 2.69 TB

Recovery Window Goal: 10 Days

Reserved Space: 7.9 TBUsed Space: 2.5 TBDeduplication Ratio: 10:1

Current RPO: < 1 sec !


Management Reports

• Protected Database Details

• Recovery Window Summary

– Recovery status by protection policy

• Top 10 Protected Databases by Data Transfer

• Capacity Planning Reports:

– Summary

– Details

Generate on a Recurring Schedule or on an Ad hoc BasisProtected Database Details Report (Partial screenshot):

35







1

2

3

36

4


ZDLRA is Change-Based (Delta Push)

• Only captures changes to data

–Oracle DBMS (any DBMS) tracks and manages changes to data

– ZDLRA taps into these mechanisms

• De-Duplication looks for Un-Changed data

– Generic technology works on ANY data (works better with non-database data)

– Attempts to identify and discard data that has NOT changed

– Not very accurate, only identifies a portion of the un-changed data

– Depends on disabling Oracle DB (RMAN) performance features

37


Space Savings = Cost Effective

Calculation Total

Total Size of Databases Sum of database sizes 100 TB

Less Backup Optimization (est. 20%) 100TB - (100TB * 20%) = 80 TB

Daily Change Rate (2%) 100TB * 2% = 2 TB

Daily Redo Generation (2%) 100TB * 2% = 2 TB

Data Retention Period (30 days) 80TB + (30 * 2TB) + (30 * 2TB) = 220 TB

Compression (est. 50%) 220TB * 50% = 110 TB

Total Space: 110 TB

Daily Full Backup Equivalent (100 TB * 30) + (2 TB * 30) = 3,060 TB

Space Savings 3,060 TB – 110 TB = 2,950 TB

@10X De-duplication (poor performance) 3,060 / 10 = 306 TB

@4X De-Duplication (poor de-duplication) 3,060 / 4 = 765 TB

38


WAN Savings = Cost Effective

Daily Full Backup WFDDI ZDLRA

Database Size 100 TB 100 TB 100 TB

Daily Change Rate 2TB 2 TB 2 TB

Daily Redo Generation 2TB 2 TB 2 TB

Weekly Backup Volume 714 TB 128 TB 4 TB

Compression/De-Duplication 10X 4X 2X

Weekly Replication 71 TB 32 TB 14 TB

Monthly Replication (4.3 weeks/month) 305 TB 137 TB 60 TB

Relative Monthly WAN Saving (GB) 250,880 GB 78,848 GB

Monthly Excess WAN Costs ($) at $0.05/GB $12,544 $3,942

Yearly Excess WAN Costs ($) $150,528 $47,304


Deep Dive


Oracle ZDLRA: The Time Machine for the Enterprise

“On balance, the ZDLRA represents the most integrated, end-to-end backup and recovery system designed specifically for Oracle database that we’ve seen to date. Oracle has taken a different approach than that of other appliances by focusing on recovery with an attempt to automate the backup process and eliminate the guesswork out of whether backups can be both restored and recovered. ”

—David Vellante, Wikibon

“Oracle Backup and Recovery Strategies:Moving to Data Protection as a Service”

41


• Base Rack

– 2x Compute Servers with high speed connectivity *• Eight 10 Gb Ethernet ports per rack

• Twelve 40 Gb InfiniBand ports per rack

• Optional Four 16 Gb Fibre Channel ports for tape connectivity

– 3x Storage Servers *• Each storage server has 12 high capacity disks

• Customers choose number of additional storage servers at purchase or later to increase capacity

• Full Rack: 2x Compute Servers, 18x Storage Servers

From Base Rack to 18 Racks Wide

Extra Storage

Fully Redundant

Recovery ApplianceBase Rack

* Ref. Data Sheet for latest configuration info


• Add InfiniBand connected racks to scale

• Can expand with new generation hardware

• Scale to 18 Racks

– Up to 216 TB/hour Delta Ingest and Restore

Recovery Appliance Scaling

Performance per Full Rack

• Up to 120 TB/hour Virtual Backup

Rate

• Up to 12 TB/hour Sustained Delta

Ingest

• Up to 12 TB/hour Restore Rate

43


Recovery Performance Comparisons

• Compare to WFDDI 2X-3X faster or More– Restore from full vs. Full + 6 Incrementals

– Rule of Thumb is 2X-3X more time for full + incremental

• Block Media Recovery w/WFDDI 7X faster–Must restore the last full, then apply redo (7 days) to reach current point

• Compare to Daily Full Constrained by LAN/SAN/Server Infrastructure– Alleviate LAN/SAN/Server stress through Delta Push with ZDLRA

• Compare to Snapshots Use Data Guard– Snapshots are not proper backups

– Use Snapshots only for transient fallback such as during upgrades


Delta Store – Efficient Indexing

45

Day 0Full Backup

A0 B0 C0 D0 E0

Day 1Incremental Backup

C1 D1


A2 D2


B3 C3


A4 C4 D4

Day 1 - Virtual Full Backup

A0 B0 E0C1 D1


A2 B0 E0C1 D2


A2 B3 E0C3 D2


A4 B3 E0C4 D4


Delta Store – Efficient Storage Management

46


A0 B0 E0C1 D1


A2 B0 E0C1 D2


A2 B3 E0C3 D2


A4 B3 E0C4 D4

On Day 4 Assuming 3-day recovery window, upon space pressure …

Space released for blocks not needed for recovery window goal.

Day 0Full Backup

A0 B0 C0 D0 E0


C1 D1


A2 D2


B3 C3


A4 C4 D4


Delta Store – Periodic Optimization for Restore

A0 B0 C0 D0 E0

C1 D1 A2 D2 B3

C3 A4 C4 D4 free

B0

E0

C1

A2 D2

B3

C3

A4 C4 D4

free

freefreefree

free

Day 4 - Virtual Full Backup (Optimized for Restore)

Day 4 - Virtual Full Backup (Non-Optimized for Restore)

Physical LayoutDay 0Full Backup

A0 B0 C0 D0 E0


C1 D1


A2 D2


B3 C3


A4 C4 D4

Optimization

Reorder blocks for most recent backup so as to read sequentially with minimal I/O overhead


Backup (Delta Push) Workflow

48

HTTP Servlet

RFS

Backup Staging Area (FLASH)

RAC Node-1(Sessions &

Tasks)


Tasks)

Enterprise Manager

ValidateData Blocks

Delta Store

Index & Compress Blocks

Create Virtual Full

Redo Blocks

Data Blocks

Redo Blocks

Validate Redo Blocks

Delta PushUsing RMAN Module

Data Blocks

Redo Staging

Area

Archived Redo Log Backup

ReplicaZDLRA

Incremental Backups

Archived Redo Log Backups

Tape

Full/Incremental Backups

Archived Redo Log Backups


Restore Workflow

49

HTTP Servlet


Tasks)


Tasks)

Enterprise Manager

Full Backups Prepared for Network Transmission

Delta Store

Re-assemble & Validate Physical Full

Backup

Redo Blocks

Data Blocks

Full Backups

ReplicaZDLRA

Tape

Full Backups

Archived Logs

Virtual Full Backups

“RESTORE DATABASE”

“RECOVER DATABASE”

Archived Log Backups


Tape Integration

• Oracle Secure Backup

– The OSB Media Manager is integrated into ZDLRA

– OSB manages tape resources directly through Fiber Channel connections

• 3rd Party Media Manager (NetBackup, etc.)

– 3rd party MMV Client is installed on ZDLRA

– ZDLRA pushes backups to tape and recalls them upon restore

– Same backup/restore process as with OSB, but not integrated management

• Partitioned Tape Libraries

– Existing tape library can be partitioned to allow OSB to manage some resources

– Existing MMV software can manage a separate partition of the library

50


Recovery Window = Data Retention

Sun12:00 – 6:00AM

Mon12:00 – 1:00AM

Tues12:00 – 1:00AM

Wed12:00 – 1:00AM

Thurs12:00 – 1:00AM

Fri12:00 – 1:00AM

Sat12:00 – 1:00AM

Week 1 FULL Incr. Incr. Incr. Incr. Incr. Incr.





Week 6 FULL Incr.

Data Retention = Recovery Window + 7 days37 = 30 + 7


Automated Backup Polling

• Recovery Appliance can copy or migrate local RMAN backupset backups

– Backup polling directory and frequency (schedule) is defined in a Protection Policy and applicable to all databases associated with the policy

• Backup polling can be effectively used to migrate existing RMAN backupset backups into the Appliance

– Extends point-to-time recovery capability from the Appliance to that of the oldest backup copied

• Avoids having to perform the initial full backup to seed the Appliance

• Mount the Network File System (NFS) directory that stores backups

Copy or Migrate Local Backups to the Recovery Appliance

Local backups in shared directory

Polling Location

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |

Adding a Protected Database To Recovery Appliance

Schedule backups using

the Oracle Suggested Strategy for Recovery Appliance

Two Steps Plus a Backup Schedule

EM - ZDLRA Protected Database Page

Click the “ADD” Button to evoke the EM wizard to:•Add one or more databases•Associate the database(s) with a Protection Policy•Define estimated storage need (Reserved Space)•Select or define the appropriate user credentials

EM - Database Backup Settings Page

• Select the appropriate Recovery Appliance from the dropdown menu

• Select the appropriate VPC user• Click check box to enable real-time redo

shipping• Define RMAN parallelism via “Tape Settings”

as an SBT library is used


Oracle DB Backups Up Directly to Oracle Cloud via RMAN All Backup Data is Encrypted for Maximum Security and Oracle Best Practices

Oracle Database

Cloud Backup Module

54

Oracle Zero Data Loss Recovery ApplianceRMAN, Oracle Secure Backup, Zero Data Loss Recovery...

Documents

Transcript of Oracle Zero Data Loss Recovery ApplianceRMAN, Oracle Secure Backup, Zero Data Loss Recovery...