Due to requirements or constraints it might be necessary to exclude a virtual machine from automatic migration and stop it from moving around by DRS. Use the “Partially automated” setting instead of “Disabled” at the individual virtual machine automation level. Partially automated blocks automated migration by DRS, but keep the initial placement function. During startup, DRS is still able to select the most optimal host for the virtual machine. By selecting the “Disabled” function, the virtual machine is started on the ESX server it is registered and chances of getting an optimal placement are low(er).
An exception for this recommendation might be a virtualized vCenter server, most admins like to keep track of the vCenter server in case a disaster happens. After a disaster occurs, for example a datacenter-wide power-outage, they only need to power-up the ESX host on which the vCenter VM is registered and manually power-up the vCenter VM. An alternative to this method is to keep track of the datastore vCenter is placed on and register and power-on the VM on a (random) ESX host after a disaster. Slightly more work than disabling DRS for vCenter, but offers probably better performance of the vCenter Virtual Machine during normal operations.
Due to expanding virtual infrastructures and new additional features, vCenter is becoming more and more important for day-to-day operational management today. Assuring good performance outweighs any additional effort necessary after a (hopefully) rare occasion, but both methods have merits.
VM settings: Prefer Partially Automated over Disabled
51 sec read
I’ve found that DRS Groups Manager in 4.1 all but eliminates the need for disabling (or partially automating) DRS on our VMs. We place vCenter in a two node group so it would be easy to find after a disaster. Where we have mixed HW clusters specific VM’s can be tied to the faster hosts they require, but still have the efficiencies of DRS and a bigger cluster. Exchange 2010 mailbox servers with DAG’s are the only VM’s where we must limit DRS. Of course based on your article, those will now be “Partially Automated”…
For a virtualized vCenter, we placed an affinity rule that said the vCenter should run on host[A] unless the host goes offline. It has proven to be most helpful, since we can always determine where the vCenter is located.