Eric Dahnke wrote:
> Hello List,
>
> We have a server moving about 9000 msgs per day and want to have a
> second qmail server waiting on our network to take over in the event of
> a failure.
>
> Our current thinking is:
>
> - an identical qmail installation on a backup machine
> - daily copy of /home /control and /alias to backup machine
> - in the event of a massive failure unplug the ethernet from the main
> server and plug into the backup machine.
>
> (I realize we will lose the queue --normally just full of waiting
> bounces-- and all msgs received for local users since the last backup)
>
> My question is, will there be any implications "Out_There" of suddenly
> having a new IP and hostname for our mailserver, assuming we make the
> appro DNS changes?
>
> Any other comments on this kind of idle machine waiting backup scheme?
> (the main mail server is dpt raid fived)
>
> cheers - eric
Why don't you just set up your second server as an MX server and use the
handy dandy MX routing feature in named to automatically reroute mail in
the event of a failure. The MX server will hold all the messages while you
repair your server and automatically resend them when everything is back
online.
This is probably the perfect solution for you, *especially* since you have
a raid 5. Don't be looking for a harddrive failure anytime soon :) Your
harddrives are the only irreplaceable components because they contain your
data, so anything else could be repairable in the time it takes you to
scrounge up the hardware.
--
Cris Daniluk [EMAIL PROTECTED]
-------------------------------------------------------------
Digital Services Network, Inc. http://www.dsnet.net
1129 Niles-Cortland Road, Warren, Ohio 44484 [EMAIL PROTECTED]
(330) 609-8624 ext. 20 Fax (330) 609-9990
The Web Hosting Specialists
-------------------------------------------------------------
