Database in a MultiServer Environment

Discussion in 'Installation/Configuration' started by Casbot, Jan 21, 2020.

  1. Casbot

    Casbot Member

    Im trying to make sure I grasp how the database runs now with a Master ISPC Web Server, a Mail Server, a DB server, NS1 server and NS2 server.
    During the install, all servers per the documentation were installed with MariaDB. It was instructed to create 'root'@'ip' and 'root'@'fqdn' for every server on the Master Web Server database and grant all the permissions. Now after all of the servers are built, Im seeing [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], and [email protected] with their privileges set to "usage".

    So are all of the databases replicating to the Master? Is there any database redundancy going on? Or does each database contain it's own information. Can someone explain because it almost seems like a hub and spoke database design where I still have a single point of failure if the Master WebServer database goes down?

    I did the multiserver setup this time because I want to make sure that all of the eggs are not in the same basket in case something crashes but Im not sure how the database structure is on whether I have redundancy or if I should be scheduling mysql dumps every so often if they are not redundant.

  2. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    each server has its own database and fetches updates from the master-db as ispcsrvX. The root-account is for ispconfig-updates only.
  3. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Nope. If you need one, you have to create one or sxhedule mysql dumps as you mentioned.
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes, they are redundant in a way that the slave server will keep working when the master or another slave goes down. But you will have to do backups of each database as each slave node has only the data that it needs and the master contains all data, so while you have redundancy in the way that servers are not affected by outages of another servers, you still have to backup each database to be able to restore a node in case of a fatal system error.

Share This Page