Because LifeKeeper is typically started automatically after installation and each time the server is booted, you should not normally need to start/stop LifeKeeper. (The only exception is if you chose to do a Custom installation and opted not to start LifeKeeper at that time.)
In the event that you need to start or stop LifeKeeper manually, you should do so using the Services tool under Administrative Tasks in the Windows Control Panel.
LifeKeeper consists of two services:
LifeKeeper
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.
Select LifeKeeper and click Start. This will automatically start the LifeKeeper External Interfaces service.
In the Services tool, select LifeKeeper External Interfaces and click Stop. This will stop both services. Note that the length of time that it takes to stop LifeKeeper will vary depending upon the hierarchies currently configured although the Services tool shows the services as stopped immediately.
Using the command line to enter $LKROOT\bin\lkstop will more accurately show the services being stopped, and it will confirm with the message "LIFEKEEPER NOW STOPPED".
Note: Stopping LifeKeeper takes all protected hierarchies out of service. This means that any protected applications will not be accessible.
© 2017 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.