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 menu, select Create Resource Hierarchy.

The Apache Web Server should not be running when you create the resource. However, if you set up the listen variable in the system configuration file, the default daemon can be allowed to run.

The Create Resource Wizard dialog box will appear with a drop down list box displaying all recognized recovery kits installed within the cluster.

  1. Select Apache Web Server and click Next.
  1. You will be prompted to enter the following information. When the Back button is active in any of the dialog boxes, you can go back to the previous dialog box. This is helpful should you encounter an error requiring you to correct previously entered information. You may click Cancel at any time to cancel the entire creation process.
Switchback Type Choose either intelligent or automatic This dictates how the Apache instance will be switched back to this server when the server comes back up after a failover. The switchback type can be changed later from the General tab of the Resource Properties dialog box.
Server Select the Server where you want to place the Apache Web Server (typically this is referred to as the primary or template server). All the servers in your cluster are included in the drop down list box.
Web Server Binary Location Select or enter the full path name (including the file name) of the httpd Apache Web Server daemon. The default is /usr/sbin/httpd.
Web Server Root Directory You must provide the full path of the Web Server Root directory; a relative path or symbolic link may not be used. The Apache Web Server configuration file is located in conf/httpd.conf relative to the Server Root.

Note: At this point, LifeKeeper will check that there is a protected IP resource available. It will also validate that you have provided valid data to create your Apache Web Server resource hierarchy. If LifeKeeper detects a problem with either of these validations, an ERROR box will appear on the screen. If the Web Server Root Directory path is valid, but there are errors with the Apache configuration itself, you may pause to correct these errors and continue with the hierarchy creation. You may even pause to create any LifeKeeper IP resources that are required.
Root Tag Select or enter the tag name given to the Web Server hierarchy. You can select the default, which is apache <root directory>, or enter your own tag name.
  1. Click Create. The Create Resource Wizard will then create your Apache resource hierarchy. LifeKeeper will validate the data entered. If LifeKeeper detects a problem, an error message will appear in the information box.
  1. An information box will appear indicating that you have successfully created a Apache resource hierarchy, and you must Extend that hierarchy to another server in your cluster in order to achieve failover protection. Click Next.
  1. Click Continue. LifeKeeper will then launch the Pre-ExtendWizard. Refer to Step 2 under Extending an Apache Resource Hierarchy (below) for details on how to extend your resource hierarchy to another server.

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


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment