LKCLI provides functions that can be performed with the LifeKeeper GUI through the command line interface. LifeKeeper provides export/import of communication paths and resource information which the GUI does not provide. Export/import functionality enables duplicating a created system and easy deployment from a testing environment to a production environment.
LKCLI is supported in the following environments:
- OS – All operating systems supported by LifeKeeper are supported.
- Application Recovery Kits – Except for those subject to the restrictions described below, only environments configured with the Application Recovery Kits in the “Supported ARK List” are supported. If unsupported ARK resources have been created on a node, the environment is not supported.
If you want to perform command line operations in an unsupported environment, please consider using the Command Line Interface.
For Single Server Protection for Linux, LKCLI is not available or supported with the following functions:
- Common option
- [ --remote <str> ]
- Communication path operations
- lkcli commpath …
- lkcli import (not available only for the creation of communication paths)
- Extending/unextending or switching resources
- lkcli resource extend
- lkcli resource unextend
- lkcli resource eqv
- lkcli resource reorder-priority
- lkcli resource switchback
- lkcli server …
- Application Recovery Kits
- SIOS DataKeeper for Linux
- Recovery Kit for EC2
- LVM Recovery Kit
- MD Recovery Kit
- Route53 Recovery Kit
- SAP Recovery Kit
- SAP HANA Recovery Kit
- VMDK as Shared Storage Recovery Kit
- Multipath Recovery Kit（DMMP / HDLM / PPATH / NECSPS）
- lkcli export or lkcli resource info command of the IP Recovery Kit
If processing stops with the lkcli export command or lkcli resource, ensure that the hostname is configured properly.
You can use LKCLI with Single Server Protection for Linux in the same way as the LifeKeeper for Linux. See LKCLI (LifeKeeper Command Line Interface) for details.