Last week, I wrote an article which described how to use a combination of vSAN Availability Rules with Tag Based Placement Rules in vSAN Storage Policies to select one specific vSAN datastore for object placement when many vSAN datastores might appear as compatible candidates. I create this short 3m30s video to show how to do this in practice.
I was recently working in an environment where my vCenter server was managing two vSAN clusters, each with its own datastore. I wanted to be able to choose which datastore to provision to via storage policy, but came across some unexpected behaviour. When I configured my vSAN Rule and my Tag Rule, it seems that both datastores would appear as compliant to the policy. I found out the reason, and decided to write it up as I had never known this was how policies AND and OR rules behaved until now. Setting up Tags I created a Tags Category called…
I was doing some work in the lab with Storage Policy Based Management recently. I was using both vSAN and a Virtual Volume array from Nimble Storage. While I was able to create independent policies for both vSAN and VVols, I was curious to see if I could create a policy where I could be offered both datastore types for the initial placement of a VM. For example, if I wanted to ensure my VM was encrypted, could I have a policy which would be compliant with both vSAN datastore and the Virtual Volume datastore, so long as they both…