DB2 Version 10.1 for Linux, UNIX, and Windows

Configuring a GDPC environment

The topics in this section detail how to configure a geographically dispersed DB2® pureScale® cluster (GDPC) environment. Configuring a GDPC environment involves getting the cluster installed and running, setting up GPFS™ replication, creating a database, and configuring the cluster for high availability.

Before you begin

Note: IBM support for a geographically dispersed DB2 pureScale cluster (GDPC) implementation requires engagement of IBM Lab Services for separately charged initial installation services. Contact your IBM sales representative for details.

Ensure that these prerequisites are met:

Three sites to communicate with each other through reliable TCP/IP links.
All DB2 pureScale installation prerequisites have been satisfied across all hosts to be used in the cluster.
Two sites are connected via a WAN or dark fiber with distance range extenders, with a single high speed interconnect subnet configured across the sites.
The two sites each have a local SAN controller, and the SAN is zoned such that LUNs used for the DB2 pureScale instance are directly accessible from both sites. A one-to-one mapping between LUNs is required across sites so each LUN on the first site has a corresponding equally sized LUN on the second site.

About this task

For this example, the following hardware configurations are used:

There are three sites. In this example, the three sites are as follows:

Site A: Hosts hostA1, hostA2, hostA3
Site B: Hosts hostB1, hostB2, hostB3
Site C: Host T

Equal sized LUNs have been prosvisioned on storage at 2 sites, and all LUNs are accessible by all hosts at the sites.

LUNs on disks located at Site A are:

/dev/hdiskA1
/dev/hdiskA2
/dev/hdiskA3
/dev/hdiskA4
/dev/hdiskA5
/dev/hdiskA6
/dev/hdiskA7

Where /dev/hdiskA1 is used for the instance shared file system; /dev/hdiskA2 is used for the database log file system; and /dev/hdiskA3, /dev/hdiskA4, /dev/hdiskA5, /dev/hdiskA6, and /dev/hdiskA7 are used for the database data file system.

LUNs on disks located at Site B are:

/dev/hdiskB1
/dev/hdiskB2
/dev/hdiskB3
/dev/hdiskB4
/dev/hdiskB5
/dev/hdiskB6
/dev/hdiskB7

Where /dev/hdiskB1 is used for the instance shared file system; /dev/hdiskB2 is used for the database log file system; and /dev/hdiskB3, /dev/hdiskB4, /dev/hdiskB5, /dev/hdiskB6, and /dev/hdiskB7 are used for the database data file system.

LUNs on disks located at Site C are as follows. These disks can be as small as 50 MB volumes.
```
/dev/hdiskC1
/dev/hdiskC2
/dev/hdiskC3
```

In this scenario, the geographically dispersed DB2 pureScale cluster (GDPC) is setup as:

Database MYDB is to be created on instance db2inst1.
db2inst1 has three file systems:
- logfs for transaction logs and database metadata for MYDB.
- datafs for database containers for MYDB.
- db2fs1 for the shared file system for the instance

The command syntax in the examples use this format:

uid@host> command

Where uid is the user ID that executes the command, host is where the command should be executed, and command is the command to execute.

Procedure

What to do next

Once you have configured your GDPC environment, validate the GDPC through testing.