Later this week I’ll be attending the AWS Summit in New York City. As big a fan as I am of AWS for Zimbra hosting, there are a number of circumstances where hosting on-premises is as, if not more, appropriate than hosting in The Cloud. Regardless of Where you host, you still need a Disaster Recovery plan to cover “What happens if the data center is offline for an extended period of time?“. That’s where running Zimbra across multiple data centers using my Zimbra Hybrid Architecture Plan can help to lower your Disaster Recovery planning costs and shorten your RPO/RTO targets.
There are many examples of a single Zimbra multi-server system working across multiple data centers. I live-migrated a Zimbra Hosting farm across two data centers years ago over a few months with no end-user service interruption (except for a quick 15-minute downtime for the final evacuation of the old data center). One company I know runs a single Zimbra hosting farm across multiple data centers around the globe, with LDAP, MTA, Proxy and mailbox servers sprinkled across all of these data centers spanning more than half a dozen time zones.
For companies with under, say, 50K mailboxes the usual Zimbra deployment is in a single data center, with some sort of Disaster Recovery environment in a second data center combined with a data transfer mechanism suitable for the company’s budget and RPO/RTO targets.
My key goal in attending next week’s AWS Summit is to vet the draft Zimbra Hybrid Architecture Plan I’ve been working on, and which I intend to publish here. My Zimbra Hybrid Architecture Plan will show you how to run Zimbra across two (or more) data centers, so as to provide cost-effective Disaster Recovery in the event your Primary data center is destroyed or goes offline for an extended period. A choice of RPO/RTO targets will also be provided at different price points, so you can decide for yourself how much “insurance” you want to buy.
If you’d like to get a copy of my Zimbra Hybrid Architecture Plan when it is ready, just fill out the form below.
Hope that helps,
L. Mark Stone
Mission Critical Email
5 July 2019
The information provided in this blog is intended for informational and educational purposes only. The views expressed herein are those of Mr. Stone personally. The contents of this site are not intended as advice for any purpose and are subject to change without notice. Mission Critical Email makes no warranties of any kind regarding the accuracy or completeness of any information on this site, and we make no representations regarding whether such information is up-to-date or applicable to any particular situation. All copyrights are reserved by Mr. Stone. Any portion of the material on this site may be used for personal or educational purposes provided appropriate attribution is given to Mr. Stone and this blog.