This operation can be started from the Edit menu, or initiated automatically upon completing the Create Resource Hierarchy option, in which case you should refer to Step 2 below.
- On the Edit menu, select Resource, then Extend Resource Hierarchy. The Pre-Extend Wizard appears. 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.
Note: The first two fields appear only if you initiated the Extend from the Edit menu.
|Template Server||Enter the server where your Apache resource is currently in service. It is important to remember that the Template Server you select now and the Tag to Extend that you select in the next dialog box represent an in service resource hierarchy. An error message will appear if you select a resource tag that is not in service on the template server you selected. The drop down box in this dialog provides the names of all the servers in your cluster.|
|Tag to Extend||Select the name of the Web Server instance you wish to extend from the template server to the target server. The wizard will list in the drop down list box all the resources that you have created on the template server, which you selected in the previous dialog box.|
|Target Server||Select the Target Server where you are extending your Web Server resource hierarchy. The drop down box provides the names of the servers in your cluster that are not already in the selected hierarchy.|
|Switchback Type||Select either intelligent or automatic. This dictates how the Web Server instance will be switched back to this server when it comes back into service after a failover to the backup server. Intelligent switchback requires administrative intervention to switch the instance back to the primary/original server. Automatic switchback means the switchback will occur as soon as the primary server comes back on line and reestablishes LifeKeeper communication paths.|
|Template Priority||Select or enter a priority for the template hierarchy. 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.|
|Target Priority||Select or enter the Target Priority of your extended Web Server resource. The priority is a number between 1 and 999 indicating a server’s priority in the cascading failover sequence for the resource. The hierarchy priorities are sorted numerically, where a lower number means a higher priority (the number 1 indicates the highest priority). Note that LifeKeeper automatically assigns the number “1” to the server that the hierarchy is created on. The priorities need not be consecutive, but no two servers can have the same priority for a given resource.|
| After receiving the message that the pre-extend checks were successful, click Next.
Depending upon the hierarchy being extended, LifeKeeper will display a series of information boxes showing the Resource Tags to be extended, which cannot be edited. Click Extend
|Network Interface||Select or enter the Network Interface. This is the name of the network interface (i.e. Ethernet card) the IP resource will use on the target server.|
|Backup Interface||Select a Backup Interface if you want to engage the IP Local Recovery feature on the server to which you are extending the IP resource. The default value is none; however, if you have another network interface card configured on this server, it should be listed in the drop down list.|
|IP Resource Tag||Select or enter the IP Resource Tag. This is the resource tag name to be used by the IP resource being extended to the target server.|
|Root Tag||Select or enter the Root Tag. This is the tag name given to the Web Server hierarchy. By default, the Root Tag name should be the same on both the template and target server.|
|Mount Point|| This selection appears only when the Web Server Root Directory is on a shared file system.
Select or enter the Mount Point of the shared file system where the Web Server Root Directory is located. The Template Server and Target Server should have the same mount point for the shared Web Server Root Directory. The default mount point provided in the dialog box should be selected in most cases.
|Root Tag|| This selection appears only when the Web Server Root Directory is on a shared file system.
Select or enter the Root Tag. This is the tag name of the shared file system.
- An information box will appear verifying that the extension is being performed. Click Next Server if you want to extend the same Apache 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 Web Server resource was completed successfully.
- Click Done in the last dialog box to exit from the Extend Resource Hierarchy menu selection.
Note: Be sure to test the functionality of the new instance on both servers.
Thanks for your feedback.
Post your comment on this topic.