In one of the previous blog post, we discussed about vSAN Policies. In this post, let's have a quick look at the vSAN Default Storage Policy.
The VM's running on a vSAN Datastores must have at least one storage policy assigned to it in order to function. If you don't specifically assign a storage policy to a virtual machine when provisioning it, the vSAN Default Storage Policy is assigned to the virtual machine. The default policy typically used for the placement of virtual machines deployed on vSAN datastores includes vSAN rule sets and a set of fundamental storage capabilities.
vSAN Default Storage Policy Specifications
You can review the configuration settings for the default virtual machine storage policy when you navigate to the VM Storage Policies > vSAN Default Storage Policy > Manage > Rule-Set 1: VSAN. VMware recommends to consider creating and using your own VM storage policies, even if the requirements of the policy are same as those defined in the default storage policy.
The vSAN Default Storage Policy has the characteristics listed below.
1. If you do not specify any vSAN policy when you provision a virtual machine, the vSAN default storage policy is applied to all virtual machine objects.
2. The default policy cannot be deleted.
3. The vSAN storage provider specification as well as the default policy's name and description cannot be changed. The policy rules as well as all other parameters are changeable.
4. You can clone the default policy and use it as a template to create a user-defined storage policy.
5. Only vSAN datastores are covered by the vSAN default policy. NFS or VMFS datastores, which are not vSAN datastores, cannot use the default storage policy.
I'll conclude this post here in order to keep things brief.
In the upcoming blogs we will discuss more on applying a storage policies to a VM.
Thank you for reading!
*** Explore | Share | Grow ***
Comments