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
Copy file name to clipboardExpand all lines: articles/storage/files/create-file-share.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Create a File Share (Microsoft.FileShares)
2
+
title: Create a file share (Microsoft.FileShares)
3
3
description: Learn to use the Azure portal to deploy an NFS file share with Microsoft.FileShares resource provider (preview).
4
4
author: khdownie
5
5
ms.service: azure-file-storage
@@ -62,17 +62,17 @@ The first tab to complete creating a file share is labeled **Basics**, which con
62
62
| Subscription | Drop-down list |*Available Azure subscriptions*| The selected subscription in which to deploy the storage account.|
68
-
| Resource group | Drop-down list |*Available resource groups in selected subscription*| The resource group in which to deploy the file share. A resource group is a logical container for organizing Azure resources, including file shares.|
69
-
|file share name | Text box | -- | The name of the file share must be unique across all existing file share names in Microsoft Azure. It must be 3 to 63 characters long and can contain only lowercase letters, numbers, and hyphens. The name must start and end with a letter or number.|
70
-
| Tier | N/A | -- | Premium file shares are backed by solid-state drives (SSD) for better performance. Currently, the Microsoft.FileShares preview only supports SSD. |
71
-
| Protocol | N/A | -- | file shares support a multitude of access protocols. If you need the SMB protocol, deploy your file share within a storage account. Currently, the Microsoft.FileShares preview only supports NFS protocol.|
72
-
| Region | Drop-down list |*Available Azure regions*| The region for the file share to be deployed into. This can be the region associated with the resource group, or any other available region.|
73
-
| Provisioned capacity (GiB) | Text box | Integer | Provisioned capacity for the file share, ranging from 32 GiB to 262144 GiB.|
74
-
| Redundancy | Drop-down list | - Locally redundant storage (LRS) <br> - Geo-redundant storage (GRS) | The redundancy choice for the file share. See [Azure Files redundancy](files-redundancy.md) for more information.|
75
-
| Provisioned IOPS and throughput| Radio button group | - Recommended provisioning <br> - Manually specify IOPS and throughput: <br> - Provisioned IOPS <br> - Provisioned throughput (MiB/sec)| The Microsoft.FileShares preview only uses the [provisioned v2 billing model](understanding-billing.md#provisioned-v2-model).|
65
+
| Field name|Input type|Values|Meaning |
66
+
|-|-|-|-|
67
+
| Subscription | Drop-down list |*Available Azure subscriptions*| The selected subscription in which to deploy the storage account. |
68
+
| Resource group | Drop-down list |*Available resource groups in selected subscription*| The resource group in which to deploy the file share. A resource group is a logical container for organizing Azure resources, including file shares. |
69
+
|File share name | Text box | -- | The name of the file share must be unique across all existing file share names in Microsoft Azure. It must be 3 to 63 characters long and can contain only lowercase letters, numbers, and hyphens. The name must start and end with a letter or number. |
70
+
| Tier | N/A | -- | The media tier for the file share. The Microsoft.FileShares preview only supports the SSD media tier.|
71
+
| Protocol | N/A | -- | File shares support a multitude of access protocols. If you need the SMB protocol, deploy your file share within a storage account. Currently, the Microsoft.FileShares preview only supports NFS protocol. |
72
+
| Region | Drop-down list |*Available Azure regions*| The region for the file share to be deployed into. This can be the region associated with the resource group, or any other available region. |
73
+
| Provisioned capacity (GiB) | Text box | Integer | Provisioned capacity for the file share, ranging from 32 GiB to 262,144 GiB. |
74
+
| Redundancy | Drop-down list | <ul><li>Locally redundant storage (LRS)</li><li>Zone redundant storage (ZRS)</li></ul> | The redundancy choice for the file share. See [Azure Files redundancy](files-redundancy.md) for more information. |
75
+
| Provisioned IOPS and throughput| Radio button group | <ul><li>Recommended provisioning</li><li>Manually specify IOPS and throughput:<ul><li>Provisioned IOPS</li><li>Provisioned throughput (MiB/sec)</li></ul></li></ul> | The Microsoft.FileShares preview only uses the [provisioned v2 billing model](understanding-billing.md#provisioned-v2-model). |
Copy file name to clipboardExpand all lines: articles/storage/files/files-redundancy.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ LRS is a good choice for the following scenarios:
63
63
- If your application stores data that can be easily reconstructed if data loss occurs.
64
64
- If your application is restricted to replicating data only within a country or region due to data governance requirements. In some cases, the paired regions across which the data is geo-replicated might be in another country or region. For more information, see [Azure region pairs and nonpaired regions](/azure/reliability/regions-paired).
65
65
66
-
LRS is supported in all Azure regions for HDD file shares. For a list of regions that support LRS for SSD file shares, see [LRS support for SSD file shares](redundancy-premium-file-shares.md#lrs-support-for-ssd-azure-file-shares).
66
+
LRS is supported in all Azure regions for HDD (standard) file shares. For a list of regions that support LRS for SSD (premium) file shares, see [LRS support for SSD file shares](redundancy-premium-file-shares.md#lrs-support-for-ssd-azure-file-shares).
67
67
68
68
### Zone-redundant storage
69
69
@@ -86,9 +86,10 @@ ZRS provides excellent performance, low latency, and resiliency for your data if
86
86
87
87
#### ZRS support by region
88
88
89
-
To understand which regions support ZRS for standard file shares, see the [Azure regions list](/azure/reliability/regions-list#azure-regions-list-1) and refer to the availability zone support column. ZRS is supported in standard general-purpose v2 storage accounts for all three standard tiers: transaction optimized, hot, and cool.
89
+
ZRS is supported for both SSD and HDD file shares. To see which regions support ZRS for each media tier, refer to the following resources:
90
90
91
-
ZRS is supported for SSD file shares through the `FileStorage` storage account kind. For a list of regions that support ZRS for SSD file share accounts, see [ZRS support for SSD file shares](redundancy-premium-file-shares.md#zrs-support-for-ssd-azure-file-shares).
91
+
-**HDD file shares**: See the availability zone support column in the [Azure regions list](/azure/reliability/regions-list#azure-regions-list-1).
92
+
-**SSD file shares**: See [ZRS support for SSD file shares](redundancy-premium-file-shares.md#zrs-support-for-ssd-azure-file-shares).
92
93
93
94
## Redundancy in a secondary region
94
95
@@ -99,7 +100,7 @@ For applications requiring high durability for SMB file shares, you can choose g
99
100
100
101
When you create a storage account, you select the primary region for the account. The paired secondary region is determined based on the primary region, and can't be changed. For more information about regions supported by Azure, see the [Azure regions list](/azure/reliability/regions-list#azure-regions-list-1).
101
102
102
-
Azure Files offers two options for copying your data to a secondary region. Currently, geo-redundant storage options are only available for standard SMB file shares.
103
+
Azure Files offers two options for copying your data to a secondary region. Currently, geo-redundant storage options are only available for HDD SMB file shares.
103
104
104
105
-**Geo-redundant storage (GRS)** copies your data synchronously three times within one or more Azure availability zones in the primary region using LRS. It then copies your data asynchronously to a single physical location in the secondary region. Within the secondary region, your data is copied synchronously three times using LRS.
105
106
-**Geo-zone-redundant storage (GZRS)** copies your data synchronously across three Azure availability zones in the primary region using ZRS. It then copies your data asynchronously to a single physical location in the secondary region. Within the secondary region, your data is copied synchronously three times using LRS.
Copy file name to clipboardExpand all lines: articles/storage/files/files-reserve-capacity.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,19 +14,16 @@ recommendations: false
14
14
15
15
# Optimize costs with Azure Files Reservations
16
16
17
+
:heavy_check_mark:**Applies to:** Classic file shares created with the Microsoft.Storage resource provider with either the provisioned v1 or pay-as-you-go billing models
18
+
19
+
:heavy_multiplication_x:**Doesn't apply to:** All file shares using the provisioned v2 billing model including file shares created with the Microsoft.FileShares resource provider (preview) or classic file shares created with the Microsoft.Storage resource provider
20
+
17
21
You can save money on the storage costs for Azure file shares with Azure Files Reservations. Azure Files Reservations (also referred to as *reserved instances*) offer you a discount on capacity for storage costs when you commit to a Reservation for either one year or three years. A Reservation provides a fixed amount of storage capacity for the term of the Reservation.
18
22
19
23
Azure Files reservations can significantly reduce your capacity costs for storing data in Azure file shares. How much you save will depend on the duration of your Reservation, the total storage capacity you choose to reserve, and the tier and redundancy settings that you've chosen for your Azure file shares. Reservations provide a billing discount and don't affect the state of your Azure file shares. Reservations have no effect on performance.
20
24
21
25
For pricing information about Azure Files Reservations, see [Azure Files pricing](https://azure.microsoft.com/pricing/details/storage/files/).
22
26
23
-
## Applies to
24
-
25
-
| File share type | SMB | NFS |
26
-
|-|:-:|:-:|
27
-
| Standard file shares (GPv2), LRS/ZRS |||
28
-
| Standard file shares (GPv2), GRS/GZRS |||
@@ -44,11 +41,11 @@ An Azure Files Reservation covers only the amount of data that is stored in a su
44
41
45
42
### Reservations and snapshots
46
43
47
-
If you're taking snapshots of Azure file shares, there are differences in how Reservations work for standard versus premium file shares. If you're taking snapshots of standard file shares, then the snapshot differentials count against the Reservation and are billed as part of the normal used storage meter. However, if you're taking snapshots of premium file shares, then the snapshots are billed using a separate meter and don't count against the Reservation.
44
+
If you're taking snapshots of Azure file shares, there are differences in how Reservations work for pay-as-you-go versus provisioned v1 file shares. If you're taking snapshots of pay-as-you-go file shares, then the snapshot differentials count against the Reservation and are billed as part of the normal used storage meter. However, if you're taking snapshots of provisioned v1 file shares, then the snapshots are billed using a separate meter and don't count against the Reservation.
48
45
49
-
### Supported tiers and redundancy options
46
+
### Supported billing models and redundancy options
50
47
51
-
Azure Files Reservations are available for premium, hot, and cool file shares. Reservations aren't available for Azure file shares in the transaction optimized tier. All storage redundancies support Reservations. For more information about redundancy options, see [Azure Files redundancy](storage-files-planning.md#redundancy).
48
+
Azure Files Reservations are available for SSD provisioned v1 file shares, and for HDD pay-as-you-go file shares in the hot and cool access tiers. Reservations aren't available for the provisioned v2 billing model or for pay-as-you-go file shares in the transaction optimized access tier. All storage redundancies support Reservations. For more information about redundancy options, see [Azure Files redundancy](storage-files-planning.md#redundancy).
52
49
53
50
### Security requirements for purchase
54
51
@@ -60,7 +57,7 @@ To purchase a Reservation:
60
57
61
58
## Determine required capacity before purchase
62
59
63
-
When you purchase an Azure Files Reservation, you must choose the region, tier, and redundancy option for the Reservation. Your Reservation is valid only for data stored in that region, tier, and redundancy level. For example, suppose you purchase a Reservation for data in West US for the hot tier using zone-redundant storage (ZRS). That Reservation will not apply to data in US East, data in the cool tier, or data in geo-redundant storage (GRS). However, you can purchase another Reservation for your additional needs.
60
+
When you purchase an Azure Files Reservation, you must choose the region, billing model and access tier (for pay-as-you-go), and redundancy option for the Reservation. Your Reservation is valid only for data stored in that region, billing model/access tier, and redundancy level. For example, suppose you purchase a Reservation for data in West US for the hot access tier using zone-redundant storage (ZRS). That Reservation will not apply to data in US East, data in the cool access tier, or data in geo-redundant storage (GRS). However, you can purchase another Reservation for your additional needs.
64
61
65
62
Reservations are available for 10 TiB or 100 TiB blocks, with higher discounts for 100 TiB blocks. When you purchase a Reservation in the Azure portal, Microsoft may provide you with recommendations based on your previous usage to help determine which Reservation you should purchase.
66
63
@@ -83,7 +80,7 @@ Follow these steps to purchase a Reservation:
83
80
|**Scope** | Indicates how many subscriptions can use the billing benefit associated with the Reservation. It also controls how the Reservation is applied to specific subscriptions. <br/><br/> If you select **Shared**, the Reservation discount is applied to Azure Files capacity in any subscription within your billing context. The billing context is based on how you signed up for Azure. For enterprise customers, the shared scope is the enrollment and includes all subscriptions within the enrollment. For pay-as-you-go customers, the shared scope includes all individual subscriptions with pay-as-you-go rates created by the account administrator. <br/><br/> If you select **Single subscription**, the Reservation discount is applied to Azure Files capacity in the selected subscription. <br/><br/> If you select **Single resource group**, the Reservation discount is applied to Azure Files capacity in the selected subscription and the selected resource group within that subscription. <br/><br/> You can change the Reservation scope after you purchase the Reservation. |
84
81
|**Subscription**| The subscription that's used to pay for the Azure Files Reservation. The payment method on the selected subscription is used in charging the costs. The subscription must be one of the following types: <br/><br/> Enterprise Agreement (offer numbers: MS-AZR-0017P or MS-AZR-0148P): For an Enterprise subscription, the charges are deducted from the enrollment's Azure Prepayment (previously called monetary commitment) balance or charged as overage. <br/><br/> Individual subscription with pay-as-you-go rates (offer numbers: MS-AZR-0003P or MS-AZR-0023P): For an individual subscription with pay-as-you-go rates, the charges are billed to the credit card or invoice payment method on the subscription. |
85
82
|**Region**| The region where the Reservation is in effect. |
86
-
|**Tier**| The tier for which the Reservation is in effect. Options include *Premium*, *Hot*, and *Cool*. |
83
+
|**Tier**| The billing model or access tier for the Reservation. Options include *Premium* (SSD provisioned v1), *Hot* (HDD pay-as-you-go), and *Cool* (HDD pay-as-you-go). |
87
84
|**Redundancy**| The redundancy option for the Reservation. Options include *LRS*, *ZRS*, *GRS*, and *GZRS*. For more information about redundancy options, see [Azure Files redundancy](storage-files-planning.md#redundancy). |
88
85
|**Billing frequency**| Indicates how often the account is billed for the Reservation. Options include *Monthly* or *Upfront*. |
0 commit comments