Can you have multiple vROps clusters

[GKleinow]

We currently have a test\dev instance of vROps 6.1 installed. We are ready to do the install of our production system and one of my colleagues wants to keep the test\dev instance. Would having two different clusters (with two different master nodes) pointing at the same vCenter Server be a problem?

[mark_j]

Nope - go for it. Just know the 'last registered' vR Ops will be the one that is registered in the vCenter Web Client.

If vR Ops is collecting from a 'fully loaded' vCenter Server, as in vCenter is at its product maximums (not many customer are!), you should see a maximum 10% increase in vCenter CPU (assuming the vCenter is sized properly). So, our guidance is to not have more than 2 vR Ops deployments monitoring the same vCenter Server. And be aware tat each vR Ops instance will have between 5-10 maintained connections to that vCenter Server. The # connections depends on the size of your vCenter inventory, and they're maintained user connections that you'll see in vCenter GUI.

[jl99]

In relation to connecting multiple vROPs to vCenter...

Can you also connect multiple vROPs to Horizon?

[dtaliafe]

I'm pretty sure you can't connect multiple vROps to the same Horizon environment.  Unlike the vCenter adapter the Horizon adapter gets most of its data from agents installed in the Horizon environment.  There's a vROps broker agent that you install on the Horizon connection server and it can only be pointed at one remote collector.  There's also an agent on the Horizon View desktops that report to a single vROps collector.