OracleWorld 2003 - Data Guard

1
(No Transcript)
2
Oracle Data Guard Maximum Data Protection at
Minimum Cost
Session Id 40056

• Ashish RaySenior Product Manager
• Oracle Corporation

Darl KuhnSenior DBA, Staff Engineer Sun
Microsystems
3
Agenda

• Oracle Data Guard a Quick Introduction
• Data Guard Features in Oracle Database 10g
• Customer Success Story Sun Microsystems
• Summary Q/A

4
What is Oracle Data Guard?

• Oracles disaster recovery solution for Oracle
  data
• Feature of Oracle Database Enterprise Edition
• Automates the creation and maintenance of one or
  more transactionally consistent copies (standby)
  of the production (or primary) database
• If the primary database becomes unavailable
  (disasters, maintenance), a standby database can
  be activated and assume the primary role

5
Oracle Data Guard Focus

• Data Failures Site Disasters

• Data Protection
• Data Availability
• Data Recovery

Data is the core asset of the enterprise!

• Also addresses human errors planned maintenances

6
Oracle Data Guard Architecture
Physical Standby Database
Sync or Async Redo Shipping
Backup
Redo Apply
Logical Standby Database
Transform Redo to SQL
Open for Reports
SQLApply
Additional Indexes MVs
7
Data Guard Redo Apply
Physical Standby Database
Primary Database
Data Guard Broker
Redo Apply
Backup
Network
Redo Shipment
Standby Redo Logs

• 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 for
  reporting/queries
• Can also be used for backups, offloading
  production database

8
Data Guard SQL Apply
Additional Indexes Materialized Views
Logical Standby Database
Primary Database
Data Guard Broker
Transform Redo to SQL and Apply
ContinuouslyOpen for Reports
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

9
Agenda

• Oracle Data Guard a Quick Introduction
• Data Guard Features in Oracle Database 10g
• Customer Success Story Sun Microsystems
• Summary Q/A

10
Oracle Data Guard 10g Objectives

• Establish Data Guard as an extremely
• easy-to-use
• low-cost
• comprehensive
• reliable
• Disaster Recovery solution for enterprise data

11
Overview of Objectives

• Ease of use simplified SQL, easy to create,
  manage and administer standby databases,
  simplified GUI focused on best practices
• Low cost businesses can leverage existing
  resources to implement Data Guard, zero
  integration costs
• Comprehensive feature-rich and flexible
• Reliable a rock-solid solution for protection
  of mission critical business data

12
Data Guard 10g New Features

• General new features
• Real Time Apply
• Flashback Database Integration
• SQL Apply new features
• Zero Downtime Instantiation
• Rolling Upgrades
• Additional Datatypes
• Data Guard Broker Enterprise Manager new
  features
• RAC integration
• Simplified browser-based interface focused on
  best practices

13
Real Time Apply

• Redo data is applied to the standby database as
  soon as it is received from the primary database
• In Oracle9i Data Guard this apply has to wait
  till an archivelog is created on the standby
  database
• For Redo Apply
• ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
  USING CURRENT LOGFILE
• For SQL Apply
• ALTER DATABASE START LOGICAL STANDBY APPLY
  IMMEDIATE
• When real time apply is enabled, RECOVERY_MODE
  column in VARCHIVE_DEST_STATUS displays MANAGED
  REAL TIME APPLY

14
Real Time Apply Architecture
An up-to-date Physical/Logical Standby Database
Oracle Net
Transactions
MRP/ LSP
LGWR
RFS
Standby Redo Logs
Online Redo Logs
Real Time Apply
Primary Database
ARCH
ARCH
Archived Redo Logs
Archived Redo Logs
15
Real Time Apply Benefits

• Standby databases now more closely synchronized
  with the primary
• More up-to-date, real-time reporting
• Faster switchover and failover times
• Reduces planned and unplanned downtime
• Better Recovery Time Objective (RTO) for DR

16
Existing Site Recovery Tradeoffs
Reporting on delayed data
Primary Database
Standby Database
Redo Shipment
Delayed Apply

• Log apply may be delayed to protect from user
  errors but
• Switchover/Failover gets delayed
• Reports run on old data
• After failing over to standby, production DB must
  be rebuilt

