Specifications
Extending a DataKeeper Resource
4. Depending upon the hierarchy being extended, LifeKeeper will display a series of information
boxes showingthe Resource Tags to be extended, some of which cannot be edited.
Click Next to launch the Extend Resource Hierarchy configuration task.
The next section lists the steps required to complete the extension of a DataKeeper resource to
another server.
Extending a DataKeeper Resource
1. After you have been notified that your pre-extend script has executed successfully, you will be
prompted for the following information:
Field Tips
Mount Point
Enter the name of the file system mount point on the target server. (This dialog
will not appear if there is no LifeKeeper-protected filesystem associated with the
DataKeeper Resource.)
Root Tag
Select or enter the Root Tag. This is a unique name for the filesystem resource
instance on the target server. (This dialog will not appear if there is no
LifeKeeper-protected filesystem associated with the DataKeeper Resource.)
DataKeeper
Resource
Tag
Select or enter the DataKeeper Resource Tag name.
Bitmap File
Select 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.
Important: The bitmap file should not reside on a btrfs filesystem. Placing data
replication bitmap files on a btrfs filesystem will result in an "invalid argument"
error when LifeKeeper tries to configure the mirror. The default location for the
bitmap file is under /opt/LifeKeeper. This default location should be
changed if /opt/LifeKeeper resides on a btrfs filesystem.
2. Click Next 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 Hierarchy for details. At this point,
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.
320Multi-Site Cluster