Oracle Disaster Recovery Solution Data Availability & Disaster Protection Sa Sasa sa Dj Djor ordje djevi vic cConsultant Principal Sales
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 .” (survey of 189 enterprises)
4
What is a Disaster? • Well-recognized disasters such as headline-grabbing events • Fire, earthquake, tsunami, flood, hurricane, power outages…
mundane events that occur more more frequently • And . . .more mundane • Faulty system system compone components nts – server, netw network, ork, 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 Continuous Availability for all Applications
12+3%
Unplanned Downtime
Data Failures & Disasters
Data Guard Guaranteed Zero Data Loss
36%
Planned Downtime
Flashback Query
Human Errors
Enable Users to Correct their Mistakes
System
Dynamic Reconfiguration
Maintenance
Capacity on Demand without Interruption
Database Maintenance
Online Operations Re- orgs, orgs, Index builds, Schema Evolution
6
What is Data Guard? Primary Site
Standby Site
Data Guard Primary Database
Physical or Logical Standby Database
• Data Availability & Data Protection solution for Oracle • Any combination of physical physical or logical • Use standby databases for queries, reports, test, or backups while in standby role
7
Active Data Guard 11g 11g Offloa Offload d Processing– Processing– Improv Improve e Primary Primary Performa Performance! nce! Read-write Workload Real-time
Real-time Reporting Real-time
Reporting
Queries Fast Incremental Backups
Fast Incremental Backups
Continuous redo shipping, validation & apply
Production Database
Active Standby Database
• Offload read-only queries to an up-to-date physical standby • Use fast inc incremen remental tal backu backups ps on a physical st standby andby – up to 20x faste faster r 8
Data Guard Snapshot Standby Use Standby Databases as Test Systems
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 Maximum Protection Maximum
Risk of data loss
Transport
If no acknowledgement from standby:
SYNC
Stall primary until acknowledgement is received from replica
Zero Data Loss Double Failure Protection Zero Data Loss
Availability
Single Failure Protection
Maximum Performance
Potential for Minimal Data Loss
SYNC ASYNC
Stall primary until acknowledgement is received or timeout threshold period expires – then resume processing Primary never waits for standby acknowledgement
NET_TIMEOU NET_TIMEOUT T parameter parameter of LOG_ARCHIVE_DES LOG_ARCHIVE_DEST_n T_n Data Guard 11g 11g default default = 30 seconds Data Guard 10g 10g default 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 using Data Guard Fas Fast-Start t-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 y refr refresh esh – serve servers rs an and d storage storage • Technolog • 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 Application Tier Tier - Oracle Application Server Server Clusters
FAN breaks clients out of TCP timeout, applications quickly reconnect to new primary 2
Data Database base TierTier- Ora Oracle cle Real Application Clusters
Database Services Primary Database
Data Guard 1 Data Guard Manual or Redo Transport Automatic Failover
Startup trigger is used to relocate primary database services
Standby Standby becomes Database primary database
• MAA Best Practices for Client Failover in a Data Guard Configuration • Demo Demonstra nstrations tions – Autom Automatic atic Databa Database, se, Applica Application tion & Complete Complete Site Site Failover Failover 13
Complete Site Failure Standby Site Primary Site
Primary Site WAN traffic manager
3
Firewall
Application Tier - Oracle Application Server Clusters
Automatic DNS WAN traffic manager failover routes users to new Firewall primary site 2
Start mid-tier Firewall
Firewall
Database base TierTier- Ora Oracle cle Data Real Application Clusters
1
Data Guard Guard Data Automatic Failover Redo Transport
Standby becomes primary
• Chapter 4.2.1 4.2.1 of HA Best Practices Practices – complete site site failover 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 manage ge • Attach to any database in a Data Guard configuration and mana 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
• Taneja Group - New Appr Approaches oaches to Da Data ta P Protec rotection tion and DR http://www.oracle.com/technology/deploy/availability/htdocs/analysts/tanejagroupdatabasestorage.pdf
• Enterprise Strategy Group – Data Pr Protection otection and Dis Disaster aster R Recovery ecovery 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