Kerio Connect Multi-Server is a distributed architecture solution designed for easy scalability.
All users access their Kerio Connect account through a single server address, regardless of their home server. The connection is directed to the user's server automatically.
Use Kerio Connect Multi-Server in any of the following scenarios:
- Large on-premise installations to reduce the load and improve the Kerio Connect performance.
- Distributed server environments to use a single domain and a single URL to access the mailboxes.
- Kerio Cloud Solution Partner hosting your own Kerio Connect Cloud environment to distribute users across multiple servers.
All architectural components of Kerio Connect Multi-Server are available and ready to use. However, note the following functional limitations:
- Users can see shared folders across all servers only in Kerio Connect Client and with Kerio Outlook Connector (Offline Edition). To enable sharing, set the
EnabledFolderSharingvariable of the
MultiServertable in the mailserver.cfg configuration file to
- Users cannot share public folders across the servers.
- The Greylisting service is not available.
- IP address groups in user access policies are available only for HTTP/HTTPS.
Kerio Connect does not support redundancy outside of the multi-server deployment, however, you can set up the redundancy at DNS level. You would need to set up 2 separate hardware servers, with the first one being mirrored into the redundant server, so that all emails are copied over to the backup server, this way, in case of failure, the users will still have access to their emails.
The particular difficulty in achieving this would be that all users would have to use the hostname or FQDN to connect to the server, and not the internal IP address so that they connect to the online server, and the DNS provider should be able to supply you with a DNS failover type of service, in order for the DNS records to be updated when the main server is down.
Unfortunately, the above-described setup would be out of Support scope, as it would all come down to the DNS provider supplying you with the appropriate services in order to comply with this type of setup.