LifeKeeper Configuration Tasks

Performing a Manual Switchover from the GUI

You can initiate a manual switchover from the LifeKeeper GUI by selecting
Edit, then Resource, then finally In Service from the drop down menu. For
example, an in service request executed on a backup server causes the
application hierarchy to be placed in service on the backup server and taken
out of service on the primary server. At this point, the original backup server
is now the primary server and original primary server has now become the
backup server.
If you execute the Out of Service request, the application is taken out of
service without bringing it in service on the other server.
Recovery Operations
When the primary server fails, the SAMS Recovery Kit software performs
the following tasks:
Brings the switchable IP address into service on the backup server by
bringing in service a logical interface on one of that server’s physical
network interfaces
Mounts the file system(s) on the shared disk on that server
Starts the daemon processes related to SAMS
Since session context is lost following recovery, after the recovery, SMTP,
IMAP, and POP clients must reconnect using exactly the same procedures
they used to connect originally.
Note: During a LifeKeeper initiated switchover/failover and recovery of a
SAMS resource hierarchy, it is possible that mail sent to the protected
domains maybe temporarily deferred. The mail messages will be resent at
the next available interval following the application restore.
LifeKeeper for Linux 33