Implement High Availability for Mission Critical Databases

Where “good enough” availability just isn’t good enough, ensure business requirements will be met before investing in people, processes, and technology for true high availability.


Please note that the content on this page is retired. This content is not maintained and may contain information or links that are out of date.

Implementing database high availability without a plan can result in:

  • Unnecessary complexity
  • Wasted investment
  • Continued downtime from human error

Upfront planning leads to:

  • Improved availability
  • Investment aligned with business requirements
  • Strengthened processes and controls

Book Your Workshop

Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.

Module 1: Create the Business Impact Analysis

The Purpose

  • Identify required recovery time objective (RTO) and recovery point objective (RPO) for critical databases.

Key Benefits Achieved

  • Complete a Business Impact Analysis.

Activities: Outputs:
1.1 Review critical applications and dependencies.
  • Business Impact Analysis
1.2 Define an objective scoring scale to indicate different levels of impact.
1.3 Estimate the impact of downtime.
1.4 Determine desired RTO/RPO objectives based on business impact.

Module 2: Determine Gaps Between Current and Desired Capabilities

The Purpose

  • Identify gaps between current and desired capabilities.

Key Benefits Achieved

  • Complete a response and recovery workflow.

Activities: Outputs:
2.1 Conduct a tabletop exercise to determine current recovery procedures.
  • Incident response and recovery workflow
2.2 Identify gaps between current and desired capabilities.
2.3 Identify where the database is a roadblock to system recovery.

Module 3: Review Availability Solutions

The Purpose

  • Review possible technological solutions.
  • Shortlist solutions and architectures based on cost, effort to implement, and benefit.

Key Benefits Achieved

  • Technological high availability options defined and assessed.

Activities: Outputs:
3.1 Review options to improve database availability.
  • High Availability Solution Evaluation
3.2 For mission critical databases, review high availability solutions.
3.3 Assess solutions based on cost, effort, and benefit.

Module 4: Strengthen Processes to Support Availability

The Purpose

  • Address people and process requirements for database high availability.
  • Ensure the required stakeholders are consulted on proposed process changes.
  • Communicate the value proposition to stakeholders.

Key Benefits Achieved

  • Create the action plan to develop people and processes to support databases high availability.
  • Develop the business case for a high availability deployment.

Activities: Outputs:
4.1 Identify process and control changes required ahead of a high availability deployment
  • Action Item Checklist
4.2 Review the 6-year TCO for a high availability deployment.
4.3 Develop a business case for the proposed high availability solution.
  • Business Case
Visit our Exponential IT Research Center
Over 100 analysts waiting to take your call right now: 1-519-432-3550 x2019