The LifeKeeper for Linux Sybase ASE Recovery Kit provides a mechanism for protecting Sybase ASE Server instances within LifeKeeper. The Sybase ASE software, LifeKeeper Core and Sybase ASE Recovery Kit are installed on two or more servers in a cluster. Once the Sybase ASE Server instance is under LifeKeeper protection, clients connect to the database using a LifeKeeper protected IP address. The LifeKeeper protected IP address must be created separately prior to the creation of the Sybase ASE resource hierarchy. The Sybase ASE resource hierarchy creation will create the dependency between the parent Sybase ASE resource instance, and the child IP address resource. In the event that the Sybase ASE Server instance fails, LifeKeeper will first attempt to recover it on the local server. If the local recovery fails, then LifeKeeper will fail over to a backup server.
Sybase ASE Resource Hierarchy
The following example shows an example Sybase ASE resource hierarchy:
The dependencies in the above example correspond to the following protected resources:
|LKIP.EXAMPLE.COM||Protects the switchable IP address used for client connections|
|sybase/config||Protects the file system containing the Sybase Adaptive Server, Monitor Server, and Backup Server configuration files|
|sybase/master||Protects the Sybase ASE master device|
|sybase/shm||Protects the Sybase Adaptive Server, and Monitor Server shared memory path|
|sybase/sybsystemdb||Protects the Sybase ASE sybsystemdb device|
|sybase/sybsystemprocs||Protects the Sybase ASE sybsystemprocs device|
In the event of failover, LifeKeeper will bring the file system, IP address and database resources (including all the resource dependencies) in service on a backup server. Clients will be disconnected, and will need to re-connect to the server. Any SQL statement that has not been committed will need to be re-entered.