The Recovery Kit for SAP ASE provides a mechanism for protecting SAP ASE Server instances within LifeKeeper. The SAP ASE software, LifeKeeper Core and Recovery Kit for SAP ASE are installed on two or more servers in a cluster. Once the SAP 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 SAP ASE resource hierarchy. The SAP ASE resource hierarchy creation will create the dependency between the parent SAP ASE resource instance, and the child IP address resource. In the event that the SAP 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.
SAP ASE Resource Hierarchy
The following example shows an example SAP 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 SAP Adaptive Server, Monitor Server, and Backup Server configuration files |
| sybase/master | Protects the SAP ASE master device |
| sybase/shm | Protects the SAP Adaptive Server, and Monitor Server shared memory path |
| sybase/sybsystemdb | Protects the SAP ASE sybsystemdb device |
| sybase/sybsystemprocs | Protects the SAP 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.
Post your comment on this topic.