How can we improve Kerio Connect?

enable hotbackup/failover for server in seperate location, as so no downtime for users

create feature whereas the kerio connect server at site A has a sister site at site B, so as if server A goes down or becomes unreachable, site B will automatically take up the slack, ensuring uptime/connectivity for users.

for crucial mission critical environments the ability for users to connect to '' and have the round robin dns pick whatever site is up (Site A or Site B) and route accordingly is CRITICAL (for us especially)

112 votes
Sign in Sign in with GFI
Signed in as (Sign out)
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in Sign in with GFI
Signed in as (Sign out)
  • Ronald Otto commented  ·   ·  Flag as inappropriate

    @Kerry Hormann
    - Running in separate datacenters is much harder due to the centralized storage
    - Running on bare metal is still needed
    - Errors on OS or Kerio level are still a problem on a virtualisation cluster. If you OS won't boot, there is no HA that helps when HA needs a working machine.

  • Kerry Hormann commented  ·   ·  Flag as inappropriate

    Wouldn't this be better accomplished via established enterprise-class high-availability features in products like VMware, XenServer, and MS cluster services?

Feedback and Knowledge Base