Welcome to our community!

High Availability / Active-Active Load Balancing

Sol

9 years ago
updated 3 years ago
Considering for Future Release

Hi all,

It would be nice to have some built in functionality and support for High Availability scenarios. We run over 5000 unattended sessions, and when there are issues or updates that means downtime to our business.

Basic HA would be relatively easy to accomplish on Windows by utilizing Windows Failover Clustering. This would likely work already but not be officially supported.

Cross platform and active-active Clustering could be achieved by leveraging a load balancing service or system and allowing for some basic communication between cluster nodes such as service status and settings replication.

Replies 9

Oldest first
Newest first Oldest first

anonymous

9 years ago
Pending Review

Reply Link

Avinash Sukhandan

8 years ago

We running quite a lot of agents and having SC go down for a moment is tough, need to have a HA option.

Reply Link

Cody Arnold

8 years ago

I second this.

This is a much needed feature.

Reply Link

anonymous

8 years ago
Considering for Future Release

Reply Link

VertigoRay

7 years ago

This is a very much needed feature. Would be great of CW Control would just run in a docker instance and I could just tell Kubernetes how many nodes I needed. I'm sure I could get it going. I just haven't had time to sit down and make it happen yet. Would likely need a key per node with CW Control's current license structure, but that's something we'd be willing to handle for a little HA. ;)

Reply Link

Will L

5 years ago

This is still a very important feature that is needed.

Reply Link

Joakim

4 years ago

To the decision makers of ConnectWise Control features. This feature is a must have for large customers with many sites around the world. We would like to have a connectwise server in each region, APAC, AMER, EMEA.

Reply Link

Rhys Comley

3 years ago

Agree, this feature is required, distributed relays to reduce round trip latency - as a result improving overall performance for all regions.

The primary challenge with the current architecture is single server deployment (deployed to a single region) results in round trip latency of up to 300ms for some regions and a very poor user experience.

In addition, database server redundancy is desirable.

Reply Link