With a typical installation, LifeKeeper is started automatically when the server is booted. Your applications are brought up in a protected state.
When LifeKeeper starts, it also starts the LifeKeeper GUI Server. The LifeKeeper GUI client is launched from a web browser or from the Start->All Programs->SIOS->LifeKeeper->LifeKeeper (Admin Only), and is described in detail in the LifeKeeper GUI section of SIOS Protection Suite for Windows Technical Documentation.
Starting and Stopping LifeKeeper Processes
Because LifeKeeper is started automatically when the server is booted, you should not normally need to start/stop LifeKeeper. In the rare event that you need to start or stop LifeKeeper manually, you can do so in one of two ways:
Services MMC Snap-In
You can stop and start LifeKeeper services using the Services MMC snap-in under Administrative Tasks.
LifeKeeper consists of two services:
- LifeKeeper External Interfaces
Generally, these two services should be stopped and started together. However, since LifeKeeper External Interfaces is a dependency of the LifeKeeper service, stopping it will also stop the LifeKeeper service. Likewise, it must be started before the LifeKeeper service can be started.
When stopping LifeKeeper, there are a number of related services that must be stopped. This process can take several seconds, although the Services tool does not reflect exactly when all the services are stopped. Using the command line to enter $LKROOT\bin\lkstop will show the services as they are being stopped, and when completed, the message “LIFEKEEPER NOW STOPPED” will display as confirmation.