I have a datastore that is used just for the swapfile of all our VMs. I have created a number of workload placement policies but am getting misconfiguration errors. Is there a way to exclude this datastore from being monitored?
I'm guessing you may have already attempted the policy above and you're still getting misconfiguration errors. When you create that policy, VMTurbo thinks "Oh, those VMs have a drive on the swap storage! I'll move them away right now." Which I don't think is the behavior you want. You want those swap drives to remain on the swap datastores and the other VM drives to remain amongst the other datastores. Let's try this:
1) Remove the VM workload placement policies you've already created to solve this problem so we can start fresh.
2) Create a new custom group that contains just the swap datastore.
3) Go to Analysis > Storage > Expand "My Groups" > Select your group > Check "Lock VMs to Datastores"
4) Click "Apply settings change" and wait about 30-60 mins. The misconfiguration messages should eventually disappear.
VMTurbo now always keeps the VMs' drives within the datastore group (in this case it's just the swap datastore) and prevents other VMs' drives from coming into the group.
Please let me know if that works!
Here are the steps to create the policy you want:
1) create a group VMs by Storage not equal to the name of the swap datastore
2) create a group that is storage by name - manually select the swap datastore so it is the sole member of the group
3) workload placement policy - do not place VMs from group 1 on provider group made in number 2
Please let me know if this helps and we're happy to walk through this with you!
Thanks Anson, yes that didn’t really work. This is what I have so far.
This is what I am trying to do. We aslo have a Cluster called EMS with its VMs needing to stay on Prod_xx and SRM_xx datastores.
I did that and will wait.
Retrieving data ...