I love VSAN! Horizon View 6 and VSAN are like a marriage made in heaven, if you create Linked Clone or Full Clone desktops in View 6.0 using VSAN. It automatically adds the default Virtual Machine (VM) Storage Policies to the objects that are created during the desktop pool creation using View Administrator. The objects that get created using the desktop pool creation such as Persistent Disk, Replica Disk etc. automatically add the disk stripe, Flash cache and fault tolerance to each object.
What does that mean? Out of the box, your desktop objects are made highly available and one doesn’t have to go to individual desktops and set VM Storage policies. The following table outlines the View Auto Created out-of-the-box VM Storage Policies available with Horizon View 6 and VSAN:
| Default VM Storage Policies |
No. Disk stripes per object
|
Flash read cache reservation (%)
|
No. Failures to tolerate
|
Object space reservation (%)
|
Desktop Type
|
| VM_HOME_ |
1
|
0
|
1
|
0
|
Linked Clone/Full Clone |
| OS_DISK_ |
1
|
0
|
1
|
0
|
Dedicated Linked Clone |
| REPLICA_DISK_ |
1
|
10
|
1
|
0
|
Linked Clone |
| Persistent Disk_ |
1
|
0
|
1
|
100
|
Linked Clone/Full Clone |
| FULL_CLONE_DISK_FLOATING_ |
1
|
0
|
0
|
100
|
Floating Full Clone |
| FULL_CLONE_DISK_ |
1
|
0
|
1
|
100
|
Dedicated Full Clone |
| OS_DISK_FLOATING_ |
1
|
0
|
0
|
0
|
Floating Linked Clone |
More Details:
VM_HOME – The folder which contains the virtual machine configuration files, such as .vmx, .vmsd, and .nvram.
OS_Disk – Linked Clone Dedicated/Persistent desktop pools
OS_DISK_FLOATING – Linked Clone Floating/Non-persistent desktop pools
REPLICA_DISK – A replica of the parent VM is created and stored on 1 per LUN basis from which the LC desktops are created
Persistent Disk – The User Persistent disk that redirects the user profile and user data to D: drive
_ – The GUID seen at the end of the default policy is a cluster GUID for a view deployment. The policies can be shared amongst multiple pools within a single view deployment.
Number of Failures to Tolerate (FTT) – Defines the number of hosts, disk, or network failures a storage object can tolerate. For n failures tolerated, n+1 copies of the object are created and 2n+1 hosts that contribute storage are required.
Number of Disk Stripes Per Object – The number of HDDs across which each replica of a virtual machine object is striped. A value higher than 1 might result in better performance, but also results in a higher use of system resources.
I hope this information helps. Feel free to post your comments down below.
Best Regards,
Aresh Sarkari
Excellent blog on Horizon 6 and VSAN, hope VSAN is 1.0.