Вы находитесь на странице: 1из 20

<Insert Picture Here>

Oracle Disaster Recovery Solution


Data Availability & Disaster Protection
Sasa Djordjevic
Principal Sales Consultant
Agenda

• HA/DR Challenges & Oracle Database HA <Insert Picture Here>

• Data Guard Architecture & Features


• Process Architecture & Protection Modes
• Management Interface
• Best Practice & Resources
• Case Study
• Q&A

2
Common Concerns for DR Solutions
• Roadblocks for adoption of DR solutions
• Perception around the term “Disaster”
• “Disaster” often linked to destructive events that occur
infrequently, so no strong urge to implement a DR solution
 “When it happens, we will see.”
 “We do tape backups, and that should be fine, right?”

• Shortcomings of existing solutions


 Most DR solutions involve redundant systems that can’t be
utilized for productive use
 The solutions are expensive, with no immediate ROI (till
“disaster” occurs)
 “We don’t have budget for machines basically sitting idle.”

3
Market State

• Forrester Research, “Six Years After 9/11, Most Firms


Are Not Ready For Another Disaster”, Sep 11, 2007

“… IT operations professionals are crossing their fingers


and hoping a disaster won’t hit, while business executives
have no idea how vulnerable they really are to significant
losses . . .” (survey of 189 enterprises)

4
What is a Disaster?

• Well-recognized disasters such as headline-grabbing events


• Fire, earthquake, tsunami, flood, hurricane, power outages…

• And . . .more mundane events that occur more frequently


• Faulty system components – server, network, storage, software, …
• Data corruptions
• Backup/recovery of bad data
• Wrong batch job
• Bad HW/SW installations / upgrades / patching
• Operator errors
• Etc.

• Database down for critical applications, regardless of cause = disaster

5
Business Challenges

49%
System Real Application Clusters
Failures Continuous Availability for all Applications

12+3%
Unplanned Data Failures Data Guard
Downtime & Disasters Guaranteed Zero Data Loss

36%
Human Flashback Query
Errors Enable Users to Correct their Mistakes

System Dynamic Reconfiguration


Maintenance Capacity on Demand without Interruption
Planned
Downtime
Database Online Operations
Maintenance Re-
Re-orgs, Index builds, Schema Evolution

6
What is Data Guard?

Primary Site Standby Site

Data Guard
Physical
Primary or Logical
Database Standby
Database

• Data Availability & Data Protection solution for Oracle


• Any combination of physical or logical
• Use standby databases for queries, reports, test, or backups while in
standby role

7
Active Data Guard 11g
Offload Processing– Improve Primary Performance!
Read-write
Workload Real-time
Real-time Reporting
Real-time
Reporting Queries

Fast
Incremental Fast
Backups Incremental
Backups
Continuous redo
shipping, validation & apply

Production Active Standby


Database Database

• Offload read-only queries to an up-to-date physical standby


• Use fast incremental backups on a physical standby – up to 20x faster

8
Data Guard Snapshot Standby
Use Standby Databases as Test Systems

Updates Queries
Updates

redo
data

Primary Physical
PhysicalStandby
Standby
Snapshot Standby
Database Database
Database

DGMGRL> convert database <name> to snapshot standby;


DGMGRL> convert database <name> to physical standby;

9
Deploying Data Guard
Protection Mode Controls Response to Failure Events

Mode Risk of data loss Transport If no acknowledgement from standby:


Zero Data Loss
Maximum Stall primary until acknowledgement is
Protection Double Failure SYNC received from replica
Protection
Zero Data Loss Stall primary until acknowledgement is
Maximum
Availability Single Failure SYNC received or timeout threshold period expires
Protection – then resume processing

Maximum Potential for Primary never waits for standby


Performance
ASYNC acknowledgement
Minimal Data Loss

NET_TIMEOUT parameter of LOG_ARCHIVE_DEST_n

Data Guard 11g default = 30 seconds


Data Guard 10g default = 180 seconds

