Setup Procedure for Connecting to a LifeKeeper Cluster using AWS

In this section, a general procedure to setup the environment shown as the figure below.

Preparations

Create an environment that satisfies Requirements. Please install LifeKeeper on each instance and create a communication path between Node1 and Node2 (or Node2’).
Please confirm that you can access from other VPC environments to the ENI’s real IP address connected to Node1/Node2 (or Node2’).

Configuration not requiring IP resources

The steps to create a configuration to protect the services of an Application Recovery Kit (e.g. PostgreSQL Server Recovery Kit) that does not require IP resources are as follows.

1. Create a Route 53 Resource
   1. Create a Route 53 resource on Node1. The IP address set for the network adapter selected when creating the resource will be the IP address to which clients will connect when Node1 is active.
   2. Extend the Route 53 resource to Node2 (or Node2’). The IP address set for the network adapter selected when expanding the resource will be the IP address to which clients connect when Node2 (or Node2’) is active.
2. Create a resource for the protected service
   Create a resource for the service to be protected on Node1 and extend it to Node2 (or Node2’).
3. Create resource dependencies
   Create resource dependencies so that the resource of the service protected by the parent resource and the child resource are Route 53 resources.

Configuration requiring IP resources

The steps to create a configuration to protect the services of an Application Recovery Kit (e.g. Oracle Recovery Kit) that requires IP resources are as follows.

1. Creating an IP resource 1
   1. Add the secondary private IP address to the ENI on Node1. When Node1 is active, this IP address will be the IP address to which the client connects.
   2. Create an IP resource on Node1. The IP address specified when creating the resource should be the secondary private IP address added in the previous step.
   3. Extend the IP resource to Node2 (or Node2’). Set the target’s Restore Mode to disabled.
2. Creating an IP resource ２
   1. Add the secondary private IP address to the ENI on Node2 (or Node2’). When Node2 (or Node2’) is active, this IP address will be the IP address to which the client connects.
   2. Create an IP resource on Node2 (or Node2’). The IP address specified when creating the resource should be the secondary private IP address added in the previous step.
   3. Extend the IP resource to Node1. Set the target’s Restore Mode to disabled.
3. Switching over resources
   Switch over the IP resource created on Node2 (or Node2’) to Node1.
4. Changing priorities
   Change the priority of the IP resource created on Node2 (or Node2’) to match the IP resource created on Node1.
   
5. Creating a Route 53 resource
   Create a Route 53 resource on Node1 and extend it to Node2 (or Node2’).
6. Creating resource dependencies
   Create resource dependencies so that the parent resource is a Route 53 resource and the child resources are two IP resources.
   
7. Creating resources for services to be protected
   Create a resource for the service to be protected on Node1 and extend it to Node2 (or Node2’).
8. Creating resource dependencies
   Create resource dependencies so that the parent resource is the resource of the service to be protected and the child resources is the Route 53 resource.