After you have created a hierarchy, you must extend that hierarchy to another server in the cluster. There are three possible scenarios to extend your resource instance from the template (primary) server to a target server.
- Continue from creating the resource into extending that resource to another server.
- Enter the Extend Resource Hierarchy task from the edit menu.
- Right click on an unextended hierarchy in either the left or right hand pane.
Each scenario takes you through the same dialog boxes (with a few exceptions, detailed below).
- If you are entering the Extend wizard from the LifeKeeper for Windows GUI menu select Edit, then Resource. From the dropdown menu select Extend Resource Hierarchy. This will launch the Extend Resource Hierarchy wizard.
- Select backup server.
- An information box will appear explaining that LifeKeeper for Windows has successfully checked your environment and that all the requirements for extending this Route53 resource have been met. If there were some requirements that have not been met, you would not be allowed to select the Next button and the Back button would be enabled. If you click Back, you can make changes to your resource extension according to any error messages that may appear in the information box. If you click Cancel now, you will need to manually extend your Route53 resource hierarchy to another server to put it under LifeKeeper for Windows protection. When you click Next, LifeKeeper will launch you into the Extend Resource Hierarchy configuration task.
- The Extend Resource Hierarchy configuration task will prompt you to enter the following information.
|Select a network adapter from the network adapters list. The selected network adapter is used, in case no descendant IP resources exist, to obtain the target IP address to set to Route53 A record.
|Route53 Resource Tag
| Select or enter the Route53 Resource Tag. This is the resource tag name to be used by the Route53 resource being extended to the target server.
Note: The field is not editable.
| Select or enter the Target Priority. This is the priority for the new extended Route53 hierarchy relative to equivalent hierarchies on other servers. Any unused priority value from 1 to 999 is valid, indicating a server’s priority in the cascading failover sequence for the resource. A lower number means a higher priority (1=highest).
Note: LifeKeeper for Windows assigns the number “1” to the server on which the hierarchy is created by default. The priorities do not need to be consecutive and no two servers can have the same priority for a given resource.
- An information box will appear verifying that the extension is being performed. Click Next Server if you want to extend the Route53 resource instance to another server in your cluster. This will repeat the Extend Resource Hierarchy operation. If you click Finish, LifeKeeper for Windows will verify that the extension of the Route53 resource was completed successfully.
- Click Done to exit from the Extend Resources Hierarchy menu selection.