Specifications

Extending Your Hierarchy
Extending Your Hierarchy
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.
1. 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.
2. 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.
Field Tips
Template
Server
Select the TemplateServer where your DataKeeper resource hierarchy 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 (activated) resource hierarchy.
An error message will appear if you select a resource tag that is not in service on
the template server you have selected. The drop down box in this dialog
provides the names of all the servers in your cluster.
Tag to
Extend
This is the name of the DataKeeper instance you wish to extend from the
template server to the target server. The drop down box will list all the resources
that you have created on the template server.
Target
Server
Enter or select the server you are extending to.
Switchback
Type
You must select intelligent switchback. This means that after a failover to the
backup server, an administrator must manually switch the DataKeeper resource
back to the primary server.
CAUTION: This release of SteelEye DataKeeper does not support Automatic
Switchback for DataKeeper resources. Additionally, the Automatic Switchback
restriction is applicable for any other LifeKeeper resource sitting on top of a
SteelEye DataKeeper resource.
Template
Priority
Select or enter a Template Priority. This is the priority for the DataKeeper
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.
286Installation and Configuration