If you have installed your SPS environment as described in the SPS Installation Guide, you should be ready to start and configure the SPS software on each server in your cluster.

Follow the steps below which contain links to topics with additional details. Perform these tasks on each server in the cluster.

  1. Start LifeKeeper by typing the following command as root:

/etc/init.d/lifekeeper start

or

systemctl start lifekeeper

This command starts all LifeKeeper daemon processes on the server being administered if they are not currently running.

For additional information on starting and stopping LifeKeeper, see Starting LifeKeeper and Stopping LifeKeeper.

  1. Set Up TTY Communications Connections. If you plan to use a TTY communications (comm) path for a LifeKeeper heartbeat, you need to set up the physical connection for that heartbeat.
  1. Configure the GUI. There are multiple tasks involved with configuring the GUI. Start with the LifeKeeper GUI – Overview topic within Preparing to Run the GUI. Then for detailed instructions, follow the browse sequence throughout Preparing to Run the GUI.

Note: The first time you run the LifeKeeper GUI, you will see a QuickStart button which opens a window with instructions and links to help you step through the configuration of your LifeKeeper resources. Subsequently, you can access this QuickStart Configuration Assistant under the Help menu.

  1. Create Communication Paths. Before you can activate LifeKeeper protection, you must create the communications path (heartbeat) definitions within LifeKeeper.
  1. Perform any of the following optional configuration tasks:
    • If you plan to use STONITH devices in your cluster, create the scripts to control the STONITH devices and place them in the appropriate LifeKeeper events directory.
  1. SPS is now ready to protect your applications. The next step depends on whether you will be using one of the optional SPS Recovery Kits:
    • If you are using an SPS Recovery Kit, refer to the Documentation associated with the kit for instructions on creating and extending your resource hierarchies.
    • If you are using an application that does not have an associated Recovery Kit, then you have two options:
    • If it is a simple application, you should carefully plan how to create an interface between your application and LifeKeeper. You may decide to protect it using the Generic Application Recovery Kit included with the LifeKeeper core.

    • Services provided by the operating system can easily be protected by using the Quick Service Protection (QSP) Recovery Kit include with the LifeKeeper Core. However, please be aware that quickCheck will only perform a simple check of the service state.

Feedback

Thanks for your feedback.

Post your comment on this topic.

Post Comment