Duncan Sterling wrote:
Greetings All,
Quick question: in the interest of redundancy and quick disaster
recovery, would it not make sense while running a production toaster to:
1) Build an identically configured backup toaster
2) Run (Jakes?) backup script daily on the production toaster, backing
it up to the the backup toaster
Thereby allowing near instant recovery in the event of HW/sotware
failure on the production box?
In the past, for ISPs, I've used some type of shared filesystem (usually
NFS using 2 servers running DRBD and heartbeat) and then configured 2+
Qmail systems to act as front ends using the shared backend filesystem
(most of the config files, and the mail store). Then you have 2 servers
that you can DNS-round-robin, and it's trivial to plug more in as load
increases.
Although what you're suggesting WOULD work. The biggest things is always
sharing the mysql DB, but there's several ways to do that depending on
your conditions.
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
