Você está na página 1de 43

Why should you care about Database Downtime?

Downtime Means Down Revenue Downtime Damages Relationships Downtime Disrupts Supply Chains Downtime Erodes brand and share value Downtime has Legal Repercussions

Framework for Database Availability Strategies

Severity of Database Downtime Latency of Database Recovery

Severity of Database Downtime

Severity of Database Downtime Latency of Database Recovery

Catastrophic

Unplanned

Planned

No Downtime

Latency of Database Recovery

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability

Planned

No Downtime

Continuous Availability

Latency of Database Recovery

Strategies for Database Availability

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

Online and Offline Maintenance

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

High Availability Clusters

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

Switching and Warm Standby Replication

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

Cold Standby

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

Combining Strategies for Database Availability

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

Online and Offline Maintenance

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

Online maintenance

Compressed Back-ups Quiesce Database Online index rebuild for DOL tables, Online update statistics, Online dbcc checkstorage Dynamic Reconfiguration

Dynamic Reconfiguration Solution in ASE 12.5


Self-Tuning assisted by Dynamic Re-configuration

SM

Monitoring Agent

Dynamic Reconfig params: Total memory Number of user connections Load Number of locks Number of open objects ASE Procedure Cache (absolute) Disk I/O structures Online index Dynamic Monitoring agent will assess the Re-configuration health of ASE using Systems Mgm API and automatically apply configuration changes

Quiesce Database
Primary Secondary

2:00 AM quiesce database hold; <copy database using external command>; quiesce database release 7:00 AM dump tran with standby_access 9:00 AM dump tran with standby_access 10:00 AM dump tran with standby_access Repeat each hour until activity tapers off; then lengthen intervals accordingly

2:10 AM dataserver-q .. 7:05 AM load tran; online database for standby_access 9:07 AM load tran; online database for standby_access 10:10 AM load tran; online database for standby_access

Warm Stand by Model using Quiesce Database

High Availability Clusters

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

Cluster Availability

HA System

S1

Establish Companion

S2
Node 2

Node 1
Replicate Users/Logins

Disk

Disk

Local or Shared dual ported Storage

Cluster Availability Fail Over


HA System

Transparent Fail Over

S1

S1

S2
Node 2

Disk

Disk

Local or Shared dual ported Storage

Cluster Availability Fail Back


HA System

Transparent Fail Back

S1

S2
Node 2

Disk

Disk

Local or Shared dual ported Storage

Cluster Availability

Fail Back
HA System
Prepare

Transparent Fail Back

S1

Failback

S2
Node 2

Disk

Disk

Local or Shared dual ported Storage

Cluster Availability

Fail Back
HA System

S1

Establish Companion

S2
Node 2

Node 1

Disk

Disk

Local or Shared dual ported Storage

Summary

Dynamic Re-Configuration Online maintenance Quiesce Database Sybase HA addressed Planned and unplanned downtime No client disconnects during HA failover No data loss Transparent client fail over

Warm Standby Replication and Switching

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

Warm Standby Replication Value Proposition


The only solution that addresses all areas of HA Key Benefits Works across the LAN and WAN - no geographic restrictions Database Integrity is guaranteed Redundant hardware can be leveraged for DSS or load balancing Automates the failover switch

Disaster Recovery Solution


Physical separation needed for Disasters/Site failure No geographic limitation Database integrity maintained Automatic switch of DBs regardless of locale Leverage secondary resources for DSS

Chicago Operations

ASE PRIMARY DATACENTER London Operations

ASE SECONDARY DATACENTER

Unplanned Downtime Solution


Automated Failover and synchronization of client connections Synchronized Failback with no loss of data
ASE PRIMARY DATACENTER

ASE SECONDARY DATACENTER DATACENTER SECONDARY

Planned Downtime Solution


Provide secondary copy for:

maintenance
critical tasks, such as hardware/software upgrades
ASE PRIMARY DATACENTER

ASE SECONDARY DATACENTER DATACENTER SECONDARY

Warm Standby with Open Switch

OpenSwitch

Active DB

Replication Server

Standby DB

Queue

Warm Standby with Open Switch

OpenSwitch

Active DB

Replication Server

Standby DB

Queue

Warm Standby with Open Switch

OpenSwitch

Active DB

Replication Server

Standby DB

Queue

Warm Standby with Open Switch

OpenSwitch

Active DB

Replication Server

Standby DB

New Active

Queue

Warm Standby with Open Switch

OpenSwitch

Active DB

Replication Server

Standby DB

New Active

Queue

Warm Standby with Open Switch

OpenSwitch

Active DB

Replication Server

Standby DB

New Active

Queue

Warm Standby with Open Switch

OpenSwitch

Active DB

Replication Server

Standby DB

New Active

Queue

Warm Standby with Open Switch

OpenSwitch

Active DB

Replication Server

Standby DB

Queue

Warm Standby Replication Summary


The only solution that covers all areas of HA

No geographic limitation
Database integrity maintained Leverage secondary resources for DSS Automatic Failover and synchronized Failback

Case StudyMajor Credit Card Issuer


Obvious: purchase approval application needs HA Not so obvious: the call center needs DB availability Customers seek immediate assistance when: requesting new cards, increasing credit limits, and applying for loans. Database availability required for service rep to handle request Also, requires data replicated from back- & front-office systems Sybase Replication Server synchs customer data Collects data from heterogeneous sources Stores customer info in Sybase ASE, warm standby for HA Achieved 99.95% database availability Which contributed to customer acquisition and retention

Case StudyOnline Bond Trading Firm


Incentive to avoid costs of Database Downtime Hundreds of millions in lost sales opportunities each hour Key benefit to customers is liquidity, which requires HA Frequent downtime is a violation of regulations Started with clean slate, but chose Sybase ASE Reasonable licenses, ease of finding Sybase DBAs Leading database for both financial apps and availability Sybase HA Option for fastest failover possible Building the business vs Protecting the Business For some companies, its time for HA phase

Conclusion
Data access is key to any availability strategy Databases require availability, same as network, hardware, etc Nows the time to re-evaluate your database availability As you do more business online, your need for HA increases Customers, partners, investors--expectations for HA grow daily Some companies have availability plans that are years old Rationalizing Return on Investment (ROI) Database availability solutions are more affordable than ever Avoid cost of business losses due to database downtime Reap benefits of business stability with database availability