Specifications
Recovering After a Failover
3. Restore the hierarchy. Use the LifeKeeper GUI to bring the resource hierarchy back in
service. See Bringing a Resource In Service for instructions.
Recovering After a Failover
After LifeKeeper performs a failover recovery from a primary server (Server A) to a backup server
(Server B), perform the following steps:
1. Review logs. When LifeKeeper on Server B performs a failover recovery from Server A,
status messages are displayed during the failover.
The exact output depends upon the configuration. Some messages on failure to mount or
unmount are expected and do not suggest failure of recovery. These messages, as well as
any errors that occur while bringing the resource in service on Server B, are logged in the
LifeKeeper log.
2. Perform maintenance. Determine and fix the cause of the failure on Server A. Server A may
need to be powered down to perform maintenance.
3. Reboot Server A, if necessary. Once maintenance is complete, reboot Server A if
necessary.
4. Start LifeKeeper, if necessary. If LifeKeeper is not running on Server A, use the command
/etc/init.d/lifekeeper start to start LifeKeeper.
5. Move application back to Server A. At a convenient time, use the LifeKeeper GUI to bring
the application back into service on Server A. See Bringing a Resource In Service for
instructions. Note that this step may be unnecessary if the application on Server A was
configured for Automatic Switchback.
Removing LifeKeeper
You can uninstall the LifeKeeper packages in a Linux environment using any rpm supported graphical
interface or through the command line. This section provides detailed instructions on uninstalling
LifeKeeper using the rpm command from the command line. Refer to the rpm(8) man page for
complete instructions on using the rpm command.
For information on rpm software, you can go to the following web site: http://www.rpm.org/.
Included below are the requirements for removing LifeKeeper software.
l Move applications. Before you remove the software, you should verify that you do not have
applications requiring LifeKeeper protection on the server. You should never remove
LifeKeeper from a server where an application resource hierarchy is in service. Removing
LifeKeeper removes all configuration data such as equivalencies, resource hierarchy
definitionsand log files. See Transferring Resource Hierarchiesfor additional information.
l Start LifeKeeper. LifeKeeper recovery kits may require LifeKeeper to be running when you
remove the recovery kit software. If it is not running, the removal process cannot remove the
resource instances from other LifeKeeper servers in the cluster which would leave the servers
in an inconsistent state.
206User Guide