SIOS TECHNOLOGY CORP.

DRBD Recovery Kit Known Issues / Restrictions

Description
DRBD resource files are not deleted from /opt/LifeKeeper/subsys/scsi/resources/drbd/ when a resource is paused.

If you delete a drbd resource while it is paused it will leave files in /opt/LifeKeeper/subsys/scsi/resources/drbd/ when a resource is deleted.

The workaround is to go the /opt/LifeKeeper/subsys/scsi/resources/drbd/ by running cd /opt/LifeKeeper/subsys/scsi/resources/drbd and manually delete the files
Connection issues when rebooting a paused node.

When a target node where DRBD is paused is rebooted, the connection may fail when the node comes into service, or synchronization may resume.
This happens when rebooting a target node where DRBD is paused and there is unsynchronized data from the source. It is recommended to resume DRBD before rebooting.
If this issue arises, execute the following commands in the specified order:
First, obtain the DRBD resource name. This command can only be executed if the resource is in service.

$ drbdadm status
lk0 role:Secondary

Next, disconnect the resources on all nodes. Replace lk# with your resource name.
# drbdadm disconnect lk#

Connect resources on all nodes.
# drbdadm connect lk#

Then, resume the DRBD resource on the source node.
# lkcli drbd resume --tag <tag>
The lkcli command for DRBD does not support export/import.
lkbackup will not backup resource files if there are more than one set of resource files.

lkbackup will not backup DRBD resource files when there are more than one set of resource files (one set is defined as lk#.res and lk#.res.db). If there is only one set of files then they will be properly backed up. The workaround is to manually save all resource files.
DRBD: Unable to change DRBD connection endpoint IPs using lk_chg_value.

While the IP addresses used by some LifeKeeper recovery kits can be updated by using the /opt/LifeKeeper/bin/lk_chg_value script (see, for example, Changing the Data Replication Path (DataKeeper), Changing the IP for the Queue Manager (IBM MQ), and Changing LifeKeeper Configuration Values), this script cannot currently be used to modify IP addresses used by DRBD resources.

Executing commands similar to the following:

# lkstop
# /opt/LifeKeeper/bin/lk_chg_value -o 182.168.0.1 -n 192.168.1.1
# lkstart

will modify the IP addresses used by LifeKeeper communication paths on the system. However, this will not update the IP addresses in DRBD configuration files. Usage of LifeKeeper to update the connection endpoints for a DRBD resource is currently not supported.
DRBD does not fully resync after unextend/reextend

If a DRBD resource is unextended and then extended again a full resync is required. If the full resync is not automatically performed take the DRBD resource out-of-service and then back in-service on the same node where it was in-service. This should cause any outstanding out-of-sync blocks to be replicated.
Creating/extending a DRBD resource will fail when protecting NVMe devices and some other devices where the path exceeds 128 characters.

The following error message is displayed when the creation or extension of a DRBD resource fails:
/etc/drbd.d/lk0.res.tmp:48: Token too long >>>/dev/disk/by-id/nvme...<<<

The problem can occur on an NVMe device or other device that does not have a GUID Partition Table (GPT).

LifeKeeper uses the /dev/disk/by-id/ path as a persistent identifier for devices that do not have a GUID Partition Table (GPT) created. If you protect a device with a by-id path that exceeds 128 characters, the creation and extension of the DRBD resource will fail.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment