[mute]

Originally Posted by blackvborg

Hello mute, thank you for your post; I've evauleated all your points and the best (in theory) seems the 2nd, but it's not much reliable (eg the notify of file change happens when the write starts and not when it finish, moreover you've some headeache with the replication of new directories)

about NFS yes, it a SPOF. have you some figure about the performance of apache running against a local filesystem vs a network filesystem like NFS? in some benchmarks I've seen that the performance are much lower. for sure it's the easiest implementation.

About HA and NFS I think you could rsync the nfs content on a second passive server (or just one of your webserver) and in case of failure change the NFS server to the backup server

BTW I don't like none of them

for Loco.M: I'd replicate attachments bacause I need to have more webservers

for nexialys: I've not found much to date; I'm looking for realtime mirroring software; not found much except network filesystem like redhat gfs (poor performance for me)

any other advice?

Well, as far as NFS vs locally hosted content, I'm sure there's a performance hit, but I don't have any hard numbers. One thing to remember is that if you are using a PHP cache like Xcache, APC, etc, then a lot of your dynamic content (the only thing we serve via apache) is cached in memory, so the amount of traffic over the NFS is actually a lot less than you'd expect.