Skip to content

Commit f25522d

Browse files
Merge pull request #283583 from b-ahibbard/anf-lgvol
less > more
2 parents 4ae29d5 + bed7d5f commit f25522d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-netapp-files/large-volumes-requirements-considerations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The following requirements and considerations apply to large volumes. For perfor
2020
* A regular volume can’t be converted to a large volume.
2121
* You must create a large volume at a size of 50 TiB or larger. A single volume can't exceed 1 PiB.
2222
* You can't resize a large volume to less than 50 TiB.
23-
A large volume cannot be resized to less than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits).
23+
A large volume cannot be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits).
2424
* Large volumes are currently not supported with Azure NetApp Files backup.
2525
* You can't create a large volume with application volume groups.
2626
* Currently, large volumes aren't suited for database (HANA, Oracle, SQL Server, etc.) data and log volumes. For database workloads requiring more than a single volume’s throughput limit, consider deploying multiple regular volumes. To optimize multiple volume deployments for databases, use [application volume groups](application-volume-group-concept.md).

0 commit comments

Comments
 (0)