Creating a MySQL Resource Hierarchy

!IMPORTANT:

In a LifeKeeper cluster environment where the MySQL data directory (datadir) files are on a shared/replicated disk, you must make sure that the shared file system is mounted on the primary/template server. If the file system resource is created first, the shared file system MUST be mounted on the same mount point on each server. It is also important to remember that a working communication path (i.e. heartbeat) is required before you can create your resource. The MySQL data directory can exist on shared, replicated or network attached storage.

Replicated file system resources using DataKeeper or DRBD must be created before creating the MySQL resource. File systems on other storage types will automatically be created during MySQL hierarchy creation.

To create a resource instance from the primary server, you should complete the following steps:

1. From the LifeKeeper GUI menu, select Edit, then Server. From the drop‑down menu, select Create Resource Hierarchy.

If you wish to change a selection you have already entered or encounter an error message during any step in the creation of your MySQL resource hierarchy, you will generally be able to back up and change your selection or make corrections (assuming the Back button is enabled).

*Important: The MySQL database server daemon (mysqld) for the MySQL instance you want to protect must be running when you create the resource.

A dialog box will appear with a drop‑down menu listing all recognized Recovery Kits installed within the cluster. Select MySQL Database from the drop‑down menu.

Click Next.

If you click the Cancel button at any time during the sequence of creating your hierarchy, LifeKeeper will cancel the entire creation process.

2. Select the Switchback Type. This dictates how the MySQL instance will be switched back to this server when it comes back into service after a failover to the backup server. You can choose either intelligent or automatic. Intelligent switchback requires administrative intervention to switch the instance back to the primary/original server. Automatic switchback means the switchback will occur as soon as the primary server comes back on line and reestablishes LifeKeeper communication paths.

The switchback type can be changed later, if desired, from the General tab of the Resource Properties dialog box.

Click Next.

3. Select the Server where you want to place the MySQL database instance (typically this is referred to as the primary or template server). All the servers in your cluster are included in the drop‑down menu.

Click Next to proceed to the next dialog box.

4. Select or enter the Location of my.cnf. This is the full path name (excluding the file name) where the MySQL configuration file (my.cnf) is located.

Click Next to proceed to the next dialog box.

5. Select the Protection Instance Number if you have a mysqld_multi style my.cnf file. If you are using a more traditional style my.cnf file, you will not see this screen.

6. Select or enter the* Location of MySQL executables location*. This is the full path name of the binaries used to start and monitor the MySQL database server daemon.

*Note: At this point, LifeKeeper will validate that you have provided valid data to create your MySQL resource hierarchy. If LifeKeeper detects a problem with either of this validation, an ERROR will appear on the screen. If the directory paths are valid, but there are errors with the MySQL configuration itself, you may pause to correct these errors and continue with the hierarchy creation.

Click Next to proceed to the next dialog box.

7. Select or enter the Database Tag. This is a tag name given to the MySQL hierarchy. You can select the default or enter your own tag name.

When you click Create, the Create Resource Wizard will create your MySQL resource.

*Note: The MySQL resource hierarchy should be created successfully at this point.

8. Another information box will appear explaining that you have successfully created an MySQL resource hierarchy, and you must Extend that hierarchy to another server in your cluster in order to place it under LifeKeeper protection.

When you click Continue, LifeKeeper will launch the Pre-Extend Wizard that is explained in the next section.

If you click Cancel now, a dialog box will appear warning you that you will need to come back and extend your MySQL resource hierarchy to another server at some other time to put it under LifeKeeper protection.

9. Click Done to exit.