Skip to content

Commit fe2fb6d

Browse files
authored
Update configure-storage-policy.md
1 parent eec2abe commit fe2fb6d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/azure-vmware/configure-storage-policy.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ In this article learn how to:
3131
3232
## Prerequisites for vSAN OSA-based clusters
3333

34-
Make sure that the minimum level of hosts are met, according to the following table:
34+
Make sure that the minimum level of hosts is met, according to the following table:
3535

3636
| **RAID configuration** | **Failures to tolerate (FTT)** | **Minimum hosts required** |
3737
| --- | :---: | :---: |
@@ -43,7 +43,7 @@ Make sure that the minimum level of hosts are met, according to the following ta
4343

4444
## Prerequisites for vSAN ESA-based clusters
4545

46-
Make sure that the minimum level of hosts are met, according to the following table:
46+
Make sure that the minimum level of hosts is met, according to the following table:
4747

4848
| **RAID configuration** | **Failures to tolerate (FTT)** | **Minimum hosts required** |
4949
| --- | :---: | :---: |
@@ -146,15 +146,15 @@ Keep the following information in mind:
146146

147147
* You can't modify existing Azure VMware Solution default storage policies.
148148
* Certain options enabled in storage policies produce a warning that a policy is out of compliance.
149-
* Out of compliance: When you modify existing storage policies, existing associated vSAN objects like VMs, VMDK files, and ISO files appear to be "out of compliance." This means that existing objects are running against premodified policy settings. To update to match the modified policy settings, reapply the storage policy to objects.
149+
* When you modify existing storage policies, existing associated vSAN objects like VMs, VMDK files, and ISO files appear to be "out of compliance." This means that existing objects are running against premodified policy settings. To update to match the modified policy settings, reapply the storage policy to objects.
150150

151151
1. Select **Run command** > **Packages** > **New-AVSStoragePolicy**.
152152

153153
1. Provide the required values or change the default values according to the following table. Then select **Run**.
154154

155155
| **Field** | **Value** |
156156
| --- | --- |
157-
| **Overwrite** | Overwrite existing storage policy. <br>- The default value is `$false`. <br>- When you pass overwrite `true` provided overwrites an existing policy exactly as defined. <br>- Those values not passed are removed or set to default values. |
157+
| **Overwrite** | Overwrite existing storage policy. <br>- The default value is `$false`. <br>- Passing overwrite `true` provided overwrites an existing policy exactly as defined. <br>- Those values not passed are removed or set to default values. |
158158
| **NotTags** | Match to datastores that do *not* have these tags. <br>- Tags are case sensitive. <br>- Comma separate multiple tags. <br>- Example: `Tag1,Tag 2,Tag_3`. |
159159
| **Tags** | Match to datastores that do have these tags. <br>- Tags are case sensitive. <br>- Comma separate multiple tags. <br>- Example: `Tag1,Tag 2,Tag_3`. |
160160
| **vSANForceProvisioning** | Force provisioning for the policy. <br>- The default value is `$false`.<br>- Valid values are `$true` or `$false`. <br>- Warning: vSAN force-provisioned objects aren't covered under Microsoft's Service Level Agreement (SLA). Data loss and vSAN instability can occur. <br>- Recommended value is `$false`. |

0 commit comments

Comments
 (0)