Hi all, I have to build a clustered website with FreeBSD 7.x as SO and Apache 2.x as httpd. As load-balancing solution I'll use HAProxy (or maybe a OpenBSD relayd, I'm not sure). Because of several technical (and especially non-technical) reasons, I haven't the possibility to mount a shared storage layer (NFS, SAN...) so I have to share the local data among the different httpd servers. At first approach I've thought in rsync+cron, but ?anyone knows another replication-data solution in the described scenario? PD. Please, don't advice to me to using a pure shared-data layer... I know it will be the optimal structure, but as I've said above, I can't use it because various reasons. -- Thanks, Jordi Espasa Clofent
On Mon, Nov 03, 2008 at 10:35:59PM +0100, Jordi Espasa Clofent wrote:> I have to build a clustered website with FreeBSD 7.x as SO and Apache > 2.x as httpd. As load-balancing solution I'll use HAProxy (or maybe a > OpenBSD relayd, I'm not sure). > > Because of several technical (and especially non-technical) reasons, I > haven't the possibility to mount a shared storage layer (NFS, SAN...) so > I have to share the local data among the different httpd servers. > > At first approach I've thought in rsync+cron, but > > ?anyone knows another replication-data solution in the described scenario? > > PD. Please, don't advice to me to using a pure shared-data layer... I > know it will be the optimal structure, but as I've said above, I can't > use it because various reasons.Try ggatec(8) and ggated(8). They perform replication at the filesystem level, over the network. I do not have experience using them. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
On Mon, Nov 3, 2008 at 10:35 PM, Jordi Espasa Clofent <jespasac@minibofh.org> wrote:> Hi all, > > I have to build a clustered website with FreeBSD 7.x as SO and Apache 2.x as > httpd. As load-balancing solution I'll use HAProxy (or maybe a OpenBSD > relayd, I'm not sure). > > Because of several technical (and especially non-technical) reasons, I > haven't the possibility to mount a shared storage layer (NFS, SAN...) so I > have to share the local data among the different httpd servers. > > At first approach I've thought in rsync+cron, but > > ?anyone knows another replication-data solution in the described scenario? > > PD. Please, don't advice to me to using a pure shared-data layer... I know > it will be the optimal structure, but as I've said above, I can't use it > because various reasons. > > -- > Thanks, > Jordi Espasa ClofentGlusterFS http://www.gluster.org seems promising. It is a replication layer that sits on top of FUSE (Filesystem in Userspace http://fuse.sf.net). You can replicate pretty much any type of file system, ufs, zfs, dos...etc. In other words, you don't need to reformat your disk or create some special underlying file system. GlusterFS is in userspace. However.... I have yet to get it working on freebsd. Anyone had any luck with GlusterFS on Freebsd 6.x? Michael Grant
On 04/11/2008, at 8:35 AM, Jordi Espasa Clofent wrote:> At first approach I've thought in rsync+cron, butunison [1] works really well for us. In some ways it is better than some sort of shared SAN type solution since there is no single point of failure at the SAN or link to the SAN. Unison is just two way rsync so that changes can propagate in both directions between servers. Ari [1] http://www.cis.upenn.edu/~bcpierce/unison/ --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
On Mon, 03 Nov 2008 22:35:59 +0100 Jordi Espasa Clofent <jespasac@minibofh.org> wrote:> Hi all,Hola Jordi,> I have to build a clustered website with FreeBSD 7.x as SO and Apache > 2.x as httpd. As load-balancing solution I'll use HAProxy (or maybe a > OpenBSD relayd, I'm not sure).you may want to look into carp as well if you don't want to have a separate layer of load balancers.> Because of several technical (and especially non-technical) reasons, I > haven't the possibility to mount a shared storage layer (NFS, SAN...) so > I have to share the local data among the different httpd servers. > > At first approach I've thought in rsync+cron, but > > __anyone knows another replication-data solution in the described scenario?rsync / rsyncd is simple and works. But it really depends on how often you'll be publishing to your site, how big are the change sets ( consider publishing to a separate directory via rsync and then doing an atomic rename/move if the change set is too big.) we used to publish from AU to NL to dir1 in server1 , then ssh to server1 and rsync to server2-n in parallel - all from a script of course. That way, the slow link ( AU <-> NL) never got in the way of the publish. B _________________________ {Beto|Norberto|Numard} Meijome He could be a poster child for retroactive birth control. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.