Tried to find anywhere else, not really proficient in Windows.
I have two backing devices on linux servers, which works well with
linux diskless clients. Now I'm trying to achieve the same with Win
2019 Server diskless. It works but I have to manually bring the
resource up and make it primary after each reboot. Can't figure out
how to stick it. Did I miss something?
Here is the dumped config:
resource win {
on combo {
node-id 1;
volume 1 {
device minor 1;
disk none;
}
address ipv4 10.10.3.100:7799;
}
on drbd-01 {
node-id 2;
volume 1 {
device /dev/drbd1 minor 1;
disk /dev/soft/win;
meta-disk internal;
}
address ipv4 10.10.3.3:7799;
}
on drbd-02 {
node-id 3;
volume 1 {
device /dev/drbd1 minor 1;
disk /dev/soft/win;
meta-disk internal;
}
address ipv4 10.10.3.4:7799;
}
connection-mesh {
hosts drbd-01 drbd-02 combo;
}
net {
protocol C;
}
}
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user
I have two backing devices on linux servers, which works well with
linux diskless clients. Now I'm trying to achieve the same with Win
2019 Server diskless. It works but I have to manually bring the
resource up and make it primary after each reboot. Can't figure out
how to stick it. Did I miss something?
Here is the dumped config:
resource win {
on combo {
node-id 1;
volume 1 {
device minor 1;
disk none;
}
address ipv4 10.10.3.100:7799;
}
on drbd-01 {
node-id 2;
volume 1 {
device /dev/drbd1 minor 1;
disk /dev/soft/win;
meta-disk internal;
}
address ipv4 10.10.3.3:7799;
}
on drbd-02 {
node-id 3;
volume 1 {
device /dev/drbd1 minor 1;
disk /dev/soft/win;
meta-disk internal;
}
address ipv4 10.10.3.4:7799;
}
connection-mesh {
hosts drbd-01 drbd-02 combo;
}
net {
protocol C;
}
}
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user