Massimiliano wrote:

Hi !
I'm now using a Qmail Server for handling about 40 e-mail accounts . My boss asked me today to raise the "availability level " of the server next to 100% because the e-mail service is getting for my company more and more important so my obvious conclusion is that I'll need another Qmail server . The question is : how shall I setup the main Server ( let's say qmail01) in order to automatically route all the incoming e-mails to the qmail02 ? In the case of a crash , the only thing i'd have to do is changing the port-forwarding (25 SMTP) on my firewall changing from IP qmail01 to IP qmail02 and tell users to use the new mail server through squirrelmail
thanks

A while ago someone had talked about using heartbeat and a mysql sync-ing package that would do what you're asking. What I use here is a backup caching mail server (QMT install with the domains added into /var/qmail/control/rcpthosts and NO users or domains added to it), with a queuelifetime of 5 days and an MX priority of 20 (main server has a 10). That way, if the main server goes down for some reason, the backup will still accept the messages, and try and deliver them to the main server for 5 days before it gives up and bounces them back to the sender. I then run the backup script I've put together on the main server, sending the backup file to the backup server every night. If the main server has a complete hardware crash, I can rebuild it and restore QM on it within the 5 day time-limit and the backup server will then deliver all the mail it's been holding to the main one once it's back online. Worst case is that 6-12 hours of emails are lost during the wee hours of the morning (low traffic anyway). That has worked for me, and I didn't see a real need to go through the whole process of setting up heartbeat and sync'ing the database/directories all the time, plus I can still use the backup server to do things such as FTP and serving other webpages.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to