Comments on DRBD 8.3 Third Node Replication With Debian Etch

Hello budy you did not mention the necesary config for node 3 *foxtrot*

 It's mention on the drdb.conf but, do I need to initiate any stuff on it, etc

 thanks

 yea, +1 to question. what about is?

yes its great to see this its help me a lot.

He's not your Budy, guy.

I'm guessing from all the testing i've just done that the 3rd node, since it's a backup and possibly remote node is used when the first two nodes fail. In this case, you can just stop drbd on the 3rd node and use the device as normal.

 e.g. if node3 drbd3 = /dev/sda3 then stop drbd, mount /dev/sda3 and proceed with disaster recovery.

 no idea how you would sync back, but this is about as far as i have gotten.

Once you stop drbd service on 3rd node, drbdx disappears from /dev.

Any other option to access 3rd node?

Hi!

All fine works before the first restart active node.

After try 

 drbdadm --stacked adjust r0-U

i see

Can not open device '/dev/drbd0': Read-only file system
Command 'drbdsetup 10 disk /dev/drbd0 /dev/drbd0 internal --set-defaults --create-device' terminated with exit code 20
drbdadm attach r0-U: exited with code 20

you have not had this problem?

Hi

How to recover in-case of both nodes alpha and bravo failed (shutdown), how to recover  the data from DR node (foxtrot).

I tried this way, but failed:

After the shutting down alpha and bravo, i stopped drbd on foxtrot and tried to mount the actual lvm (/dev/VG_drbd_bck/LV_drbd_bck - in my case), it says:

[root@mysqlserver3 ~]# mount /dev/VG_drbd_bck/LV_drbd_bck /opt/

mount: unknown filesystem type 'drbd'

If without stopping the drbd the:

[root@mysqlserver3 ~]# mount  /dev/drbd2 /mnt/ 

mount: you must specify the filesystem type

or if: 

[root@mysqlserver3 ~]# mount -t ext3 /dev/drbd2 /mnt/ 

mount: block device /dev/drbd2 is write-protected, mounting read-only

mount: Wrong medium type

None my tricks work, please help me on this issue.

hi, i an error when trying to execute any command on foxtrot machine => 'data-lower' is not recognized in the syncer block.

if i remove that line from drbd.conf it works well.

How to recover DR Node data when Primary Site Nodes are online