10
Switchover and Failover

• Switchover
• Planned role reversal
• No database reinstantiation required
• Used for maintenance of OS or hardware

• Failover
• Unplanned failure of primary
• Use Flashback Database to reinstate original primary

• Manually execute via SQL or simple GUI interface, or


• Automate failover using Data Guard Fast-Start Failover

11
Data Guard Switchover
Reduce Downtime for Planned Events

• Database Rolling Upgrades


• Scheduled power outages and site maintenance
• Data center moves
• Migrations to ASM and/or RAC
• Technology refresh – servers and storage
• Windows/Linux migrations *
• 32bit/64bit migrations*
• HP-UX/PA RISC to HP-UX/IPF migrations*
• Implement major database changes in rolling fashion
• e.g. ASSM, initrans, blocksize
* see Metalink Note 413484.1

12
Application Failover
Primary Site and Application Tier is Still Viable
Primary Site Standby Site
3 FAN breaks clients out
Application Tier - Oracle of TCP timeout,
Application Server Clusters
applications quickly
reconnect to new
primary
2 Startup trigger
is used to
relocate
Database Tier- Oracle primary
Real Application Clusters database
services
Database Data Guard
1 Data Guard
Manual or
Services Redo Transport Standby
Standby
Automatic Failover becomes
Primary Database
primary
Database
database

• MAA Best Practices for Client Failover in a Data Guard Configuration


• Demonstrations – Automatic Database, Application & Complete Site Failover

13
Complete Site Failure

Primary Site Standby


Primary Site
WAN traffic
3 WAN traffic
Automatic DNS
manager
manager
failover routes
Firewall users to new
Firewall
primary site
Application Tier - Oracle
Application Server Clusters 2 Start
mid-tier
Firewall Firewall

Database Tier- Oracle Standby


Real Application Clusters
becomes
Data Guard
Guard primary
1 Data
Automatic Failover
Redo Transport

• Chapter 4.2.1 of HA Best Practices – complete site failover


• Demonstrations – Automating Site Failover, E-Biz Suite and Siebel Apps

14
Data Guard Management Interfaces

• SQL*Plus Command Line


• Requires connecting to each database, primary and standby
• Data Guard Broker
• DGMGRL Command Line
• Monitor process runs on all databases in a Data Guard config
• Single command performs work of multiple SQL*Plus commands
• Attach to any database in a Data Guard configuration and manage
all databases as a single configuration
• Enterprise Manager Grid Control
• GUI interface that interacts with the Data Guard Broker
• No separate license purchase required

15
Enterprise Manager

16
Data Guard Best Practices

<Insert Picture Here>


 Where do I begin?
 How much bandwidth do I need?
 How will Data Guard impact performance?
 How far apart can I locate primary and standby databases?
 Physical or logical standby?
 Which management interface do I use?
 How do I protect against data corruptions?
 How much time and effort is required to failover?
 How do I failover applications as well as the database?
 How do I minimize planned downtime?

17
Resources

• Oracle Data Guard on OTN


http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardOverview.html

• Oracle HA Portal on OTN


http://www.oracle.com/technology/deploy/availability/

• Maximum Availability Architecture (MAA) white papers and demonstrations


http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm

• Oracle HA Customer Success Stories on OTN:


http://www.oracle.com/technology/deploy/availability/htdocs/HA_CaseStudies.html

• Taneja Group - New Approaches to Data Protection and DR


http://www.oracle.com/technology/deploy/availability/htdocs/analysts/tanejagroupdatabasestorage.pdf

• Enterprise Strategy Group – Data Protection and Disaster Recovery


http://www.oracle.com/technology/deploy/availability/htdocs/analysts/enterprisestrategygroupdataguard.pdf

18
Agenda

• HA/DR Challenges & Oracle Database HA <Insert Picture Here>

• Data Guard Architecture & Features


• Process Architecture & Protection Modes
• Management Interface
• Best Practice & Resources
• Case Study
• Q&A

19
20