1 / 43

Why should you care about Database Downtime?

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.

rocio
Download Presentation

Why should you care about Database Downtime?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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

  2. Framework for Database Availability Strategies Severity of Database Downtime Latency of Database Recovery

  3. Severity of Database Downtime Catastrophic Unplanned Severity of Database Downtime Planned No Downtime Latency of Database Recovery

  4. Latency of Database Recovery DisasterRecovery Catastrophic HighAvailability Unplanned Severity of Database Downtime Planned No Downtime ContinuousAvailability Latency of Database Recovery

  5. Strategies for Database Availability Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

  6. Online and Offline Maintenance Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

  7. High Availability Clusters Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

  8. Switching and Warm Standby Replication Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

  9. Cold Standby Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

  10. Combining Strategies for Database Availability Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

  11. Online and Offline Maintenance Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

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

  13. Dynamic Reconfig params: Total memory Number of user connections Number of locks Number of open objects Procedure Cache (absolute) Disk I/O structures Online index Monitoring agent will assess the health of ASE using Systems Mgm API and automatically apply configuration changes Dynamic Reconfiguration Solution in ASE 12.5 Self-Tuning assisted by Dynamic Re-configuration Load SM ASE DynamicRe-configuration Monitoring Agent

  14. Quiesce Database Secondary Primary 2:00 AMquiesce database hold;<copy database usingexternal command>;quiesce database release 7:00 AMdump tran with standby_access 9:00 AMdump tran with standby_access 10:00 AMdump tran with standby_access Repeat each houruntil activity tapers off; then lengthen intervals accordingly 2:10 AMdataserver-q .. 7:05 AMload tran;online database for standby_access 9:07 AMload tran;online database for standby_access 10:10 AMload tran;online database for standby_access Warm Stand by Model using Quiesce Database

  15. High Availability Clusters Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

  16. Replicate Users/Logins Cluster Availability HA System Establish S2 S1 Companion Node 2 Node 1 Disk Disk Local or Shared dual ported Storage

  17. Fail Over Cluster Availability HA System Transparent Fail Over S1 S1 S2 S1 Node 2 Disk Disk Local or Shared dual ported Storage

  18. Fail Back Cluster Availability HA System Transparent Fail Back S1 S2 Node 2 Disk Disk Local or Shared dual ported Storage

  19. Fail Back PrepareFailback Cluster Availability HA System Transparent Fail Back S1 S2 Node 2 Disk Disk Local or Shared dual ported Storage

  20. Fail Back Cluster Availability HA System Establish S2 S1 Companion Node 2 Node 1 Disk Disk Local or Shared dual ported Storage

  21. 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

  22. Warm Standby Replication and Switching Switchingand WarmStandbyReplication ColdStandby DisasterRecovery Catastrophic HighAvailabilityClusters HighAvailability Unplanned Severity of Database Downtime OfflineMaintenance Planned OnlineMaintenance No Downtime ContinuousAvailability Latency of Database Recovery

  23. 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

  24. Disaster Recovery Solution • Physical separation needed for Disasters/Site failure • No geographic limitation • Database integrity maintained • Automatic switch of DB’s regardless of locale • Leverage secondary resources for DSS Chicago Operations ASE PRIMARY DATACENTER London Operations ASE SECONDARY DATACENTER

  25. Unplanned Downtime Solution • Automated Failover and synchronization of client connections • Synchronized Failback with no loss of data ASE PRIMARY DATACENTER ASE SECONDARY DATACENTER SECONDARY DATACENTER

  26. Planned Downtime Solution • Provide secondary copy for: • maintenance • critical tasks, such as hardware/software upgrades ASE PRIMARY DATACENTER ASE SECONDARY DATACENTER SECONDARY DATACENTER

  27. Warm Standby with Open Switch OpenSwitch Replication Server Active DB Standby DB Queue

  28. Warm Standby with Open Switch OpenSwitch Replication Server Active DB Standby DB Queue

  29. Warm Standby with Open Switch OpenSwitch Replication Server Active DB Standby DB Queue

  30. Warm Standby with Open Switch OpenSwitch Replication Server Active DB Standby DB New Active Queue

  31. Warm Standby with Open Switch OpenSwitch Replication Server Active DB Standby DB New Active Queue

  32. Warm Standby with Open Switch OpenSwitch Replication Server Active DB Standby DB New Active Queue

  33. Warm Standby with Open Switch OpenSwitch Replication Server Active DB Standby DB New Active Queue

  34. Warm Standby with Open Switch OpenSwitch Replication Server Active DB Standby DB Queue

  35. 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

  36. Case Study—Major 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

  37. Case Study—Online 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, it’s time for HA phase

  38. Conclusion • Data access is key to any availability strategy • Databases require availability, same as network, hardware, etc • Now’s 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

More Related