How to Create VMware vSAN Storage Policies

In order to control the behavior of VMware virtual SAN (vSAN) storage, we need to use storage policies. These profiles allow admins to create rules that utilize capabilities advertised by the storage. These rules allow for control over performance or protection levels of a virtual machine on a vSAN datastore. This post will walk through the short process of enabling and creating a new storage profile.

Enabling VM Storage Policies

To get started I’ve logged into the vSphere web client and located the icon for VM Storage Policies. Click on the icon, make sure the service is enabled, and then we can start to configure.

VM virtual SAN vsan Storage Policies

The first step is to enable storage policies on our vSAN cluster. Click the highlighted button as shown in the image below.

Sponsored Content

Devolutions Remote Desktop Manager

Devolutions RDM centralizes all remote connections on a single platform that is securely shared between users and across the entire team. With support for hundreds of integrated technologies — including multiple protocols and VPNs — along with built-in enterprise-grade password management tools, global and granular-level access controls, and robust mobile apps to complement desktop clients.

VM virtual SAN vsan enable Storage Policies


This will open a window that will tell us the current VM storage policy status. If its anything other than enabled we will need to enable. To do this click on the cluster that we want to turn on and click the Enable button.

VM virtual SAN vsan Storage Policies


Creating a Storage Policy

We are now ready to create our first storage policy. We are back at the previous screen and click the icon show to create the policy.

VM virtual SAN vsan create Storage Policies


We can now walk through the wizard. First, enter a name for the policy and write a description. The description will help others understand how the policy should be used.

VM virtual SAN vsan create Storage Policies

We are now ready to create the rule set. The first step is to pick vSAN from the list of vendor capabilities. If you have other storage that supports VASA there might be more than just the vSAN option. For the first rule, select the Number of failures to tolerate. This can be used to adjust how many copies of an object or a VM that we want to have on the vSAN cluster.

You have the option to define multiple capabilities within a single policy. This would be needed if you wanted to enable several storage capabilities on a particular VM, since you cannot apply more than a single storage policy to a VM.

VM virtual SAN vsan create Storage Policies rule set

Now the rule set that was created must be matched to a resource. In this case, the resource is our vSAN datastore that was already created.

VM virtual SAN vsan create Storage Policies rule set

The final step of the wizard is the confirmation screen. This shows the details of the policy we created, listing the rules/capabilities that were selected.

VM virtual SAN vsan create Storage Policies confirmation

Creating storage policies is pretty easy. I don’t see many customers creating policies so far, but I do expect this to become more common. As new storage technologies continue to develop and be more software controlled, I think the need for storage policies will continue to grow.

Related Topics:


Don't have a login but want to join the conversation? Sign up for a Petri Account

Comments (3)

3 responses to “How to Create VMware vSAN Storage Policies”

  1. Is there any way to assign target IOPS/throughput in these storage policies? for example “Gold/Silver/Bronze” based on the IOPS/throughput? That would be great. Maybe Storage DRS /SIOC would help?

    • Alex, Today there is a not a way to control IOPS with these storage policies.

      VSAN does not support SIOC, so other than editing the .vmx file for each VM and enforcing an IOPS limit there is not much to work with right now around your idea.

      • thanks a lot – i didn’t even know it was possible to limit iops through editing the vmx, so thanks for letting me know. I have ordered the “mastering vsan 5.5” book and i will try to find workarounds, like setting the stripe size etc etc. I know it’s hard to implement (It took NetApp a long time, and they just announced it for 8.2), and given that vSAN is a v1.0 product, I am hopeful it might be implemented in the future, along with dedup and compression..

Leave a Reply