As a side note, you can avoid ha if you're using replicate on client side.<br><br><div class="gmail_quote">On Wed, Feb 11, 2009 at 9:51 PM, Raghavendra G <span dir="ltr"><<a href="mailto:raghavendra@zresearch.com">raghavendra@zresearch.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Alain,<br><br>In the configuration you are using, replicate is on server side which means servers replicate among themselves. If the server which the client is currently communicating with goes down, client has to 'switch' to the other server. This functionality can be provided by using High availability (HA) on client side.<br>
<br>on client the configuration can be<br><br>volume client1<br> type protocol/client<br> .<br> .<br> option remote-host server1<br>end-volume<br> <br><br>volume client2<br> type protocol/client<br> .<br> .<br> option remote-host server2<br>
end-volume<br><br>volume ha<br> type cluster/ha<br> subvolumes client1 client2<br>end-volume<br><br>regards,<br><br><br><div class="gmail_quote"><div><div></div><div class="Wj3C7c">On Wed, Feb 11, 2009 at 4:34 PM, Alain Gonzalez <span dir="ltr"><<a href="mailto:alaingonza@gmail.com" target="_blank">alaingonza@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">Hi,
<br>
<br> I have a problem. I need to replicate data between three machines. Two of machines are servers and one is a client.
<br><br>
If I change data in client, also changed in the two servers. And if I change any data on a server1, also changed in the other server2 and
client. <br><br>I have done tests with the tutorials of glusterfs, but I donīt have good results.<br>
<br> Someone who can help me? <br><br>#server1<br><pre>volume brick1<br> type storage/posix<br> option directory /home/export #created<br>end-volume<br><br>volume brick2<br> type protocol/client<br> option transport-type tcp/client<br>
option remote-host 192.168.x.x # IP address of server2<br> option remote-subvolume brick1 # use brick1 on server2<br>end-volume<br><br>volume afr<br> type cluster/afr<br> subvolumes brick1 brick2<br>end-volume<br>
<br>volume server<br> type protocol/server<br> option transport-type tcp/server<br> subvolumes brick1 afr<br> option auth.ip.brick1.allow *all<br> option auth.ip.afr.allow *all<br>end-volumevolume brick1<br><br>
</pre>#server2<br><pre>volume brick1<br> type storage/posix<br> option directory /home/export #created<br>end-volume<br><br>volume brick2<br> type protocol/client<br> option transport-type tcp/client<br> option remote-host 192.168.x.x # IP address of server1<br>
option remote-subvolume brick1 # use brick1 on server1<br>end-volume<br><br>volume afr<br> type cluster/afr<br> subvolumes brick2 brick1<br>end-volume<br><br>volume server<br> type protocol/server<br> option transport-type tcp/server<br>
subvolumes brick1 afr<br> option auth.ip.brick1.allow * #all<br> option auth.ip.afr.allow * #all<br>end-volume<br></pre><br>#client<br><pre>volume brick<br> type protocol/client<br> option transport-type tcp/client # for TCP/IP transport<br>
option remote-host 192.168.x.x # IP address of the server ----> IP of the server1<br> option remote-subvolume afr # name of the remote volume<br>end-volume<br></pre>Best Regards<br clear="all"><br>-- <br><font color="#888888">Alain Gonzalez<br>
</font><br></div></div>_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br>
<a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><font color="#888888">Raghavendra G<br><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Raghavendra G<br><br>