Tag line, tag line

Database Disaster Recovery

Tom Hamilton, NetApp Americas Channel Database CSE

Agenda
Definitions and Issues Oracle Data Guard Microsoft SQL Server Mirroring IBM DB2 HADR NetApp SnapMirror Demo

2008 NetApp. All rights reserved.

Customer Challenges
Internal Data Center Failures
Power Failure IT Hardware Failure Network Failure IT Software Failure Human Error Flood Hurricane
12% 10% 7% 6% 4% 3% 2% 1% 16% 16% 21% 31% 42%

External Data Center Failures

Fire Winter Storm Terrorism Earthquake Tornado Chemical Spill

Source: Forester / Disaster Recovery Journal Global Disaster Recovery Preparedness Online Survey, Oct, 2007
2008 NetApp. All rights reserved. NetApp Confidential - Limited Use 3

What is Data Guard?

Data Availability & Data Protection solution for Oracle Automates the creation and maintenance of one or more synchronized copies of the primary database If the primary database becomes unavailable, a standby database can easily assume the primary role Standby databases can be used for queries, reporting, testing, or backups while in standby role Feature of Oracle Database Enterprise Edition (EE)

2008 NetApp. All rights reserved.

Oracle Data Guard Architecture

Dallas
Sync or Async Redo Shipping

Physical Standby
Redo Apply

Open R/O

Production Database
Network

Backup

Broker

DIGITAL DATA STORAGE

DIGITAL DATA STORAGE

Chicago

Transform Redo to SQL

Logical Standby

Open R/W

SQL Apply

Boston

2008 NetApp. All rights reserved.

Data Guard Process Architecture

Redo Transport & Apply
Transactions

Oracle Net

Physical/Logical Standby Database

MRP - physical LSP - logical

Redo buffer

sync async LNS RFS

MRP LSP

LGWR

Primary Database

Online Redo Logs

Standby Redo Logs async

Transform Redo to SQL for Logical Standby

ARCH ARCH

Queries Reports Testing Backups

Archived Redo Logs

Archived Redo Logs

2008 NetApp. All rights reserved.

Data Guard Redo Apply

Open Read-Only Primary Database Data Guard Broker Redo Apply Network Redo Shipment Standby Redo Logs Backup
DIGITAL DATA STORAGE

Physical Standby Database

Physical Standby Database is a block-for-block copy of the primary database Uses the database recovery functionality to apply changes Can be opened in read-only mode while apply is active for reporting/queries Can also be used for backups, offloading production database

2008 NetApp. All rights reserved.

Data Guard SQL Apply

Additional Indexes & Materialized Views

Primary Database

Data Guard Broker

Logical Standby Database Transform Redo to SQL and Apply

Open Read - Write

Network Redo Shipment Standby Redo Logs

Logical Standby Database is an open, independent, active database

Contains the same logical information (rows) as the production database Physical organization and structure can be very different Can host multiple schemas

Can be queried for reports while logs are being applied via SQL Can create additional indexes and materialized views for better query performance

2008 NetApp. All rights reserved.

Redo Apply or SQL Apply?

Redo Apply
Maintains a physical, blockfor-block copy of the primary Can be open for read-only queries At role transition, offers the assurance that the standby database chosen to be the new primary has not been changed compared to the old primary Can be used for backups Faster, since it bypasses the SQL transformation layer

SQL Apply
Maintains a logical, transaction-for-transaction copy of the primary Allows creation of additional objects, modification of objects Possible to skip apply on certain objects Can be used as a good reporting solution supports real-time reporting in 10g Has datatype restrictions

2008 NetApp. All rights reserved.

Flexible Data Protection Modes

Protection Mode
Maximum Protection

Risk of Data Loss

Zero Data Loss Double Failure Protection Zero Data Loss Single Failure Protection Potential for Minimal Data Loss

Redo Shipment
Synchronous redo shipping Synchronous redo shipping Asynchronous redo shipping

Maximum Availability

Maximum Performance

Balance cost, availability, performance, and transaction protection

2008 NetApp. All rights reserved.

Switchover and Failover

Primary and Standby role transitions Switchover Planned role reversal No database reinstantiation required Used for maintenance of OS or hardware Failover Unplanned failure (e.g. disasters) of primary Use Flashback Database to reinstante original primary Manually execute via simple SQL / GUI interface, or Automate failover using Data Guard Fast-Start Failover
2008 NetApp. All rights reserved.

Data Guard Management Interfaces

SQL*Plus Command Line Requires connecting to each database, primary and standby Data Guard Broker DGMGRL Command Line DMON process running on all databases in a Data Guard config Simpler, single statement commands that perform the work of multiple SQL*Plus commands Attach to any member of a Data Guard configuration and manage all members as a single configuration Enterprise Manager Grid Control GUI interface that interacts with the Data Guard Broker No separate license purchase required

