ISPConfig3 Multiservers Architecture

[federico]

Hi forum,
is it possible to configure an ISPConfig3 architecture with more than one server for single service and to manage them from a unique hosting control panel?

As Web Service can I use ISPConfig3 to realize the solutions below?

web-1) Two Webserver hosts and using the hosting control panel to partition the clients's sites on them.

web-2) Can I have two Webserver hosts that host the same client's site, and use a load balancer to balance the site web traffic? In this case I think that the DB used should be unique.

Are there particoular ISPConfig3 aspects to be aware in order to implement the above two solutions?

As DB Service:

DB-1) Can I have more than one DB Server and using the hosting control panel to partition the clients's databases on them.

Thanks for the answers,
Federico

[till]

You may configure as many servers for web, email and database from one ispconfig controlpanel as you like. Just install all other servers in expert mode and choose to join the master server. ISPConfig is replicating the nescessary database entrys from the master db automatically, so the servers will not fail if the master database is offline.

ISPConfig does not support mirroring, this will be implemented in version 3.0.2

[federico]

You may configure as many servers for web, email and database from one ispconfig controlpanel as you like. Just install all other servers in expert mode and choose to join the master server. ISPConfig is replicating the nescessary database entrys from the master db automatically, so the servers will not fail if the master database is offline.

ISPConfig does not support mirroring, this will be implemented in version 3.0.2

Hi Till,
can the database servers be on a backend network or does ispconfig require a plan network for the servers involved in the multiservers architecture?

Thanks,
Federico

[till]

The database server can be anywhere as long as it is reachable on a IP adress. But it is highly recomended that every instance runs its own local mysql server for best speed. If you run a central mysql instance it might fail on higher load with too many connections, thats why ispconfig replicates the database records automatically to the local databases and uses these as some kind of fast query cache.