Specifications
Unextending Your Hierarchy
Field Tips
DataKeeper
Resource
Tag
Select or enter the DataKeeper Resource Tag name.
Bitmap File
Select or edit the name of the bitmap file used for intent logging. If you choose
none, then an intent log will not be used, and every resynchronization will be a
full resync instead of a partial resync.
Replication
Path
Select the pair of local and remote IP addresses to use for replication between
the target server and the other indicated server in the cluster. The valid paths
and their associated IP addresses are derived from the set of LifeKeeper
communication paths that have been defined for this same pair of servers. Due
to the nature of DataKeeper, it is strongly recommended that you use a private
(dedicated) network.
If the DataKeeper Resource has previously been extended to one or more target
servers, the extension to an additional server will loop through each of the
pairings of the new target server with existing servers, prompting for a
Replication Path for each pair.
Replication
Type
Choose “synchronous” or “asynchronous” to indicate the type of replication that
should be used between the indicated pair of servers.
As for the previous Replication Path field, if the DataKeeper Resource has
previously been extended to one or more target servers, the extension to an
additional server will loop through each of the pairings of the new target server
with existing servers, prompting for a Replication Type for each pair.
2. Click Extend to continue. An information box will appear verifying that the extension is being
performed.
3. Click Finish to confirm the successful extension of your DataKeeper resource instance.
4. Click Done to exit the Extend Resources Hierarchy menu selection.
Note: Be sure to test the functionality of the new instance on all servers by performing a
manual switchover. See Testing Your Resource Hierarchyfor details. At this point, SteelEye
DataKeeper has initiated the data resynchronization from the source to the target disk or
partition. In the LifeKeeper GUI, the state of the DataKeeper resource on the target server is
set to “Resyncing”. Once the resynchronization is complete, the state will change to “Target”
which is the normal Standby condition.
During resynchronization, the DataKeeper resource, and any resource that depends on it, will
not be able to failover. This is to avoid data corruption.
Unextending Your Hierarchy
To remove a resource hierarchy from a single server in the LifeKeeper cluster, do the following:
288Installation and Configuration