Rebalance: A desktop rebalance operation that evenly redistributes linked-clone desktops among available datastores.
When testing this, customers can often see unexpected results. This is often due to their misconception of how this function of View works.
Why? View 4.5 looks for the datastore/s that have the highest "weighted available space". The formula that View 4.5 uses to calculate this is:
weighted_available_space = datastore_capacity * overcommit_factor – virtual_usage
datastore_capacity = As you would expect, the size of the datastore.
overcommit_factor = The Storage Overcommit setting applied to each datastore when selecting which datastores to use for your desktop pools.
Conservative – x4 the size of the datastore. (This is the default level.)
">virtual_usage = The maximum possible usage of all existing VMs on this datastore, which is calculated by adding up current sizes of all disks and configured sizes of memories of all existing VMs on the datastore.
Examples
Common Scenario
You have a desktop pool with DS1 as it's only datastore. You then decided to add a second datastore, DS2. You perform a Rebalance on the pool to spread the VM's across the two datastores, but nothing happens… Why? Because DS2's weighted_available_space is less than that of DS1's.
Summary
As you can see, by default you may not get your desired effect. But with a little bit of maths you can get the reaction you want from the Rebalance feature. I must stress, this is only for VMware View 4.5 and older.
Another VMworld is upon us!!! Sadly, it's only virtual again this year. However, that does…
As part of my recent move to Google, I'm working on quickly getting up to…
I am delighted to announce the next chapter in my career. Today is my first…
In episode thirteen of The VCDX Podcast, I am joined by two special guests who…
In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…
In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…