Maintaining a LifeKeeper Single Server Protection Protected System

When performing system or application maintenance on a LifeKeeper Single Server Protection-protected server, you should either stop LifeKeeper Single Server Protection monitoring or place the protected resources into maintenance mode. This will stop LifeKeeper Single Server Protection from interfering with the system and application maintenance tasks by disabling both application recovery and triggering of VMware HA failure events.

To stop and restart LifeKeeper Single Server Protection:

1. Stop LifeKeeper Single Server Protection. Use the command /etc/init.d/lifekeeper stop-daemons to stop LifeKeeper Single Server Protection. The resources will remain running but will no longer be monitored by LifeKeeper Single Server Protection. Any failure will have to be handled manually.

2. Perform maintenance. Perform the necessary maintenance.

3. Start LifeKeeper Single Server Protection. Use the command /etc/init.d/lifekeeper start to start LifeKeeper Single Server Protection. Your resources are now protected.

Alternatively, place the resources in maintenance (a.k.a., notification only) mode:

1. Place all resources in maintenance mode. Use the command /opt/LifeKeeper/bin/lkpolicy -s NotificationOnly --On. Resources will not be recovered and VMware HA failure events will not be triggered.

2. Perform maintenance. Perform the necessary maintenance.

3. Turn off maintenance mode. Use the command /opt/LifeKeeper/bin/lkpolicy -s NotificationOnly --Off. Resources are now protected.