<div dir="ltr">Hi.<br><br>Thanks for the example, but how actually server-side AFR works?<br><br>I mean, when you put a file on one server, it writes to the second one? And vice-versa?<br><br>Regards.<br><br><div class="gmail_quote">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">here's my server configs:<br>
<br>
volume home1<br>
type storage/posix # POSIX FS translator<br>
option directory /gluster/home # Export this directory<br>
end-volume<br>
<br>
volume posix-locks-home1<br>
type features/posix-locks<br>
option mandatory on<br>
subvolumes home1<br>
end-volume<br>
<br>
## Reference volume "home2" from remote server<br>
volume home2<br>
type protocol/client # POSIX FS translator<br>
option transport-type tcp/client<br>
option remote-host <a href="http://192.168.2.2" target="_blank">192.168.2.2</a> # IP address of remote host<br>
option remote-subvolume posix-locks-home1 # use home1 on remote host<br>
option transport-timeout 10<br>
end-volume<br>
<br>
### Create automatic file replication<br>
volume home<br>
type cluster/afr<br>
option read-subvolume posix-locks-home1<br>
subvolumes posix-locks-home1 home2<br>
end-volume<br>
<br>
### Add network serving capability to above home.<br>
volume server<br>
type protocol/server<br>
option transport-type tcp/server # For TCP/IP transport<br>
subvolumes posix-locks-home1<br>
option auth.addr.posix-locks-home1.allow <a href="http://192.168.2.2" target="_blank">192.168.2.2</a>,<a href="http://127.0.0.1" target="_blank">127.0.0.1</a><br>
<br>
<br>
###I believe the following will do what you want, it's not exactly the same as mine since I added the auth option for the clients (192.168.1.x) to mount home--the AFR volume<br>
option auth.addr.home.allow <a href="http://92.168.1.1" target="_blank">92.168.1.1</a>,<a href="http://192.168.1.2" target="_blank">192.168.1.2</a>,<a href="http://127.0.0.1" target="_blank">127.0.0.1</a> #<br>
end-volume<br>
<br>
<br>
<br>
</blockquote></div></div>