<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 11.04.2019 um 11:48 schrieb luckydog xf <<a href="mailto:luckydogxf@gmail.com" class="">luckydogxf@gmail.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">As your statement, nothing speical is needed to do except setting up DNS MX records, right?</div></div></blockquote><div><br class=""></div><div>MX records are for incoming MAIL:</div><div><br class=""></div><div><a href="http://yourdomain.com" class="">yourdomain.com</a> IN MX 100 mail1<a href="http://server1.yourdomain.com" class="">.yourdomain.com</a></div><div><a href="http://yourdomain.com" class="">yourdomain.com</a> IN MX 100 <a href="http://mail2.yourdomain.com" class="">mail2.yourdomain.com</a></div><div><br class=""></div><div>-> both priority 100 = 50/50 load balancing (globally, not when checked on a single resolver!)</div><div><br class=""></div><div>Then you need A Records (AAAA for ipv6)</div><div><br class=""></div><div><div><div><a href="http://mail1.yourdomain.com" class="">mail1.yourdomain.com</a> IN A 192.168.10.1</div><a href="http://mail2.yourdomain.com" class="">mail2.yourdomain.com</a> IN A 192.168.20.1</div><div class=""><br class=""></div></div><div><a href="http://mail.yourdomain.com" class="">mail.yourdomain.com</a> IN A 192.168.10.1</div><div><a href="http://mail.yourdomain.com" class="">mail.yourdomain.com</a> IN A 192.168.20.1</div><div><br class=""></div><div><br class=""></div><div>mail1/mail2 is for direct connection (MTAs)</div><div><br class=""></div><div>Your users (outlook, thunderbird, ...) connect to <a href="http://mail.yourdomain.com" class="">mail.yourdomain.com</a> which returns the two ip addresses.</div><div><br class=""></div><div>In this scenario MUA just connects to <a href="http://mail.yourdomain.com" class="">mail.yourdomain.com</a> and randomly uses one of the two ips. You can't control which one, but this gives you active/active loadbalancing.</div><div>In case one server is down the MUA just uses the other ip. dsync replicates bi-directionally so that both servers are up-to-date.</div><div><br class=""></div><div>You don't need shared storage, every server is a copy of the other. If you want to use shared storage, then dsync is not for you because there is nothing to sync at that stage.</div><div><br class=""></div><div>I would use shared storage only if you need to have more than two servers. The above setup has no locking problems and is performant due to local filesystems.</div><div>It depends on how many users you have and how much storage you need. You could buy two 2HE servers with 24 2.5" disks each (up to 96 with 4 HE), which may be sufficient for your needs.</div><div><br class=""></div></div><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class="">User's mail store is running on shared storage, basically user's MUA connects to primary MX , the backup one is used once Primary is down.</div></div></div></div></blockquote><div><br class=""></div><div>If you're not using Maildir beware of locking issues with concurrent access. It could crash indices.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class="">It's a native HA of email system? I'll test those solution out.</div></div></div></div></blockquote><div><br class=""></div></div>Yes, it works well with small setups. For big setups you'd typically use dovecot director, shared storage, object storage ... but you need more servers and it is way more complex and expensive.<div class=""><br class=""></div><div class="">Best regards</div><div class="">Gerald</div></body></html>