EC2™ Local Recovery and Configuration

Local Recovery Scenario (Backend Cluster):

When a failure of the protected Route Table is detected by Recovery Kit for EC2™, the resulting failure triggers the execution of the EC2™ local recovery script. The local recovery gathers specified IP resource entries in all Route Tables and changes the entries’ Target to the ENI on the active server. It also disables source/destination checks for the network interface. If the local recovery attempt fails, LifeKeeper will perform a failover of the EC2™ resource and all dependent resources to a standby server. See the Principles of Operation section for the configuration of this scenario.

*Note: Since the recovery kit will protect the configuration of the route table once the corresponding EC2™ resource gets created, the route table should not be modified manually.

The following example shows a typical scenario of the local recovery: When the recovery kit detects a wrong target setting of IP routing in the route table, the local recovery replaces the target to the ENI on the active server. During this process nothing will be changed regarding the entry of 10.1.0.20/32 on the Route Table B.

Route Table A – Before

Route Table A – After

Route Table B – Before

Route Table B – After

Elastic IP scenario (Frontend Cluster):

When a failure of the protected Elastic IP is detected by Recovery Kit for EC2™, the resulting failure triggers the execution of the EC2™ local recovery script. The local recovery allocates the Elastic IP to the ENI on the active node. If the local recovery attempt fails, LifeKeeper will perform a failover of the EC2™ resource and all dependent resources to a standby server. See the Principles of Operation section for the configuration of this scenario.