17
Flashback Database

• A new strategy for point in time recovery
• Eliminate the need to restore a whole database
  backup
• Integrated seamlessly with RMAN
• Think of it as a continuous backup
• Restores just changed blocks
• Its fast - recover in minutes, not hours
• Its easy - single command restore

RMANgt FLASHBACK DATABASE TIMESTAMP
to_timestamp ('2003-08-15 160000',
'YYYY-MM-DD HH24MISS')
18
Enhanced DR with Flashback Database
Real TimeReporting
Redo Shipment
Flashback Log
Flashback Log
Primary No reinstantiation after failover!

• Flashback DB removes the need to delay
  application of logs
• Flashback DB removes the need to reinstantiate
  primary after failover
• Real-time apply enables real-time reporting on
  standby

19
SQL Apply Zero Downtime Instantiation

• Logical standby database can now be created from
  an online backup of the primary database, without
  shutting down or quiescing the primary database
• No shutdown implies no downtime of production
  system
• No quiesce implies no wait on quiesce and no
  dependence on Resource Manager

20
Rolling Upgrades
21
SQL Apply Additional Data Types

• SQL Apply now supports the following additional
  data types
• Multi-byte CLOB
• NCLOB
• LONG
• LONG RAW
• BINARY_FLOAT
• BINARY_DOUBLE
• IOT-s (without overflows and without LOB columns)
• Allows logical standby databases to recover and
  protect a wider variety of data, thus increasing
  the overall database protection and recovery
  options for Data Guard

22
Enterprise Manager New Features

• Streamlined browser-based interface that enables
  complete standby database lifecycle management
• Focus on
• Ease of use
• Management based on best practices
• Pre-built integration with other HA features

23
RAC Support Broker

• Now possible to use the Broker to create and
  manage configurations that contain RAC primary
  and RAC standby databases
• Data Guard Broker interfaces with Oracle
  Clusterware such that it has control over
  critical operations during specific Data Guard
  state transitions
• Switchovers, failovers, protection mode changes,
  state changes

24
(No Transcript)
25
(No Transcript)
26
Example Ease of Use

• Switchover using Enterprise Manager is now
  literally two mouse clicks

27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
Agenda

• Oracle Data Guard a Quick Introduction
• Data Guard Features in Oracle Database 10g
• Customer Success Story Sun Microsystems
• Summary Q/A

34
Case Study

• Oracle Data Guard at Sun Microsystems
• Darl Kuhn
• Senior DBA, Staff Engineer
• Business decision considerations
• Architecture
• Implementation
• Features we use

35
Project Requirements

• Patch and Knowledge databases for Sun Support
  Services
• 7x24 High Availability
• Minimize scheduled downtime
• Minimize unscheduled downtime
• Disaster Recovery (DR) protection
• Do more with less resources
• Minimize costs
• Minimize complexity

36
Solutions We Investigated

• Backup the database, restore from tape
• Operating System failover
• Remote Mirroring
• Quests SharePlex
• Oracle Advanced Replication (OAR)
• Oracle Real Application Clusters (RAC)
• Oracle Data Guard (Standby)

37
We Chose Data Guard

• 7x24 DR protection
• Simple to implement
• Requires DBA with BR skills
• Didnt need special System Administration skills
  or consultants
• Low maintenance (do more w/less DBAs)
• No extra licensing (built into Oracle9i)

38
Implementation Decisions

• Which data protection mode?
• Maximum Protection
• Maximum Availability
• Maximum Performance
• We chose Maximum Performance
• Two identical servers
• Directory structures the same
• Database name the same
• Introduce a delay in application of redo

39
Maximum Performance
Primary Database Production Site
Standby Database Server

• .

Copied Archive Redo
Copied Archive Redo
Users
Remote File Server (RFS)
Fetch ArchiveLog (FAL)
Oracle Net
Primary Database
LGWR
Managed Recovery Process (MRP)
ARCn
On-line Redo
Online Redo
Standby Database
Local Archive Redo
Local Archive Redo
40
Database Architecture

