Hello, I want to setup an ISPConfig3 cluster, following the helpful HOWTOs for doing so on HOWTOForge. It all seems fairly straightforward I will have dedicated servers for e-mail DNS, database, and web. At this time, only the web servers will be clustered (load balanced), though I will likely set the mail server up in such a fashion that it too could be clustered if the need arises in the future. All storage (e-mail database, and website files) will be on a central backend storage (instead of syncing via Unison or GlusterFS) The ISPConfig cluster HOWTO goes through setting up a master server and slave server for the web. It seems that the master server hosts the ISPConfig interface and the slave server would just serve up websites. I am wondering if it would be possible (or even feasible) to instead put the IPSConfig interface on a different server in the cluster and have the web servers serving up just websites? I would want to be able to have either of the web servers go down (maintenance, failure, etc.) without affecting my ability to continue to manage things. If this is indeed possible, how would be the best way to go about this? I am thinking something along the lines of: ISPConfig server: Install packages for running web server (apache, php, MySQL, etc.) Run ISPConfig3 installer in expert mode choose to only install Apache and choose to install ISPConfig interface Web1 and Web2 servers: Install packages for running web server (apache, php, MySQL, etc.) Run ISPConfig3 installer in expert mode Choose "Yes" to adding to existing cluster Configure only Apache and select "No" to installing ISPConfig interface Setup MySQL databases for master-master replication, per ISPConfig3 cluster HOWTO Once the above is done, do I set both Web1 and Web2 to be slaves of the ISPConfig server, or would I have Web1 as a "master" and Web2 (and any subsequent web servers) as slaves of Web1? Thanks, in advance, for your insight.