<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Paul,<br>
<br>
That config looks right, however you will want to use a VIP address
instead of the IP address of just 1 node. This IP will move between
the 2 local nodes to whichever node is active, otherwise if when the
node with the IP in the local resource is down you will not get
updates to the stacked offsite node.<br>
<br>
Also be aware of private vs. public IP space and how the IPs may
appear when NAT comes into play and which IPs need to appear where
in the config. I avoid this by having my 2 locations connected by
VPN so all addresses are direct, no NAT.<br>
<br>
Aaron<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 9/26/2013 4:06 PM, Paul O'Rorke
wrote:<br>
</div>
<blockquote cite="mid:5244AFE9.30701@tracker-software.com"
type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">Thanks for that Aaron,<br>
<br>
I'm looking at this page <a moz-do-not-send="true"
href="http://www.drbd.org/users-guide/s-three-nodes.html">http://www.drbd.org/users-guide/s-three-nodes.html</a>
and not quite sure I understand how to merge this with my
current config. Currently I have 5 resources using Protocol C
on my 2 node local cluster. <br>
<br>
For the sake of this set up I will consider the set up one of
these resources with a third node using a stacked resource and
protocol A then hopefully once that is working I can apply this
to the other resources.<br>
<br>
In the example provided it appears that I need to define all
three resources in the one .res file. I have the following 2
config files:<br>
<br>
<b>/etc/drbd.d/global_common.conf</b><br>
global {<br>
usage-count yes;<br>
}<br>
common {<br>
protocol C;<br>
}<br>
<br>
and <br>
<br>
<b>/etc/drbd.d/restored.res</b><br>
resource restored {<br>
device /dev/drbd2;<br>
disk /dev/VirtualMachines/restored;<br>
meta-disk internal;<br>
on kvm-srv-01 {<br>
address 192.168.2.41:7789;<br>
}<br>
on kvm-srv-02 {<br>
address 192.168.2.42:7789;<br>
}<br>
}<br>
<br>
<br>
can I just tack something like this onto the end of <b>/etc/drbd.d/restored.res</b>?<br>
<br>
<pre class="programlisting">resource restored-U {
net {
protocol A;
}
stacked-on-top-of restored {
device /dev/drbd10;
address 192.168.3.41:7788;
}
on buckingham {
device /dev/drbd10;
disk /dev/hda6;
address <fixed IP at backup node>:7788; # Public IP of the backup node
meta-disk internal;
}
}</pre>
<br>
I am also wondering, since I have a spare NIC on my local nodes,
would I be better to use that to connect to my off site resource
or use the LAN connected NIC? In the example above I used a
different subnet for the off site and called the off site
machine 'buckingham'.<br>
<br>
I hope my question makes sense, still finding my feet here.<br>
<br>
Please and thanks<br>
<div class="moz-signature">
<div style="font-family:Arial;font-size:12px">
<p><strong>Paul O’Rorke</strong><br>
Tracker Software Products<br>
<a moz-do-not-send="true"
href="mailto:paul.ororke@tracker-software.com">paul@tracker-software.com</a></p>
</div>
</div>
On 9/25/2013 2:21 PM, Aaron Johnson wrote:<br>
</div>
<blockquote
cite="mid:48224317-CFBC-4E65-91EC-2C301194AC7D@ajserver.com"
type="cite">
<pre wrap="">Yes you can add the stacked resource later, I have done this same thing several times now by making the the device slightly larger first and using internal metadata.
Also I have a DR site using protocol C and pull-ahead enabled without using DRBD proxy. The main site and DR site are connected via cable modem connections (10Mbit up/ 20 down both sides). The only thing I have troubles with is if I need to add a large amount of data (50+ GB), which in my case is fairly rare (daily norm is ~2GB), then it can take days or weeks to sync up fully again. Also I used truck-based updates for the initial setup of ~1TB to avoid having to pull all that over the internet link.
Thanks,
AJ
</pre>
<blockquote type="cite">
<pre wrap="">On Sep 25, 2013, at 7:54 AM, Lionel Sausin <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:ls@numerigraphe.com"><ls@numerigraphe.com></a> wrote:
Le 25/09/2013 08:10, <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:roberto.fastec@gmail.com">roberto.fastec@gmail.com</a> a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">The purpose you are talking about, sounds more as the purpose DRBD Proxy has been developed for
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.linbit.com/en/products-and-services/drbd-proxy">www.linbit.com/en/products-and-services/drbd-proxy</a>
</pre>
</blockquote>
<pre wrap="">Yes and no, my understanding is that DRBD-proxy lets your production cluster run faster than the connection speed by acting like a write cache.
But if I'm not mistaken you still need a stacked configuration for 3 node setups until v9.0 is released.
Someone please correct me if that's wrong of course.
Lionel Sausin
_______________________________________________
drbd-user mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.linbit.com/mailman/listinfo/drbd-user">http://lists.linbit.com/mailman/listinfo/drbd-user</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
drbd-user mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.linbit.com/mailman/listinfo/drbd-user">http://lists.linbit.com/mailman/listinfo/drbd-user</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>