You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -39,20 +41,20 @@ Storage account scale targets apply at the storage account level. There are two
39
41
40
42
-**General purpose version 2 (GPv2) storage accounts**: GPv2 storage accounts allow you to deploy pay-as-you-go file shares on HDD-based hardware. In addition to storing Azure file shares, GPv2 storage accounts can store other storage resources such as blob containers, queues, or tables.
| Maximum number of virtual network rules | 200 | 200 | 200 | 200 |
54
+
| Maximum number of IP address rules | 200 | 200 | 200 | 200 |
55
+
| Management read operations | 800 per 5 minutes | 800 per 5 minutes | 800 per 5 minutes | 800 per 5 minutes |
56
+
| Management write operations | 10 per second/1200 per hour | 10 per second/1200 per hour | 10 per second/1200 per hour | 10 per second/1200 per hour |
57
+
| Management list operations | 100 per 5 minutes | 100 per 5 minutes | 100 per 5 minutes | 100 per 5 minutes |
56
58
57
59
#### Selected regions with increased maximum throughput for HDD pay-as-you-go
58
60
The following regions have an increased maximum throughput for HDD pay-as-you-go storage accounts (StorageV2):
@@ -91,37 +93,37 @@ The following regions have an increased maximum throughput for HDD pay-as-you-go
91
93
### Azure file share scale targets
92
94
Azure file share scale targets apply at the file share level.
| Maximum number of files | Unlimited | Unlimited | Unlimited |
102
-
| Maximum IOPS (Data) | 102,400 IOPS (dependent on provisioning) | 50,000 IOPS (dependent on provisioning) | 20,000 IOPS |
103
-
| Maximum IOPS (Metadata<sup>1</sup>) | Up to 35,000 IOPS | Up to 12,000 IOPS | Up to 12,000 IOPS |
104
-
| Maximum throughput | 10,340 MiB / sec (dependent on provisioning) | 5,120 MiB / sec (dependent on provisioning) | Up to storage account limits |
105
-
| Maximum number of share snapshots | 200 snapshots | 200 snapshots | 200 snapshots |
106
-
| Maximum filename length<sup>2</sup> (full pathname including all directories, file names, and backslash characters) | 2,048 characters | 2,048 characters | 2,048 characters |
107
-
| Maximum length of individual pathname component (in the path \A\B\C\D, each letter represents a directory or file that is an individual component) | 255 characters | 255 characters | 255 characters |
108
-
| Hard link limit (NFS only) | 178 | N/A | N/A |
109
-
| Maximum number of SMB Multichannel channels | 4 | N/A | N/A |
110
-
| Maximum number of stored access policies per file share | 5 | 5 | 5 |
| Maximum number of files | Unlimited | Unlimited | Unlimited | Unlimited |
104
+
| Maximum IOPS (Data) | 102,400 IOPS (dependent on provisioning) | 50,000 IOPS (dependent on provisioning) |102,400 IOPS (dependent on provisioning) |20,000 IOPS |
105
+
| Maximum IOPS (Metadata<sup>1</sup>) | Up to 35,000 IOPS | Up to 12,000 IOPS | Up to 35,000 IOPS | Up to 12,000 IOPS |
106
+
| Maximum throughput | 10,340 MiB / sec (dependent on provisioning) | 5,120 MiB / sec (dependent on provisioning) |10,340 MiB / sec (dependent on provisioning) |Up to storage account limits |
107
+
| Maximum number of share snapshots | 200 snapshots | 200 snapshots | 200 snapshots | 200 snapshots |
108
+
| Maximum filename length<sup>2</sup> (full pathname including all directories, file names, and backslash characters) | 2,048 characters | 2,048 characters | 2,048 characters | 2,048 characters |
109
+
| Maximum length of individual pathname component (in the path \A\B\C\D, each letter represents a directory or file that is an individual component) | 255 characters | 255 characters | 255 characters | 255 characters |
110
+
| Hard link limit (NFS only) | 178 | N/A |178 |N/A |
111
+
| Maximum number of SMB Multichannel channels | 4 | N/A |4 |N/A |
112
+
| Maximum number of stored access policies per file share | 5 | 5 | 5 | 5 |
111
113
112
114
<sup>1</sup> Metadata IOPS (open/close/delete). See [Monitor Metadata IOPS](analyze-files-metrics.md#monitor-utilization-by-metadata-iops) for guidance.<br>
113
115
<sup>2</sup> Azure Files enforces certain [naming rules](/rest/api/storageservices/naming-and-referencing-shares--directories--files--and-metadata#directory-and-file-names) for directory and file names.
114
116
115
117
### File scale targets
116
118
File scale targets apply to individual files stored in Azure file shares.
@@ -107,6 +109,8 @@ The provisioned v2 model is provided for file shares in storage accounts with th
107
109
108
110
| Storage account kind | Storage account SKU | Type of file share available |
109
111
|-|-|-|
112
+
| FileStorage | PremiumV2_LRS | SSD provisioned v2 file shares with the Local (LRS) redundancy specified. |
113
+
| FileStorage | PremiumV2_ZRS | SSD provisioned v2 file shares with the Zone (ZRS) redundancy specified. |
110
114
| FileStorage | StandardV2_LRS | HDD provisioned v2 file shares with the Local (LRS) redundancy specified. |
111
115
| FileStorage | StandardV2_ZRS | HDD provisioned v2 file shares with the Zone (ZRS) redundancy specified. |
112
116
| FileStorage | StandardV2_GRS | HDD provisioned v2 file shares with the Geo (GRS) redundancy specified. |
@@ -167,28 +171,28 @@ Currently, these SKUs are generally available in a limited subset of regions:
167
171
### Provisioned v2 provisioning detail
168
172
When you create a provisioned v2 file share, you specify the provisioned capacity for the file share in terms of storage, IOPS, and throughput. File shares are limited based on the following attributes:
| Maximum provisioned storage per file share | 256 TiB (262,144 GiB) | 256 TiB (262,144 GiB) |
183
+
| Maximum provisioned IOPS per file share |102,400 IOPS |50,000 IOPS |
184
+
| Maximum provisioned throughput per file share |10,340 MiB / sec |5,120 MiB / sec |
185
+
| Maximum provisioned storage per storage account |256 TiB (262,144 GiB) |4 PiB (4,194,304 GiB) |
186
+
| Maximum provisioned IOPS per storage account |102,400 IOPS |50,000 IOPS |
187
+
| Maximum provisioned throughput per storage account |10,340 MiB / sec |5,120 MiB / sec |
188
+
| Maximum number of file shares per storage account | 50 file shares | 50 file shares |
185
189
186
190
By default, we recommended IOPS and throughput provisioning based on the provisioned storage you specify. These recommendation formulas are based on typical customer usage for that amount of provisioned storage for that media tier in Azure Files:
Depending on your individual file share requirements, you may find that you require more or less IOPS or throughput than our recommendations, and can optionally override these recommendations with your own values as desired.
194
198
@@ -205,22 +209,24 @@ Share credits have three states:
205
209
206
210
A new file share starts with the full number of credits in its burst bucket. Burst credits don't accrue if the share IOPS fall below the provisioned limit due to throttling by the server. The following formulas are used to determine the burst IOPS limit and the number of credits possible for a file share:
| 3,000 | Up to 10,000 | 25,200,000 | Up to 9,000 | 21,600,000 |
224
+
| 5,000 | Up to 15,000 | 36,000,000 | Up to 15,000 | 36,000,000 |
225
+
| 10,000 | Up to 30,000 | 72,000,000 | Up to 30,000 | 72,000,000 |
226
+
| 25,000 | Up to 75,000 | 180,000,000 | Up to 50,000 | 90,000,000 |
227
+
| 50,000 | Up to 102,400 | 188,640,000 | Up to 50,000 | 0 |
228
+
| 75,000 | Up to 102,400 | 98,640,000 | -- | -- |
229
+
| 102,400 | Up to 102,400 | 0 | -- | -- |
224
230
225
231
### Provisioned v2 snapshots
226
232
Azure Files supports snapshots, which are similar to volume shadow copies (VSS) on Windows File Server. For more information on share snapshots, see [Overview of snapshots for Azure Files](storage-snapshots-files.md).
0 commit comments