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.

  1. Perform maintenance. Determine and fix the cause of the failure on Server A. Server A may need to be powered down to perform maintenance.
  1. Reboot Server A, if necessary. Once maintenance is complete, reboot Server A if necessary.
  1. Start LifeKeeper, if necessary. If LifeKeeper is not running on Server A, use the command /etc/init.d/lifekeeper start (or, systemctl start lifekeeper) to start LifeKeeper.
  1. 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.


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