Skip to content

Commit c0a5e1a

Browse files
authored
Update configure-storage-policy.md
1 parent cb7de4b commit c0a5e1a

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -146,17 +146,17 @@ Keep the following information in mind:
146146
| **Field** | **Value** |
147147
| --- | --- |
148148
| **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. |
149-
| **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` |
150-
| **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` |
151-
| **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`. |
149+
| **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`. |
150+
| **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`. |
151+
| **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`. |
152152
| **vSANChecksumDisabled** | Enable or disable checksum for the policy. <br>- The default value is `$false`. <br>- Valid values are `$true` or `$false`. <br>- Warning: Disabling checksum can lead to data loss and/or corruption. <br>- Recommended value is `$false`. |
153153
| **vSANCacheReservation** | Percentage of cache reservation for the policy. <br>- The default value is `0`. <br>- Valid values are `0` to `100`.|
154154
| **vSANIOLimit** | Sets limit on allowed input/output (IO). <br>- The default value is unset. <br>- Valid values are `0` to `2147483647`. <br>- Input/output operations per second (IOPS) limit for the policy. |
155155
| **vSANDiskStripesPerObject** | The number of hard disk drives (HDDs) across which each replica of a storage object is striped. <br>- The default value is `1`. Valid values are `1` to `12`. <br>- A value higher than `1` might result in better performance (for example, when flash read cache misses need to get serviced from HDD), but also results in a higher use of system resources. |
156-
| **vSANObjectSpaceReservation** | Object reservation. <br>- The default value is `0`. <br>- Valid values are `0` to `100`. <br>- `0` = thin provision <br>- `100` = thick provision|
156+
| **vSANObjectSpaceReservation** | Object reservation. <br>- The default value is `0`. <br>- Valid values are `0` to `100`. <br>- `0` = thin provision <br>- `100` = thick provision.|
157157
| **VMEncryption** | Sets VM encryption. <br>- The default value is `None`. <br>- Valid values are `None`, `Pre-IO`, and `Post-IO`. <br>- Pre-IO allows virtual IO (VAIO) filtering solutions to capture data before VM encryption. <br>- Post-IO allows VAIO-filtering solutions to capture data after VM encryption. |
158-
| **vSANFailuresToTolerate** | Number of vSAN hosts' failures to tolerate. <br>- The default value is `R1FTT1`. <br>- Valid values are `None`, `R1FTT1`, `R1FTT2`, `R1FTT3`, `R5FTT1`, `R6FTT2`, and `R1FTT3` <br>- `None` = No data redundancy<br>- `R1FTT1` = 1 failure - `RAID-1` (mirroring)<br>- `R1FTT2` = 2 failures - `RAID-1` (mirroring)<br>- `R1FTT3` = 3 failures - `RAID-1` (mirroring)<br>- `R5FTT1` = 1 failure - `RAID-5` (erasure coding),<br>- `R6FTT2` = 2 failures - `RAID-6` (erasure coding) <br>- The `None` (no data redundancy) option isn't covered under Microsoft's SLA.|
159-
| **vSANSiteDisasterTolerance** | Valid only for stretch clusters. <br>- The default value is `None`. <br>- Valid values are `None`, `Dual`, `Preferred`, `Secondary`, and `NoneStretch` <br>- `None` = No site redundancy. This option is recommended for nonstretch clusters and not recommended for stretch clusters. <br>- `Dual` = dual site redundancy. This option is recommended for stretch clusters. <br>- `Preferred` = No site redundancy - Keep data on Preferred (stretched cluster). <br>- `Secondary` = No site redundancy - Keep data on Secondary Site (stretched cluster). <br>- `NoneStretch` = No site redundancy - not recommended. For more details, see [For vSAN stretched clusters, don't use a storage policy with locality=none](https://kb.vmware.com/s/article/88358).|
158+
| **vSANFailuresToTolerate** | Number of vSAN hosts' failures to tolerate. <br>- The default value is `R1FTT1`. <br>- Valid values are `None`, `R1FTT1`, `R1FTT2`, `R1FTT3`, `R5FTT1`, `R6FTT2`, and `R1FTT3`. <br>- `None` = No data redundancy.<br>- `R1FTT1` = 1 failure - `RAID-1` (mirroring).<br>- `R1FTT2` = 2 failures - `RAID-1` (mirroring).<br>- `R1FTT3` = 3 failures - `RAID-1` (mirroring).<br>- `R5FTT1` = 1 failure - `RAID-5` (erasure coding).<br>- `R6FTT2` = 2 failures - `RAID-6` (erasure coding). <br>- The `None` (no data redundancy) option isn't covered under Microsoft's SLA.|
159+
| **vSANSiteDisasterTolerance** | Valid only for stretch clusters. <br>- The default value is `None`. <br>- Valid values are `None`, `Dual`, `Preferred`, `Secondary`, and `NoneStretch`. <br>- `None` = No site redundancy. This option is recommended for nonstretch clusters and not recommended for stretch clusters. <br>- `Dual` = dual site redundancy. This option is recommended for stretch clusters. <br>- `Preferred` = No site redundancy - Keep data on Preferred (stretched cluster). <br>- `Secondary` = No site redundancy - Keep data on Secondary Site (stretched cluster). <br>- `NoneStretch` = No site redundancy - not recommended. For more details, see [For vSAN stretched clusters, don't use a storage policy with locality=none](https://kb.vmware.com/s/article/88358).|
160160
| **Description** | Description of the storage policy that you're creating, free form text. |
161161
| **Name** | Name of the storage policy to set. For example, *RAID1 FTT-1*. |
162162
| **Retain up to** | Retention period of the cmdlet output. The default value is `60`. |

0 commit comments

Comments
 (0)