Warm-standby and disaster recovery

1
(No Transcript)
2
(No Transcript)
3
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

4
Framework for Database Availability Strategies
Severity of Database Downtime
Latency of Database Recovery
5
Severity of Database Downtime
Catastrophic
Unplanned
Severity of Database Downtime
Planned
No Downtime
Latency of Database Recovery
6
Latency of Database Recovery
DisasterRecovery
Catastrophic
HighAvailability
Unplanned
Severity of Database Downtime
Planned
No Downtime
ContinuousAvailability
Latency of Database Recovery
7
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
8
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
9
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
10
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
11
Cold Standby
Switchingand WarmStandbyReplication
ColdStandby
DisasterRecovery
Catastrophic
HighAvailabilityClusters
HighAvailability
Unplanned
Severity of Database Downtime
OfflineMaintenance
Planned
OnlineMaintenance
No Downtime
ContinuousAvailability
Latency of Database Recovery
12
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
13
(No Transcript)
14
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
15
Online maintenance

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

16
Dynamic Reconfiguration Solution in ASE 12.5
Self-Tuning assisted by Dynamic Re-configuration

• 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

Load
SM
ASE
DynamicRe-configuration
Monitoring Agent
17
Quiesce Database
Primary
Secondary
200 AMquiesce database holdltcopy database
usingexternal commandgtquiesce database
release 700 AMdump tran with
standby_access 900 AMdump tran with
standby_access 1000 AMdump tran with
standby_access Repeat each houruntil activity
tapers off then lengthen intervals accordingly
210 AMdataserver-q .. 705 AMload
tranonline database for standby_access 907
AMload tranonline database for standby_access
1010 AMload tranonline database for
standby_access
Warm Stand by Model using Quiesce Database
18
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
19
Cluster Availability
HA System
Establish
S2
S1
Companion
Node 2
Node 1

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

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

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

Disk
Disk
Local or Shared dual ported Storage
23
Cluster Availability
HA System
Establish
S2
S1
Companion
Node 2
Node 1

Disk
Disk
Local or Shared dual ported Storage
24
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

25
(No Transcript)
26
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
27
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

28
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
29
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
30
Planned Downtime Solution

• Provide secondary copy for
• maintenance
• critical tasks, such as hardware/software
  upgrades

ASE
PRIMARY DATACENTER
ASE
SECONDARY DATACENTER
SECONDARY DATACENTER
31
Warm Standby with Open Switch
OpenSwitch
Replication Server
Active DB
Standby DB
Queue
32
Warm Standby with Open Switch
OpenSwitch
Replication Server
Active DB
Standby DB
Queue
33
Warm Standby with Open Switch
OpenSwitch
Replication Server
Active DB
Standby DB
Queue
34
Warm Standby with Open Switch
OpenSwitch
Replication Server
Active DB
Standby DB
New Active
Queue
35
Warm Standby with Open Switch
OpenSwitch
Replication Server
Active DB
Standby DB
New Active
Queue
36
Warm Standby with Open Switch
OpenSwitch
Replication Server
Active DB
Standby DB
New Active
Queue
37
Warm Standby with Open Switch
OpenSwitch
Replication Server
Active DB
Standby DB
New Active
Queue
38
Warm Standby with Open Switch
OpenSwitch
Replication Server
Active DB
Standby DB
Queue
39
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

40
(No Transcript)
41
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

42
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

43
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