Troubles while using DRBD 9.2.4 about drbd HOT 2 CLOSED

1. Replacing device files

This is not an issue with DRBD. It is the kernel that enumerates the block devices. If you want to avoid this in the future you can use udev symlinks such as /dev/disk/by-uuid/ within your DRBD configuration or just simply use LVM.

2. Not recognizing the service user

Again, this is not an issue with DRBD. I suspect the named user does not have the same uid and gid on all nodes. You need to make sure the uid and gid of users match across the cluster nodes for things to work properly.

3. Loss of all data in mount point

We need more information here. The data was likely not deleted, or if it was, something other than DRBD deleted it. My best guess here is that DRBD was in some degraded state, or you were running your commands on the primary node when a failover occured.

from drbd.

Also, worth mentioning that we have a community Slack channel as well as a DRBD user mailing list where configuration and use-case specific questions like this can be asked.

from drbd.