How to Confine Virtual Disks to a Group of Datastores

Document created by will.schnoor on Jul 27, 2016Last modified by fran.schwarzmann on Aug 15, 2016
Version 3Show Document
  • View in full screen mode

In this tutorial we'll cover how to confine vmdks to a group of datastores. This will be useful in several scenarios. Most notably, if you are using vSphere Standard edition, you cannot create storage clusters in your VMware environment. Therefore, any business policies that limit the datastores from which a VM can consume are typically enforced manually, or through scripts that administrators create. These policies create additional constraints, and additional trade-offs, that need to be considered while trying to manage performance.


So how do you make VMTurbo aware of these constraints? It's actually a simple, two-step process.


First, you need to identify the group of datastores to which you want to constrain VMs. You can use either default groups for this, like the datastores that have been presented to a particular cluster, or you can create custom groups. If you want to create a custom group, please see the below document on how to create groups within VMTurbo.


How to Create a Custom Group (v5.4+)


For the second step, you need to navigate to the Policy tab (along the top of the interface), drop down Analysis on the far left, select Storage, then find the group of datastores which you have identified. After selecting that group, click on the "Lock VMs to Datastores" option and select Apply Settings Change.



That's it! You're done. Within about 20 minutes, you will see the actions which VMTurbo has identified reflecting your new policy. You should expect to see any vmdk that currently resides within that group stay within the group.

1 person found this helpful