Achieve high availability with DB2 9.5

High availability of data is a key requirement for important database systems. This paper summarizes the features of DB2 9.5 which provide these functions. Understand the pros and cons of different solutions, and determine which approach is best for you.

Brief introduction

High availability is a key requirement for important database applications. IBM DB2 9.5 offers many features to meet this requirement. If you are not familiar with the DB2 on a distributed platform, or have been using it for a while, you may find this set of features confusing to deal with usability. When to use which feature, what goals do you want to accomplish when using attributes?

The purpose of this article is to summarize these features and to guide you through how to build highly available database systems using the DB2 technology. In addition, discover the cost and benefits of each solution.

Before we begin, we'll define the meaning of the term high availability (HA). HA refers to the requirement to provide data when a dependent application requires data. The aim is to eliminate or avoid downtime as much as possible. One term associated with HA is disaster recovery (disaster RECOVERY,DR), and DR differs from ha in that it focuses on protecting data and preventing data loss due to catastrophic failures. This article focuses only on HA.

Terminology and client/server database schemas

Terminology and client/server database schemas

We first discuss terms and concepts that are important to understanding high availability.

A database solution consists of three pieces of software:

This article has been transferred from IBM Developerworks China

Please click here to view the full text