• 50M archive redo logs
• 1 Gig of redo per day
• Primary in Colorado
• Standbys in North Carolina, Holland and Singapore
• Database size currently 60 Gig
• Hardware Sun 6500, 280R, 4500
• Storage T3 partner pair fiber channel

41
Implementation of Physical Standby

• 1. Ensure primary database is in archive log mode
• Note In Data Guard 10g, you also need to
  implement a password file for both Primary and
  Standby
• 2. Take backup of primary database datafiles
  options
• RMAN
• Hot
• Cold
• Do not backup controlfiles or online redo logs

42
Using RMAN to Build Standby

• On Primary
• RMANgt backup database
• Copy backup pieces to Standby
• Create a Standby controlfile and copy to Standby
• Then on Standby
• SQLgt startup nomount
• SQLgt alter database mount standby database
• RMANgt restore database
• SQLgt alter database recover managed standby
  database disconnect

43
Implementation of Physical Standby

• 3. Copy backup datafiles to standby server
• 4. Create a standby controlfile
• 5. Copy the standby controlfile to standby server
• 6. Configure primary init.ora or spfile
• 7. Copy primary database init.ora file to standby
  server and make modifications for standby
  database
• 8. Configure Oracle Net

44
Implementation of Physical Standby

• 9. Startup and mount standby database
• SQLgt startup nomount
• SQLgt alter database mount standby database
• Startup syntax is simplified in Oracle Data Guard
  10g
• SQLgt startup mount
• In Data Guard 10g, the startup will put the
  Standby into read-only mode
• SQLgt startup

45
Implementation of Physical Standby

• 10. Enable managed recovery mode on Standby
• SQLgt alter database recover managed standby
  database disconnect
• Troubleshooting
• tail f alert_BRDSTN.log
• Almost all problems encountered were
• TNS set up incorrectly
• Initialization parameters set wrong

46
Preventing User Errors

• Logs copied but not applied for 60 minutes
• Used to have to manually script this
• SQLgt alter database recover managed standby
  database delay 60 disconnect
• To disable delay
• SQLgt alter database recover managed standby
  database nodelay

47
Use of Read-Only Standby

• 7x24 business requirement for knowledge reporting
• Primary database batch loaded once a day
• How do we ensure that there will always be a
  database available?
• Create two (or more) Standby databases
• Shut down one at a time, apply redo

48
Use of Read-Only Standby
Primary Database Production Site
Two Separate Read-Only Standby Database Servers

• .

Oracle Net
l3srv1
Daily Batch Load
Standby 1 brdstn
Reports
Primary Database
ARCn
l3srv2
Standby 2 brdstn
49
Use of Read-Only Standby

• Let Oracle Net connection figure out which
  read-only physical Standby database available
• brdstn
• (DESCRIPTION
• (LOAD_BALANCEon) (ADDRESS(PROTOCOLtcp)(
  HOSTl3srv1)(PORT1521))
• (ADDRESS(PROTOCOLtcp)(HOSTl3srv2)(PORT1521))
  
• (CONNECT_DATA(SERVICE_NAMEbrdstn))
• )

50
Disaster Happens

• Havent had a complete disaster yet
• We have had bad hardware cause failovers
• We were able to easily failover to Standby
• SQLgt alter database activate standby database
• In Data Guard 9i, we keep 9i Primary init.ora on
  Standby
• In Data Guard 10g, VALID_FOR eliminates this need

51
Archive Gap Management

• This is one of our favorite Data Guard 9i
  features
• Addresses critical issues such as
• What if network or server is down?
• After failure resolution, how is the standby
  caught up?
• In Oracle8i Standby Database, we would manually
  fix
• In Oracle9i
• Data Guard has automatic methods for gap
  resolution
• Fetch Archive Log (FAL) processes
• In our experience, very reliable

52
Propagation of Datafile Operations

• Another task automated in Data Guard 9i
• In Oracle8i Standby Database, add/drop
  tablespace/datafile commands not automatically
  propagated
• DBA had to intervene
• In Oracle9i Data Guard
• Fully automated
• In Standby initialization file
• standby_file_management auto

53
Propagation of Datafile Operations

• Example
• SQLgt drop tablespace HRM_SALA including contents
  and datafiles
• On standby the tablespace HRM_SALA will be
  automatically dropped and all datafiles will be
  deleted from disk
