Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello,
i think it's clear and the pacemaker config is also clear but i can't
get a positiv result.
I started with 4 maschines
vm01 vm02 vm03 vm04
On vm01 and vm02 i created a DRBD resource with this config.
resource test {
device /dev/drbd3;
meta-disk internal;
disk /dev/vg01/test;
protocol C;
syncer{
rate 800M;
}
on vm01 {
address 10.10.255.12:7003;
}
on vm02 {
address 10.10.255.13:7003;
}
}
On vm03 and vm04 i created this DRBD Resource
resource test2 {
device /dev/drbd3;
meta-disk internal;
disk /dev/vg01/test;
protocol C;
syncer{
rate 800M;
}
on vm03 {
address 10.10.255.14:7003;
}
on vm04 {
address 10.10.255.15:7003;
}
}
This two unstacked resources are running.
If i look in the documentation i think that i need to create the
following DRBD Resource on vm01-04.
resource stest {
protocol A;
stacked-on-top-of test2 {
device /dev/drbd13;
address 10.10.255.16:7009;
}
stacked-on-top-of test {
device /dev/drbd13;
address 10.10.255.17:7009;
}
}
But if i save this and copy them to all vms i get on vm03-04 if i run
drbdadm --stacked create-md stest
drbd.d/stest.res:1: in resource stest, referenced resource 'test' not
defined.
and vm01-02 on
drbd.d/stest.res:1: in resource stest, referenced resource 'test2' not
defined.
What do i need that vm01-02 know about test2 on vm03-04 and vm03-04 know
about test on vm01-02?
Both ip addresses are virtual adresses on vm01 and vm03 where test and
test2 are primary
That is what i understood after i look on the picture and the pacemaker
configuration.
Best regards
Benjamin
Am 13.01.2012 15:27, schrieb Andreas Kurz:
> Hello,
>
> On 01/13/2012 12:56 PM, Benjamin Knoth wrote:
>> Hi,
>>
>> i will create a 4 node replication with DRBD.
>> I read also the documentation.
>> I understand also the configuration of a 3 way replication, but how do i
>> need to config the 4 way replication?
>>
>> I configured 2 2way resources successfully and now i need to config the
>> stacked resource.
>
> Have a look at:
>
> http://www.drbd.org/users-guide-8.3/s-pacemaker-stacked-resources.html#s-pacemaker-stacked-dr
>
> ... a picture says more than 1000 words ;-)
>
>>
>> resource r0-U {
>> {
>> protocol A;
>> }
>> stacked-on-top-of r0 {
>> device
>> /dev/drbd10;
>> address
>> 192.168.42.1:7788;
>> }
>> on charlie {
>> device /dev/drbd10;
>> disk /dev/hda6;
>> address 192.168.42.2:7788; # Public IP of the backup
>> meta-disk internal;
>> }
>>
>> }
>>
>>
>> Is the solution to define on server alice and bob and charlie and daisy
>> a lower level resource with protoc C and than one stacked resource where
>> directly the stacked resource from alice and bob communicate with the
>> stacked resource of charlie and daisy like this configuration?
>
> Yes, configure the replication between two stacked resources.
>
>>
>> resource stacked {
>> protocol A;
>> stacked-on-top-of r0 {
>> device /dev/drbd10;
>> address 192.168.:7788;
>> }
>> stacked-on-top-of r0 {
>> device /dev/drbd10;
>> address 134.76.28.188:7788;
>> }
>> }
>>
>> Best regards
>
> Regards,
> Andreas
>
>
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4520 bytes
Desc: S/MIME Kryptografische Unterschrift
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120116/788e06e5/attachment.bin>