You are here: User Guide > Using LifeKeeper Linux > Advanced Tasks > Interface Issues for Common Application Types

Interface Issues For Common Application Types

The actions you perform to provide an interface between your application and LifeKeeper depend upon the type and complexity of your application.  For example:

File System Service.  The LifeKeeper GUI provides menu-based configuration of file system hierarchies.  LifeKeeper also provides recovery scripts that mount, unmount and clean up Linux file systems on shared SCSI disk configurations.

DBMS Application.  The LifeKeeper product family provides optional recovery kit packages for the RDBMS applications such as MySQL, Oracle, DB2 and Informix.  These recovery packages deliver menu options in the LifeKeeper GUI for configuring a database instance into LifeKeeper protection.  These packages also provide default restore and remove scripts that use the associated database initialization commands.

Simple Application.  For configurations that depend upon a single file system or disk device, the LifeKeeper GUI provides menus for hierarchy creation functions.  You need only provide remove and restore scripts for the application itself.

Complex Application.  For more complex configurations where no associated LifeKeeper application recovery kit package exists, you can use the LifeKeeper Configuration Database Interface (LCDI) commands.  You would use the commands, for example, to provide an interface for a custom relational database and for applications that depend upon more than one file system or disk partition.  You would also need to provide the necessary restore and remove scripts.  For further discussion, see LCDI Command Interface

© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.