2008 NetApp. All rights reserved.

 2008 NetApp. All rights reserved.

Snapshot Standby
Increase ROI

Updates

Queries Updates

Primary Database

Physical Standby Snapshot Database Database

Preserves zero data loss continuous redo transport while open read-write Truly leverages standby database and DR hardware for multiple purposes Similar to storage snapshots, but provides DR at the same time and uses single copy of storage

2008 NetApp. All rights reserved.

Traditional Physical Standby Databases

Investment in Disaster Recovery only

Real-time Queries

Production Database

Standby Database

Applications, backups, reports run on production only

2008 NetApp. All rights reserved.

Active Data Guard 11g

Increase ROI - Real-time Query

Real-time Query Queries

Real-time

Continuous Redo Shipment and Apply

Production Database

Physical Standby Database

Offload read-only queries to physical standby Offload fast incremental backups to physical standby

2008 NetApp. All rights reserved.

Active Data Guard Benefits

Increase ROI - Invest in Improving Quality of Service

Physical standby in recovery All read activity on production

Simultaneous read & recovery Shift read-only workload to standby

Disaster protection only

Standby systems rarely used Complex replication used to create reporting replica

Performance protection
Regularly used for production Simple replication with very high performance and no restrictions

2008 NetApp. All rights reserved.

Microsoft High Availability

Failover clustering Database mirroring Log shipping Replication

2008 NetApp. All rights reserved.

Microsoft SQL Server Database Mirroring

Benefits
Increased data protection Increased database availability Database availability during upgrades

How SQL Server Mirroring Works

Operating modes
High safety mode High performance mode

2008 NetApp. All rights reserved.

SQL Server Database Mirroring

High safety mode

2008 NetApp. All rights reserved.

SQL Server Database Mirroring

High performance mode

2008 NetApp. All rights reserved.

SQL Server Database Mirroring

Transaction safety and operating modes
Full (Synchronous) Off (Asynchronous)

Role Switching
Automatic failover Manual failover Forced service

2008 NetApp. All rights reserved.

What is HADR?
Disaster recovery solution for IBMs DB2 Automates the creation and maintenance of a synchronized copy of the primary database If the primary database becomes unavailable, a standby database can easily assume the primary role Client automatic failover

2008 NetApp. All rights reserved.

IBM DB2 HADR

Why HADR
Ultra fast failover Easy to implement Rolling upgrades Transparent failover and failback Negligible impact on performance

2008 NetApp. All rights reserved.

IBM DB2 HADR

Overview
2008 NetApp. All rights reserved.

HADR Topology

2008 NetApp. All rights reserved.

HADR Topology
Synchronization modes
Synchronous Near-synchronous Asynchronous

2008 NetApp. All rights reserved.

SnapMirror Our Flagship DR

Technology
Value Proposition
Primary Data Center

Simple, flexible and cost-effective

LAN

Benefits
Simple
Simple configuration Integrated with SnapManager Simplified failover/failback - MultiStore

FAS

FAS

Flexible
SnapMirror DR Site Address a broad range of DR requirements Operate with FC or IP network Mirror to/from any NetApp system Multi-hop, cascading

Cost-effective
FAS NearStore

Mirror to inexpensive targets Supports all SLAs Bandwidth efficient with BLI changes Leverage low cost IP networks Backup data can be made writeable

2008 NetApp. All rights reserved.

SnapMirror Flexibility
Synchronous SnapMirror
1
Every Write

Zero data loss Distance limited Performance impact Small data loss No distance limit No performance impact

Semi-Synchronous SnapMirror
1
Every Write

Asynchronous SnapMirror
1 A 2
2008 NetApp. All rights reserved.
1 2

3
Changed blocks Set intervals

Data loss > 1 minute No distance limit No performance impact

SnapMirror Deployment Options

Multiple hops
Cascading Many-to-one

Sync

Async

Asymmetric replication
FAS

NearStore

Heterogeneous replication with V-Series

Enterprise Storage Array
2008 NetApp. All rights reserved.

V-Series

FAS

NetApp Solution:

Rapid Recovery for Business Apps

Replication
Primary Data Center DR or 2nd Datacenter

SnapManager coordinates consistent snapshots SnapMirror replicates snapshot copies ensure restartable copies

Oracle Server SnapManager SnapDrive Failover Server

Mirror database and logs at different frequencies

FAS System

Database

FAS System

Logs

SnapMirror

2008 NetApp. All rights reserved.

Application Mirroring Vs. SnapMirror

Data transfers Licenses Server-server vs. controller-controller Reversible sync Failover Database only vs. everything Go for win-win

2008 NetApp. All rights reserved.