Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-13-2009, 06:02 PM
Elite Member
 
Posts: 377
Default Backup MX?

I know we can set a secondary MX record that will take over the primary MX when the primary email server failed. The question is, when the primary email server is up, there will be email getting into the secondardy email server during the period the primary email server was down, so how do the email client download email from the secondary email server without having to amend their POP?

Not to mention that amending POP will lead to redownloading of all email again. Luckily Zimbra has the option to select download email from now on. A very useful feature.

How do you guys setup a backup email server when the primary failed? Do you use MX record with lower priority too?
Reply With Quote
  #2 (permalink)  
Old 12-13-2009, 11:55 PM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

A quick search would have found this: postfix mackup mx - Yahoo! Search Results
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 12-14-2009, 01:39 AM
Elite Member
 
Posts: 377
Default

Does this mean that we should use postfix instead of zimbra for this purpose?
Reply With Quote
  #4 (permalink)  
Old 12-14-2009, 03:56 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

Quote:
Originally Posted by bhwong View Post
Does this mean that we should use postfix instead of zimbra for this purpose?
No but it does describe how to set-up a Backup MX which is, I believe, what you were asking. BTW, Zimbra uses postfix for it's MTA.
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 12-14-2009, 05:36 AM
Elite Member
 
Posts: 334
Default

Hi,
Quote:
Originally Posted by bhwong View Post
I know we can set a secondary MX record that will take over the primary MX when the primary email server failed. The question is, when the primary email server is up, there will be email getting into the secondardy email server during the period the primary email server was down, so how do the email client download email from the secondary email server without having to amend their POP?

Not to mention that amending POP will lead to redownloading of all email again. Luckily Zimbra has the option to select download email from now on. A very useful feature.

How do you guys setup a backup email server when the primary failed? Do you use MX record with lower priority too?
I think the best option was using the DRBD + Heartbeat + Zimbra to make an online backup MX. Below is an example :

Howto: Highly available Zimbra cluster using Heartbeat and DRBD | mig5.net
__________________
Best Regards
---
Masim "Vavai" Sugianto
Vavai Personal Blog
Personal Blog [ID]

Release 7.1.3_GA_3346.SLES11_64_20110930001521 SLES11_64 FOSS edition.
Reply With Quote
  #6 (permalink)  
Old 12-14-2009, 07:59 AM
Moderator
 
Posts: 1,209
Default

Quote:
Originally Posted by bhwong View Post
I know we can set a secondary MX record that will take over the primary MX when the primary email server failed. The question is, when the primary email server is up, there will be email getting into the secondardy email server during the period the primary email server was down, so how do the email client download email from the secondary email server without having to amend their POP?

Not to mention that amending POP will lead to redownloading of all email again. Luckily Zimbra has the option to select download email from now on. A very useful feature.

How do you guys setup a backup email server when the primary failed? Do you use MX record with lower priority too?
We configure a separate, off-site plain Postfix server to serve as a backup MX for our production Zimbra hosting farm.

If spammers try sending to the backup MX while Zimbra is up, we don't care, the backup MX cleans the mail just like Zimbra and sends it on if clean immediately to the Zimbra system.

When the Zimbra system is down for maintenance say, other servers trying to send to Zimbra see that Zimbra is unavailable and send email to the backup MX.

The backup MX is configured to try to forward all legitimate email to the Zimbra server farm; if Zimbra is unavailable, the backup MX retries periodically.

To eliminate backscatter and ensure the backup MX only accepts email for valid recipients on the Zimbra system, we run a cron job on the Zimbra system that extracts all valid emails from the system. The output is sent to the backup MX, which runs a separate script that looks for any changes (domains/email addresses added/deleted) and updates the backup MX server's Postfix configuration accordingly and then reloads Postfix.

DRDB it seems from the posts here can also work; but the method above and DRDB are really designed to handle two different Disaster Recovery use cases.

I'd start with the use cases your management needs to address, and then the appropriate solution(s) should be straightforward to determine.

Hope that helps,
Mark
__________________
___________________________________
L. Mark Stone, CIO


"Uptime. All the time."

477 Congress Street | Portland, ME 04101-3431 | (207) 772-5678

proactive maintenance and monitoring | technology consulting
Zimbra groupware | EMR implementations | private cloud hosting
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.