Is it ok on the glusterfsd server to have the <export-directory> storage be an NFS mount? I.e. so that the AFR replicated copy of all data from all clients would go to NFS? ________________________________ From: basavanagowda at gmail.com [mailto:basavanagowda at gmail.com] On Behalf Of Basavanagowda Kanur Sent: Tuesday, November 11, 2008 2:49 AM To: Aleynikov, Serge Cc: gluster-users at gluster.org Subject: Re: File replication Aleynikov, Find replies inline. On Tue, Nov 11, 2008 at 4:06 AM, Aleynikov, Serge <Serge.Aleynikov at gs.com> wrote: Hi, I am new to this list, and would like to find out if GlusterFS can serve the following need. I have N servers running services that log to local disk and I need the content of these local logs to be replicated in "close-to-real-time" to some central storage to be accessible by other tools. Can I use GlusterFS for this purpose? If so, could you point me to a sample configuration setup? Yes, you can use. Run glusterfs server on central storage node. with the following spec file volume storage type storage/posix option directory <export-directory> end-volume volume server type protocol/server option transport-type <tcp-or-ibverbs> option auth.addr.storage.allow <ipaddress-or-username> subvolumes storage end-volume On the machines where your log files are updated, mount glusterfs using the following spec: volume client type protoco/client option remote-host <ipaddress> option remote-subvolume storage end-volume volume local-storage type storage/posix option directory <local-directory> end-volume volume afr type cluster/afr subvolumes local-storage client end-volume And point your logging process to log on mounted directory. Thanks. Serge _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users -- gowda -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081111/ec379677/attachment-0001.htm
