HP Serviceguard Toolkit for Oracle Data Guard manual Setting Up The Database Server Application

Models: Serviceguard Toolkit for Oracle Data Guard

1 140
Download 140 pages 15.58 Kb
Page 89
Image 89

This is the recommended configuration. Here, the configuration and database files are on shared disks, visible to all nodes. Since the storage is shared, there is no additional work to ensure all nodes have the same configuration at any point in time.

To run MySQL in a HP Serviceguard environment:

Each node must have the same version of the MySQL Database Server software installed.

Each node that will be configured to run the package must have access to the configuration files. The most efficient way to ensure all nodes have access to the configuration files is to put the configuration files on shared storage that is accessible to all nodes.

Multiple databases configured in the same cluster will require unique configuration per database. Each DB instance will require its own volume group, set of configuration files, and copy of the toolkit customized for the unique instance.

All data files must be accessible to all nodes configured to run the package. This means that all data files will need to reside on shared storage that is accessible to all nodes.

Each package is assigned an IP address called the relocatable (or package) IP address. When the package fails over from one node to another, the following actions occur:

Primary Node

1.The package is halted on the node where it is currently running. As a result, all (package) resources are halted.

2.The relocatable IP address is removed from this node.

3.File systems are unmounted and all volume groups assigned to this package are deactivated.

Standby Node

1.Volume groups are activated and file systems are mounted.

2.The relocatable IP address is moved over to the new node.

3.All resources are started up, and the database is brought up.

4.Clients will (continue to) connect through the same (relocatable) IP address.

Multiple Database Instances

MySQL database server supports multiple DB instances running on the same node. Using the toolkit, multiple MySQL packages can be easily configured to run on the same node. One copy of the toolkit can serve exactly one package. So, to configure multiple packages, you must create separate directories, that is, one directory per package and configure each package to run a unique database instance.

Setting Up The Database Server Application

Before creating the packages, you must configure the shared storage and create the database.

1.For the volume group (VG) and file system creation, see Building an HA Cluster Configuration chapter of Managing ServiceGuard manual available at http://www.hp.com/go/ hpux-serviceguard-docs —>HP Serviceguard. Create a unique VG and filesystem on shared storage for each instance of the DB to be included in the configuration.

2.On each node, create a mount point for each filesystem. The mount point for a specified instance/package must be the same for all nodes.

The following example shows a configuration of MySQL for a filesystem named “/MySQL_1" on /dev/vg01.

1.Assuming that LVM has been set up on the shared storage, create a filesystem (for example, /MySQL_1) on the LV and mount point (for example,., /MySQL_1) on each of the nodes to mount the filesystem. For more information in creating the VG and filesystem, see to Building

Setting Up The Database Server Application 89

Page 89
Image 89
HP Serviceguard Toolkit for Oracle Data Guard manual Setting Up The Database Server Application