Recovering from a LifeKeeper Server Failure

If any server in your LifeKeeper cluster experiences a failure that causes re-installation of the operating system (and thus LifeKeeper), you will have to re-extend the resource hierarchies from each server in the cluster. If any server in the cluster has a shared equivalency relationship with the re-installed server, however, LifeKeeper will not allow you to extend the existing resource hierarchy to the re-installed server. LifeKeeper will also not allow you to unextend the hierarchy from the re-installed server because the hierarchy does not really exist on the server that was re-installed.

Suggested Action:

1. On each server where the resource hierarchies are configured, use the eqv_list command to obtain a list of all the shared equivalencies (see LCDI-relationship for details).

The example below shows the command and resulting output for the IP resource iptag on server1 and server2 where server2 is the server that was re-installed and server1 has the hierarchy configured:

eqv_list -f:

server1:iptag:server2:iptag:SHARED:1:10

2. On each server where the resource hierarchies are configured, use eqv_remove to manually remove the equivalency relationship for each resource in the hierarchy (see LCDI-relationship for details).

For example, execute the following command on server1 using the example from step 1 above:

eqv_remove -t iptag -S server2 -e SHARED

3. In clusters with more than two servers, steps 1-2 should be repeated on each server in the cluster where equivalency relationships for these resource hierarchies are defined.

4. Finally, extend each resource hierarchy from the server where the resource hierarchy is in-service to the re-installed server using the GUI.