in this case, the namespace brick should be AFR'ed then correct? would that break things if log files are on some clients and not others? At 08:57 PM 11/15/2008, Basavanagowda Kanur wrote: >Claudiu, > You can use unify over afr. And use switch translator to schedule > your log files to a subvolume which does not replicate (without > afr) and rest of the files to afr. > >volume unify > type cluster/unify > option scheduler switch > option switch.case <pattern>:<non-replicated-subvolume>;*:<afr-subvolume> > option namespace <namespace> > subvoumes <non-replicated-subvolume> <afr-subvolume> >end-volume > >-- >gowda > >On Sat, Nov 15, 2008 at 2:32 PM, claudiu ciurdariu ><<mailto:clauc_007 at yahoo.com>clauc_007 at yahoo.com> wrote: >Hi guys, > >I'm trying to implement AFR across 2 servers and I was wondering if >there is any option that would allow me to exclude some >subdirectories from replicating each other. Say I have a directory >structure like this: > >/var/www/domain1/htdocs >/var/www/domain1/logs >/var/www/domain2/htdocs >/var/www/domain2/logs >.... > >I want to AFR /var/www across the 2 servers, but exclude the logs >directories from replication. Is there any translator that would >help me achieve that? > >Any help is appreciated. > >Claudiu > > >_______________________________________________ >Gluster-users mailing list ><mailto:Gluster-users at gluster.org>Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > > > > >-- >hard work often pays off after time, but laziness always pays off now >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
