New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2 Mailu servers for redundancy - Best approach #177

Closed
SaiGonSeamus opened this Issue Mar 11, 2017 · 8 comments

Comments

5 participants
@SaiGonSeamus
Copy link

SaiGonSeamus commented Mar 11, 2017

We have two Mailu instances being set up. One in house, one in the cloud to act as a back up.

Is DNS MX the best approach or are there others that are preferable?

I haven't seen anything here on this issue, what are others doing?

Regards

S

@zjr8

This comment has been minimized.

Copy link

zjr8 commented Mar 12, 2017

Im all cloud based at the moment but am currently implementing a high avaliability setup using HA Proxy. It has the ability todo failover routing and supports smtp / dovecot. Still have a few bugs to workout in my config but HA proxy is working with starttls support (ssl is semi working but need to sortout a dovecot auth issues as the HA Proxy is doing ssl termination and confusing dovecot). Postfix is relaying outgoing email through amazon ses to help ensure client email reaches is destination as ive had issue with ec2 ip reputation before. I should note the entire setup works and is easier with an ELB (ssl termination even working) but it doesnt seem to support a method of restoing original ip to dovecot/postfix (which ha proxy does)

@SaiGonSeamus

This comment has been minimized.

Copy link
Author

SaiGonSeamus commented Mar 12, 2017

Thanks for this, this looks like the way to go.

Do you have HA Proxy set up on a separate server in a different geographic region?

Is there some documentation you would recommend on setting up HA Proxy to work with Mailu?

@kaiyou kaiyou added the discussion label Mar 28, 2017

@SaiGonSeamus

This comment has been minimized.

Copy link
Author

SaiGonSeamus commented Sep 19, 2017

We never implemented this at the time but want to put a solution in place now. Has anything changed? Is HA Proxy still the best route to take? Has anyone any suggestions or advice?

@kaiyou

This comment has been minimized.

Copy link
Member

kaiyou commented Sep 19, 2017

It really depends on what your HA requirements are. Do you want to avoid losing any email, do you want to avoid losing the ability to read them? How long can you sustend a service disruption?

@kaiyou

This comment has been minimized.

Copy link
Member

kaiyou commented Sep 24, 2017

Issue #272 could be a first step towards a highly available frontend for multiple backends.

@SaiGonSeamus

This comment has been minimized.

Copy link
Author

SaiGonSeamus commented Nov 4, 2017

We would like to reconfigure our infrastructure to take advantage of this now.

Broadly we're try to address 2 issues with this. Deliverability & Resilience.

Ideally we want our primary backend to reside in our DMZ for security, control, cost etc. We have a KVM cluster with ZFS, RAID, Ceph on the way.

Even though our public IP space is classed as commercial, sometimes foreign networks have it classed as residential adsl with a poor reputation as their data is out of date, there is also a 3 day turnaround from the ISP on adding, removing or changed PTR records.

We now have two separate servers with hosting companies here and one as a test server in the DMZ, we would like to migrate them all to one domain.

We also have had a lot of political interference with hosting companies abroad. they just block SMTP with no warning or notice.

So being able to route mail from a different IP easily, migrate hosts quickly & easily is important.

We are also in a rapidly developing environment that sees real impact of climate change. Occasional power loss from accidents or upgrades to transmission or flooding can't be ruled out.

Being able to switch to a secondary backend for up to 6 hours or so would be ideal.

We were planing on using Portainer to monitor them unless someone can suggest something better.

Anyway, that's a quick run down on the kinds of challenges we face and what we want to address, so you understand where we are coming from.

Wondering how we can get to a situation where we can test a solution and what help we can give to the project to get there.

@benyanke

This comment has been minimized.

Copy link

benyanke commented Sep 16, 2018

I'd also like to run my primary box on my lan, but be able to occasionally flip over to a VPS if required.

@kaiyou kaiyou removed the discussion label Oct 6, 2018

@muhlemmer

This comment has been minimized.

Copy link
Member

muhlemmer commented Oct 13, 2018

I've been playing Docker Swarm on 3 cheap VPS hosts. Docker has it's own routing mesh for traffic distribution / HA. If one of the containers goes down, the user does not feel anything. (Not yet in production, working on it)

For redundant storage, I'm using GlusterFS in a triple-replicated, using data volumes from the same hosts. Since the hosts are cheap, write performance sometimes seem to suffer a bit.

If I will get to the point of having a serious user-base, I'll be just a matter of adding worker nodes to the swarm and glusterFS pool and that's all there is to do for scale ability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment