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. 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.

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.

IP resource 10.1.0.10
ENI on Active Node eni-01234567

Route Table A – Before

Destination
Target
10.1.0.10/32 eni-89abcdef
10.0.0.0/16 local

Route Table A – After

Destination
Target
10.1.0.10/32 eni-01234567
10.0.0.0/16 local





Route Table B – Before

Destination
Target
10.1.0.10/32 eni-89abcdef
10.1.0.20/32 eni-89abcdef
10.0.0.0/16 local

Route Table B – After

Destination
Target
10.1.0.10/32 eni-01234567
10.1.0.20/32 eni-89abcdef
10.0.0.0/16 local

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.

フィードバック

お役に立ちましたか?

はい いいえ
お役に立ちましたか
理由をお聞かせください
フィードバックありがとうございました

このトピックへフィードバック

送信