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 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 as shown below.
- 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 GUI menu, select Edit, then Resource. From the drop down menu, select Extend Resource Hierarchy. This will launch the Extend Resource Hierarchy wizard. If you are unfamiliar with the Extend operation, click Next. If you are familiar with the LifeKeeper Extend Resource Hierarchy defaults and want to bypass the prompts for input/confirmation, click Accept Defaults.
- The Pre-Extend Wizard will prompt you to enter the following information.
| Select the Switchback Type. This dictates how the EC2™ instance will be switched back to this server when it comes back into service after a failover to the backup server. You can choose either intelligent or automatic.
The switchback type can be changed later, if desired, from the General tab of the Resource Properties dialog box.
| Select or enter a Template Priority. This is the priority for the EC2™ hierarchy on the server where it is currently in service. Any unused priority value from 1 to 999 is valid, where a lower number means a higher priority (1=highest). The extend process will reject any priority for this hierarchy that is already in use by another system. The default value is recommended.
Note: This selection will appear only for the initial extend of the hierarchy.
| Select or enter the Target Priority. This is the priority for the new extended EC2™ 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 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 explaining that LifeKeeper has successfully checked your environment and that all the requirements for extending this AWS ECC resource have been met. If there were some requirements that have not been met, LifeKeeper will not allow you to select the Next button, and the Back button will 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 AWS ECC resource hierarchy to another server to put it under LifeKeeper 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:
|AWS ECC Resource Tag
| Select or enter the AWS ECC Resource Tag. This is the resource tag name to be used by the AWS ECC resource being extended to the target server.
Note: The field in not editable.
- An information box will appear verifying that the extension is being performed. Click Next Server if you want to extend the same AWS ECC resource instance to another server in your cluster. This will repeat the Extend Resource Hierarchy operation. If you click Finish, LifeKeeper will verify that the extension of the AWS ECC resource was completed successfully.
- Click Done to exit from the Extend Resources Hierarchy menu selection.