Mirroring ISPConfig with DRBD
I have two servers that im trying to cluster togheter for high availability, and i am having trouble replicating all the ISPConfig data.
We installed ispconfig on both servers from the /home/install_ispconfig. This because /home is the directory we will be mounting for data replication using drbd. We are also using ultramonkey for the heartbeat.
With only the heartbeat running (drbd is not running) we can get to the ispconfig admin login page and log in, on a virtual ip created with the heartbeat config files.
When we take node1 offline, node2 comes on and picks up a little later and works fine.
So far so good.
Now, we enter information in ispconfig, create some websites, email users... in node1 and we want the data to replicate to node2. We start drbd mount our mirrored devices and again we are able to reach ispconfig page, log in, we can get to webmail, etc... everything works good. This with node1 as primary and node2 secondary.
Then, we take node1 offline, do the process needed to mount the mirrored device on node2 and make it primary, and all of the sudden nothing works.
My take on it is that we need to mirror other directories that hold the websites, email, webpages, etc.... that are not being mirrored.
Now, my question is, does anyone know what directories to mirror to get this to work?
Will i have to do the changes that i do to ispconfig on both servers? cause, that kind of defeats the purpose.
I would appreciate any information that anyone can give me.
You should also mirror the config files of Apache, your FTP server, Postfix/Sendmail, Bind, etc... Also /etc/passwd and /etc/shadow, the MySQL databases, the directory where ISPconfig creates the web sites in (this is /home/www by default, unless you chose something different during installation).
Generally, ISPConfig configures the services like apache, bind postfix etc. trough their config files. If you want to mirror ISPConfig, you will have to mirror these config files and the ISPConfig mySQL database too. The config files are:
Vhost_ispconfig.conf (in /etc/apache/vhosts or similar)
/etc/passwd, /etc/shadow, /etc/group /etc/gshadow
named.conf and all the include files.
problematic might be the system quotas too.
I dont know what happened to the apache logfiles for ISPConfig, written in /var/log/httpd/ and the proftpd xfer.log
If you switch to the second server, any service must take care that the services on this server has loaded / reloaded their config files.
Maybe this is an interesting solution for ISPConfig high availability.
But I#ve not tested it yet.
Thanks for the info, i will try to implement it. Also, in case we need to consider openssi, does anyone know if the RH 9 version works on FC4?
Anyone already tested ispconfig with openssi?
|All times are GMT +2. The time now is 13:34.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.