Quote:
Originally Posted by uday277 That's because the locations are remote where the connectivity is not very stable.
The idea is whenever the connectivity is down at least the branch users should be able to communicate and use the ZCS. Whereas the mails destined to the outside world / other branch would que up and transferred as soon as the links are up. |
OK, I understand.
A mutli-server Zimbra installation needs to be colocated (or have very fast and solid WAN connectivity), and Zimbra doesn't support replication across WAN links, so this is going to be hard to do with just one domain across three locations with independent Zimbra servers in each location.
One alternate, easy-to-setup-and-administer way to do this is to use entirely separate domains for each branch office, keeping the Zimbra servers totally separate of each other.
For example,
user1@branch1.yourdomain.com,
user1@branch2.yourdomain.com,
user1@branch3.yourdomain.com.
Users would log in to their own respective Zimbra servers regardless of their location.
But... I can't help but wonder if everyone wouldn't be happier upgrading the branch office connectivity, perhaps using the budget for the two additional Zimbra servers to pay for that?
Or, users at the remote branch offices could use Zimbra Desktop or the Outlook Connector and you could put those extra 100 users on your existing server.
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