I have a recommendation to move a server to a host on a cluster it doesn't currently reside on.
That's not supposed to happen, right?
The second one you can do pretty easily by creating a custom group of the vCenter servers in Policy>Group Management then you would just need to use regex to identify the vcenter vms (.*vcenter.* for example). Then under actions just set move to disabled.
The first one should not happen without you telling VMTurbo to do it. I would recommend opening a support ticket to look into it.
If you have VMM and they're both Hyper-V hosts managed by that VMM target, then it's expected because VMM allows you to disregard the Cluster boundary.
Likewise, VMTurbo has a "Merge cluster" Workload Segment that you can create to tell VMTurbo to ignore cluster boundaries between two clusters that you can configure.
Any chance either of these is what you're noticing?
We definitely don't have any Hyper V hosts or VMM. I don't remember configuring anything in the Workload segment to merge cluster. Where is this found, in Policy?
A couple of things on my wish list for automated workload balancing.
1. The ability to stop vms from being moved to a host that is not in a cluster. When I have a host that is having issues I want to be able to remove it from a cluster to test it, I end up having to turn off automatic moves when I do this.
2. The ability to exclude specific vms from being moved, I'd like my Vcenter servers to stay on one host except in the case of a host failure. It's very helpful to know which host your Vcenter server is on if it fails.
Maybe these can be configured with Workload segments?
Retrieving data ...