The rule of determining the target IP address corresponding to a Recovery Kit for Route 53™ resource varies by configuration.
Configuration with no descendant IP resource of a Route53 resource
The target IP address is the IP address of the network adapter that is selected at the time of creation/extension of the Route53 resource. Typically, this configuration is used with an application recovery kit that does not require IP resources (ex. PostgreSQL Server Recovery Kit).
Configuration with multiple descendant IP resources of a Route53 resource
The target IP address is the one of the IP addresses associated with the descendant IP resources restored on the local computer. Typically, this configuration is used with an application recovery kit that requires IP resources (ex. Oracle Recovery Kit). Here is a configuration example of a 2 nodes cluster.
- step1: Add the secondary IP addresses to each EC2 instance of the cluster node.
- step2: Create one IP resource on the primary node and another on the secondary node. Assign the IP addresses created at step1 to the IP resources. At the time of extension of each IP resource, target restore mode has to be disabled.
- step3: Set each IP resource to the “IN SERVICE” state on the primary node. Set priority as shown below.
- step4: Create a Route53 resource and add its dependencies to the IP resources created at step 2. Note the priorities of the Route53 resource and its descendant IP resources must be identical.
Thanks for your feedback.
Post your comment on this topic.