How to create new VxRail vSAN storage policy in 6.7 U3

Posted by

When you stand up a new cluster you may have storage requirements besides just the default vSAN storage policy.  Since the screens have change slightly 🙂 between 6.5 and 6.7 update 3 I thought I would take a moment for a high level walk through of creating a new storage policy.

Go to Menu >  Policies and Profiles

Machine generated alternative text:
Menu v 
Home 
O Search in all environme 
ctrl + alt + home 
Shortcuts 
Hosts and Clusters 
VMS and Templates 
Storage 
Networking 
Content Libraries 
ctrl + alt + 1 
ctrl + alt +2 
ctrl + alt +3 
ctrl + alt + 4 
ctrl + alt +5 
ctrl + alt +6 
Global Inventory Lists ctrl + alt + 7 
Policies and Profiles
Machine generated alternative text:
Policies and Profiles 
VM Customization Specifications 
VM Storage Policies 
Host Profiles 
Storage Policy Components 
VM Storage Policies 
Create VM Storage Policy 
Name

VM Storage Policies > Create VM Storage Policy

Machine generated alternative text:
Create VM Storage Policy 
1 Name and description 
2 Policy structure 
3 VSAN 
4 Storage compatibility 
5 Review and finish 
Name and description 
vCenter Server: 
Name: 
Description: 
DALPRDESXVIC02_FREEMANCO.COM v 
R5 FTTI DSI T? 
Raid-S 
Fault Tolerance 1 
Disk 1 
Thin provisioning 
CANCEL 
NEXT

Give it a name – my method is to name it for what the policy will do

Machine generated alternative text:
Create VM Storage Policy 
2 
3 
4 
5 
Name and description 
Policy structure 
VSAN 
Storage compatibility 
Review and finish 
Policy structure 
Host based services 
Create rules tor data sewices provided by hosts. Available data services could include encryption, I/O control. caching, etc. 
Host based services will be applied in addition to any datastore specific rules 
Enable host based rules 
Datastore specific rules 
Create rules tor a specific storage to configure data services provided by the datastores. The rules will be applied when 
VMS are placed on the storage type. 
e 
Enable rules for "vSAN" storage 
Enable tag based placement rules 
CANCEL 
BACK 
NEXT

Every environment is different so shape it to what best fits your environment.

Machine generated alternative text:
Create VM Storage Policy 
vSAN 
Availability Advanced Policy Rules 
Tags 
2 
3 
4 
5 
Name and description 
Policy structure 
VSAN 
Storage compatibility 
Review and finish 
Site disaster tolerance @ 
Failures to tolerate @ 
None - standard cluster 
1 failure 
No data 
1 failure 
1 failure 
- RAID-I (Mirroring) 
redundancy 
oe 200 Ga 
- RAID-I (Mirroring) 
- RAID-5 (Erasure Coding) 
2 failures 
2 failures 
3 failures 
- RAID-I (Mirroring) 
- RAID-6 (Erasure Coding) 
- RAID-I (Mirroring) 
CANCEL 
BACK 
NEXT

I am leaving site disaster tolerance to none – standard cluster because this policy won’t be used for stretch clusters or nested fault domains

Since my example is a Raid-5 with 1 failure I have selected 1 failure – RAID-5 (Erasure Coding)

Machine generated alternative text:
Create VM Storage Policy 
1 Name and description 
2 Policy structure 
3 VSAN 
4 Storage compatibility 
5 Review and finish 
vSAN 
Availability Advanced Policy Rules 
Number of disk stripes object @ 1 
Tags 
'OPS limit for object @ 
Object space reservation @ 
Flash read cache reservation (%) @ 
Disable object checksum @ 
Force provisioning @ 
Thin provisioning 
Initially reserved storage space for ICO G3 VM disk would be O 
o 
Reserved cache space for IOOGS VM disk be O a 
CANCEL 
BACK 
NEXT

Under Advanced Policy Rules I am leaving everything default because I selected Thin provisioning and Disk Stripe to 1

However, if I wanted to thick provision this policy due to say a vendor requirement then I would change Object space reservation to Thick provisioning

If I wanted to spread the objects across more capacity drives for increase performance I could change the number of disk stripes per object to 2 or more

Machine generated alternative text:
Create VM Storage Policy 
2 
3 
4 
5 
Name and description 
Policy structure 
VSAN 
Storage compatibility 
Review and finish 
vSAN 
Availability Advanced Policy Rules 
Tags 
Add tag rules to filter datastores to be used for placement of VMS. 
ADD TAG RULE 
CANCEL 
BACK 
NEXT

I am not adding TAG rule for my example but these can be very useful.

Machine generated alternative text:
Create VM Storage Policy 
1 Name and description 
2 Policy structure 
3 VSAN 
4 Storage compatibility 
5 Review and finish 
Storage compatibility 
compatible storage 139.73 TB (85.41 TB tree) 
Compatible 
Expand datastore clusters 
Name 
VxRaiI-Non-Prod-vSAN-Datas 
tore 
Datacenter •r 
Richardson 
Type 
vSAN 
Space 
85.41 Ta 
Capacity 
13973 TB 
CANCEL 
Wamings 
BACK 
NEXT

Next shows the compatible storage in your environment based on your selections.

Example: if I had only 3 hosts contributing storage to my vSAN datastore then no datastores would appear as compliant storage because R5 erasure coding requires a four host minimum.

Machine generated alternative text:
Create VM Storage Policy 
2 
3 
4 
5 
Name and description 
Policy structure 
VSAN 
Storage compatibility 
Review and finish 
Review and finish 
General 
Name 
Description 
vCenter Server 
VSAN 
Availability 
Site disaster tolerance 
Failures to tolerate 
Advanced Policy Rules 
Number of disk stripes object 
'OPS limit for object 
Object space reservation 
Flash read cache reservation 
Disable object checksum 
Force provisioning 
Raid-S Fault Tolerance 1 Disk Stripe 1 Thin provisioning 
dalprdesxvic02_freemancocom 
None - standard cluster 
1 failure - RAID-I (Mirroring) 
Thin provisioning 
CANCEL 
BACK 
FINISH

Click finish and the new policy will be generated

Summary:
As you can see from the above creating a new storage policy has become less complex and more wizard driven.  I do enjoy the cleaner interface.  I hope this helps anyone trying to create a new policy to fit the workload you intend to support.  As always, I hope y’all found this article useful.

Leave a Reply