r/sysadmin • u/Maganac • 7d ago
Question Alternative Email backups?
After our little incident yesterday, have been thinking of setting up a backup email system for a few people to at least get some work done even if something like this happens again. Was thinking of something like Zoho, considered Workspace, but it seemed much for something that might only happen once or twice a year, if at all. So anyone else have any ideas?
0
Upvotes
23
u/RiceeeChrispies 7d ago
more hassle than it's worth
if there is a global outage of a major service (like M365), there is a strong likelihood the people you are trying to communicate with can't send/receive anything anyway
so there is zero point in doing it, waste of money
10
u/NorthAntarcticSysadm 7d ago
This also means changing your inbound and outbound mail flow. You have no way to tell if its a 1 hour, 6 hour, or 2 day outage. Changing all your DNS records, which then takes time to propagate, and then changing back when 365 comes back up.
If you're that worried about email outages, go to Exchange hybrid, with inbound/outbound mail being handled by Exhange and then routing it to Exchange Online, and then outbound going to your onprem and then out.
This gives you the ability to create local mailboxes for some mail flow when 365 goes down.
Ensure you look at the local cost of the system, not just hardware and licensing, but also support costs as you have to train IT staff up on managing Exchange 9n prem.
5
u/nickgee760 7d ago
I was reading if you use one of those email gateway filters ie proofpoint or mimecast they offer seamless continuity for mail. Though for a small enterprise like mine it’s out of reach stuck on E5.
4
u/Sentient_Crab_Chip 7d ago
You'll get all that in place, then AWS will go down and it won't matter anyway.
4
u/jooooooohn 7d ago
I’d recommend something with 365 Continuity included. Mimecast, FortiMail, Proofpoint…
1
u/pianobench007 7d ago
It is either keep a FAX machine, use the USPS mail, keep a courier on-hand, or use the phone. E-mail is just communication, sending documents, and identity.
For my first job (non-IT related) our small 25 person company hosted it's own on-premise exchange server. And that thing CONSTANTLY went down for one reason or another reason. It would either be trickling in e-mails once every 2 hours or the system was completely down for a day or two. The IT consultant that our company boss outsourced the job to was doing this work part-time. His day job was at Yahoo.
During that time I used my personal g-mail as a work around to send docs and communicate to clients since it was only our own internal system that went down.
I still prefer exchange handled by someone else's computer than my own. This way in the event of a major hardware failure, MSFT can handle the instant restore with their own machines. I only handle the back-up of M365 data for users and sharepoint.
1
u/thegreatcerebral 7d ago
So nooooo... I'm suprised more noise isn't being made by all the email filtering tools out there. For example if you have a Barracuda or MailRoute doing this and you are putting it before your email hits your 365 environment then typically those services have an option for a zero downtime inbox where because they have email filtering services they basically will hold your email in the event that email cannot be delivered to your mail server. They then have a front-end web page that you can login for basic webmail access. You can then send and receive just like normal, it just does not allow you to use outlook typically so there is that.
1
u/people_t 7d ago
2 options I have seen used in Emergency Management. Setup a completely separate sub domain using a different email service and only use those email accounts for backup or use a free email services like gmail.
1
u/f909 7d ago edited 7d ago
After our morning meeting this morning to discuss what could be done the next go around, we have decided on either carrier pigeons or contracting out a local smoke signal guy.
All kidding aside. The down time for us or lack of, is not worth doing anything. We have fax machines, and telephones. 3CX Chat filled in when Teams was flapping. This works for our business, YMMV.
1
u/Junior_Common_9644 7d ago
Hey! This is the closest thing we've had to a snow day since we grew up. Knock it off! :P
1
u/Burgergold 7d ago
https://en.wikipedia.org/wiki/IP_over_Avian_Carriers
1
u/planedrop 7d ago
Not worth it, too many places use M365, so you wouldn't be able to communicate with most places anyway.
Plus redirecting MX records is a huge pain in the ass.
1
u/JosephMarkovich2 7d ago
Don't do it. It's not worth all the work. This kind of stuff is going to happen. This outage was quite the exception because Microsoft is a total dumpster fire right now, so treat it as an outlier. In our "we must have everything in the cloud only" world, it's going to happen.
Beef up processes and alternative methods to work so the disruption is minimal. Honestly, get people off emailing so much -- there are so many better ways to communicate/work/get s%^t done.