gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] replicate data between 2 servers and 1 client


From: Krishna Srinivas
Subject: Re: [Gluster-devel] replicate data between 2 servers and 1 client
Date: Fri, 13 Feb 2009 12:21:45 +0530

Alain,

Are those your actual vol files? just want to confirm.

>    option remote-host 192.168.x.x   # IP address of server2

you need to give proper IP address here.

>    option auth.ip.brick1.allow *all
>    option auth.ip.afr.allow *all

"*all" is incorrect here.

If these are not your actual vol files, can you paste them here?

Krishna

On Wed, Feb 11, 2009 at 6:04 PM, Alain Gonzalez <address@hidden> wrote:
> Hi,
>
> I have a problem. I need to replicate data between three machines. Two of
> machines are servers and one is a client.
>
> 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.
>
> I have done tests with the tutorials of glusterfs, but I donĀ“t have good
> results.
>
> Someone who can help me?
>
> #server1
>
> volume brick1
>    type storage/posix
>    option directory /home/export #created
> end-volume
>
> volume brick2
>    type protocol/client
>    option transport-type tcp/client
>
>    option remote-host 192.168.x.x   # IP address of server2
>    option remote-subvolume brick1   # use brick1 on server2
> end-volume
>
> volume afr
>    type cluster/afr
>    subvolumes brick1 brick2
> end-volume
>
>
> volume server
>    type protocol/server
>    option transport-type tcp/server
>    subvolumes brick1 afr
>    option auth.ip.brick1.allow *all
>    option auth.ip.afr.allow *all
> end-volumevolume brick1
>
>
> #server2
>
> volume brick1
>    type storage/posix
>    option directory /home/export #created
> end-volume
>
> volume brick2
>    type protocol/client
>    option transport-type tcp/client
>    option remote-host 192.168.x.x   # IP address of server1
>
>    option remote-subvolume brick1   # use brick1 on server1
> end-volume
>
> volume afr
>    type cluster/afr
>    subvolumes brick2 brick1
> end-volume
>
> volume server
>    type protocol/server
>    option transport-type tcp/server
>
>    subvolumes brick1 afr
>    option auth.ip.brick1.allow * #all
>    option auth.ip.afr.allow * #all
> end-volume
>
> #client
>
> volume brick
>    type protocol/client
>    option transport-type tcp/client # for TCP/IP transport
>
>    option remote-host 192.168.x.x   # IP address of the server ----> IP of
> the server1
>    option remote-subvolume afr      # name of the remote volume
> end-volume
>
> Best Regards
>
> --
> Alain Gonzalez
>
> _______________________________________________
> Gluster-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]