Business Continuity - Databases for SAP applications on Amazon
High Availability
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Business Continuity

We recommend that you architect your business-critical applications to be fault tolerant. Depending on your availability requirements, there are different ways to achieve this. In this section we will discuss how you can set up highly available IBM Db2 for SAP applications.

High Availability

High availability for IBM Db2 database on Amazon can be configured with IBM HADR with Pacemaker:

One of the requirements for automated failover with IBM Db2 HADR on Amazon is Pacemaker. Implementing a Pacemaker cluster in Amazon is similar to deploying it in an on-premises setting. On Amazon, you need to deploy the cluster nodes in separate subnets, and we recommend that you have these subnets in different AZs.

Figure 2 provides an overview of architecture for IBM Db2 HADR with Pacemaker on Amazon. This includes the following components:

  • A VPC configured with two private subnets across two AZs. This provides the network infrastructure for your IBM Db2 deployment.

  • In private subnet, Linux servers are configured with Pacemaker to protect the IBM Db2 database.

  • Overlay IP address (similar to a virtual IP address) that is relocatable between the primary and standby Db2 databases.

IBM Db2 HADR with Pacemaker

Figure 2 - IBM Db2 HADR with Pacemaker