Specifications
Extending a Hierarchy to a Disaster Recovery System
During resynchronization, the DataKeeper resource and any resource that depends on it will
not be able to fail over. This is to avoid data corruption.
Extending a Hierarchy to a Disaster Recovery System
This operation can only occur from an ISP node or as the continuation of the creation process for
multiple nodes 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 Resourcethen 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
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 Multi-Site Cluster
hierarchy resource back to the primary server.
CAUTION: This release of SteelEye DataKeeper for Linux does not support
Automatic Switchback for DataKeeper resources. Additionally, the Automatic
Switchback restriction is applicable for any other LifeKeeper resource that
becomes part of the Multi-Site Cluster hierarchy. This includes anything sitting
above the hierarchy or becomes a child within the hierarchy.
Target
Priority
Select or enter the Target Priority. This is the priority for the new extended
DataKeeper 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 that LifeKeeper assigns the number “1” to the server on
which the hierarchy is created by default. The priorities need not be consecutive,
but no two servers can have the same priority for a given 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.
3. After receiving the message that the pre-extend checks were successful, click Next.
SteelEye Protection Suite for Linux321