Skip to content

Commit 2ccf991

Browse files
committed
Update concepts-storage.md
1 parent 07e2f95 commit 2ccf991

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/azure-vmware/concepts-storage.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,11 +28,13 @@ Local storage in cluster hosts is used in the cluster-wide vSAN datastore. All d
2828
2929
## Storage policies and fault tolerance
3030

31-
The default storage policy is set to RAID-1 (Mirroring), FTT-1, and thick provisioning. Unless you adjust the storage policy or apply a new policy, the cluster grows with this configuration. To set the storage policy, see [Configure storage policy](configure-storage-policy.md).
31+
The default storage policy is set to RAID-1 (Mirroring) FTT-1, with Object Space Reservation set to **Thin** provisioning. Unless you adjust the storage policy or apply a new policy, the cluster grows with this configuration. This is the policy that will be applied to the workload VMs. To set a different storage policy, see [Configure storage policy](configure-storage-policy.md).
3232

3333
In a three-host cluster, FTT-1 accommodates a single host's failure. Microsoft governs failures regularly and replaces the hardware when events are detected from an operations perspective.
3434

35-
:::image type="content" source="media/concepts/vsphere-vm-storage-policies.png" alt-text="Screenshot that shows the vSphere Client VM Storage Policies.":::
35+
> [!NOTE]
36+
> When you log on to the vSphere Client, you may notice a VM Storage Policy called **vSAN Default Storage Policy** with **Object Space Reservation** set to **Thick** provisioning. Please note that this is NOT the default storage policy applied to the cluster. This policy exists for historical purposes and will eventually be modified to **Thin** provisioning.
37+
3638

3739

3840
|Provisioning type |Description |

0 commit comments

Comments
 (0)