On Jan 7, 2008 9:11 PM, Anand Avati <avati@xxxxxxxxxxxxx> wrote: > Here is a very nice tutorial from Paul England which gives a usage case for > server side replication and high availability - > > > http://www.gluster.org/docs/index.php/GlusterFS_High_Availability_Storage_with_GlusterFS > > The configuration in the article can be further simplified by removing the > unify layer and having only AFR and will work for most users. unify will be > needed in this setup only if you want to extend this config with something > more advanced. > > avati > > 2008/1/8, matthew zeier <mrz@xxxxxxxxxxx>: > > > > > > > > >> I imagine the server config would look like: > > >> > > >> volume local-brick > > >> type storage/posix > > >> option directory /mnt/local-brick > > >> end-volume > > >> > > >> volume remote-brick > > >> type protocol/client > > >> option transport-type tcp/client > > >> option remote-host 10.2.10.100 > > >> option remote-subvolume other-local-brick > > >> end-volume > > >> > > >> volume afr1 > > >> type cluster/aft > > >> subvolumes local-brick remote-brick > > >> end-volume > > >> > > >> That's all a guess though. > > > > > > But then would all your clients all only connect to 1 server? kinda > > > seems like so i guess unless there is some round robin something or > > > other? > > > > > > I dunno - the client could use unify and mount both servers' afr1. > > > > I'm sure someone with more clue can say for sure :) > > > > > > > > _______________________________________________ > > Gluster-devel mailing list > > Gluster-devel@xxxxxxxxxx > > http://lists.nongnu.org/mailman/listinfo/gluster-devel Oh very cool, I actually even read that an hour ago or so but must have closed the tab, off to try this out thanks!
