The commands will be in: /opt/LifeKeeper/bin
To place this in your path, execute: ‘. /etc/default/LifeKeeper’
/etc/init.d/lifekeeper start- Start LifeKeeper core
/etc/init.d/lifekeeper stop- Stop LifeKeeper core
/etc/init.d/lifekeeper stop-daemons- Stop LifeKeeper core but do not stop the protected resource
/etc/init.d/lifekeeper stop-failover- Stop LifeKeeper Core and initiate failover
/etc/init.d/lifekeeper stop-nofailover- Stop LifeKeeper core but do not allow failover
lktest- Checks to see if LifeKeeper is configured and running properlyOptions:
none
lkGUIserver- Start and stop the LifeKeeper GUI daemon processesOptions:
start
stop
restart
lkGUIapp- Starts the LifeKeeper Java applicationOptions:
none
lcdstatus- Display status of LifeKeeper resources, comm paths, etc.Options:
-d - <node to run command on>
-q- short reports
lcdsync- Writes LifeKeeper configuration information from memory to diskOptions:
-d- <other node to run it on>
lcdrcp- Transfer files from one LifeKeeper node to another via the comm. pathOptions:
lcdrcp <file names> {dest:ofile | dest:odir}
lcdremexec- Execute the given command on the given LifeKeeper nodeOptions:
-d <node to run command on> <command>
lcdrecover- Checks and sets resource hierarchy instance settingsOptions:
see documentation
perform_action- Performs a given action on a given resource.Can be used to switch a given hierarchy to another node.
Options:
-a <action name>
-t <tag name>Examples:
perform_action -a restore -t $LKTag- bring tier into service
perform_action -a remove -t $LKTag- take tier out of service
lkchkconf : Performs the following checks to verify /etc/default/LifeKeeper settings.
Checks that the running system is actually using the current settings found in /etc/default/LifeKeeper.
If the current setting of LifeKeeper is different from the /etc/default/LifeKeeper setting, an error message is output to inform the user.
Checks for any inconsistencies between the resource health check time interval(LKCHECKINTERVAL) and the timeout value of each ARK.
An error message will be logged if the timeout value of each ARK is longer than the resource health check time interval (LKCHECKINTERVAL).
Options:
None
© 2017 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.