Best Practices for Redundancy in ControlUp Components for VDI Onboarding

A discussion arose about best practices for redundancy of components for new clients onboarded for VDI. It was suggested to deploy at least 2 ControlUp Monitors and dedicated Data Collectors for failover mode, with configuration instructions provided in the relevant EUC / Hypervisors API connection. ControlUp has a sizing guideline for v8.x, found at https://support.controlup.com/docs/sizing-guidelines-for-controlup-v8-x, though it is advised to monitor with ControlUp and scale as needed.

Read the entire ‘Best Practices for Redundancy in ControlUp Components for VDI Onboarding’ thread below:

Good day,

We are onboarding some new clients for VDI and were wondering if there are best practices concerning redundancy of the components.

Is it wise to deploy two of each (Console, Monitor, Data collector) What would happen if one of the components fail? Can we just restore the VM for backup?

If this is CU4VDI Cloud version (e.g. not our On-premises version), indeed we recommend:

1. At least two ControlUp Monitors for redundancy and high availability
2. At least two dedicated agent Data Collectors, they work in failover mode (just need to configure the two data collectors in the relevant EUC / Hypervisors API connection)

https://support.controlup.com/docs/ha-backup

Additionally you might take a peek at the sizing guideline:

https://support.controlup.com/docs/sizing-guidelines-for-controlup-v8-x

ofc your milage may vary – just eat your own dogfood 🙂 and monitor the monitors/data collectors with controlup and scale as required.

thanks for the advice and quick response!

Continue reading and comment on the thread ‘Best Practices for Redundancy in ControlUp Components for VDI Onboarding’.  Not a member? Join Here!