• Note If you rename a datafile, DBA must intervene

54
Oracle Data Guard 10g Beta Feedback

• Logical Standby easier to setup
• Simplified SQL syntax
• More helpful, feature-rich initialization
  parameters

55
Agenda

• Oracle Data Guard a Quick Introduction
• Data Guard Features in Oracle Database 10g
• Customer Success Story Sun Microsystems
• Summary Q/A

56
Maximum Availability Architecture

• Best Practices on
• General Data Guard configuration
• Redo data transport mechanisms
• Protection modes
• Switchover/Failover
• Media recovery
• SQL Apply configuration
• Network configuration
• Integration with other HA technologies

• White papers1
• MAA detailed
• Media Recovery
• Site/Network configuration
• Fast-Start Checkpointing
• SQL Apply Best Practices
• Role Management

1. Ref. http//otn.oracle.com/deploy/availability/htd
   ocs/maa.htm for latest updates

57
Data Guard Customers
Transportation
Telecom
Financial/ Insurance
Utilities
Government
Manufacturing
Health Care
Other Industries
e-Commerce
58
Customer Testimonials

• Data Guard automates disaster-recovery
  procedures and reduces Fidelity's exposure to
  data loss by an order of magnitude compared to
  previous approaches.
• Jonathan Schapiro
• Vice President
• Data Architecture Services
• Global Equity Trading Technology

59
Customer Testimonials

• We needed to consider the safe-keeping of our
  data, but we also needed to look at cost. Oracle
  Data Guard provides everything for a high
  availability solution at a lower cost than other
  alternatives
• Ann Collins
• Technical Director

60
Customer Testimonials

• We don't have to baby-sit it it just works!
• Darl Kuhn
• Senior DBA Staff Engineer
• Database Services
• Sun Services Global Engineering

61
Why Oracle Data Guard?

• Disaster Recovery High Availability
• Easy failover/switchover between primary and
  standby databases

• Complete data protection
• Enables zero data loss, safeguard against data
  corruptions

• Efficient utilization of system resources
• Standby databases can be used for reporting,
  backups, queries

• Balance data availability against performance
• Flexible data protection/synchronization modes

• Automatic resynchronization after restoration of
  network connectivity
• Automatic archive gap detection and resolution
  with no manual intervention

• Centralized and simple management
• Push-button graphical interface for management
  and monitoring

62
Of Course
Complete, out-of-the-box integration with Oracle
database, at no extra cost!
63
Resources

• Maximum Availability Architecture white papers
  http//otn.oracle.com/deploy/availability/htdocs/m
  aa.htm
• HA Portal on OTN http//otn.oracle.com/deploy/ava
  ilability
• Data Guard home page on OTN http//otn.oracle.com
  /deploy/availability/htdocs/odg_overview.html
• Oracle Consulting Services http//otn.oracle.com/
  consulting

64
Next StepsHigh Availability Sessions from Oracle
Wednesday in Moscone Room 304
Tuesday in Moscone Room 304

• 1100 AM
• How Oracle Database 10g Revolutionizes
  Availability and Enables the Grid
• 330 PM
• Oracle Recovery Manager (RMAN) 10g Reloaded
• 500 PM
• Proven Techniques for Maximizing Availability

• 830 AM
• Oracle Database 10g - RMAN and ATA Storage in
  Action
•  
• 1100 AM
• Oracle Data Guard Maximum Data Protection at
  Minimum Cost
•  
• 100 PM
• Oracle Database 10g Time Navigation Human-Error
  Correction
•  
• 430 PM
• Data Guard SQL Apply Back to the Future

For More Info On Oracle HA Go To
http//otn.oracle.com/deploy/availability/
65
Next StepsHigh Availability Sessions from Oracle
Thursday
830 AM in Moscone Room 304 Oracle Database 10g
Data Warehouse Backup and Recovery Automatic,
Simple, Reliable 830 AM in Moscone Room
104 Building RAC Clusters over InfiniBand
For More Info On Oracle HA Go To
http//otn.oracle.com/deploy/availability/
66
Reminder please complete the OracleWorld
online session surveyThank you.
67
A
68
(No Transcript)