|
10 | 10 | ms.custom: include file |
11 | 11 | --- |
12 | 12 |
|
13 | | -- **Capital and operational costs of Windows File Servers with one or more server endpoints.** Azure File Sync as a replication solution is agnostic of where the Windows File Servers that are synchronized with Azure Files are; they could be hosted on-premises, in an Azure VM, or even in another cloud. Unless you are using Azure File Sync with a Windows File Server that is hosted in an Azure VM, the capital (i.e. the upfront hardware costs of your solution) and operating (i.e. cost of labor, electricity, etc.) costs will not be part of your Azure bill, but will still be very much a part of your total cost of ownership. You should consider the amount of data you need to cache on-premises, the number of CPUs and amount of memory your Windows File Servers need to host Azure File Sync workloads (see [recommended system resources for more information](../articles/storage/file-sync/file-sync-planning.md#recommended-system-resources)), and other organization-specific costs you might have. |
| 13 | +- **Capital and operational costs of Windows File Servers with one or more server endpoints.** Azure File Sync as a replication solution is agnostic of where the Windows File Servers that are synchronized with Azure Files are; they could be hosted on-premises, in an Azure virtual machine, or even in another cloud. The costs for sync servers hosted on-premises or in other cloud providers include both capital and operating costs that aren't tracked as part of your Azure bill, but are still part of the total cost of ownership of the solution. Captial expenses are the upfront hardware costs of your solution. Operating expenses are the ongoing costs of labor, electricity, etc. You should consider the amount of data you need to cache on-premises, the number of CPUs and amount of memory your Windows File Servers need to host Azure File Sync workloads, and other organization-specific costs you might have. For more information, see [recommended system resources](../articles/storage/file-sync/file-sync-planning.md#recommended-system-resources). |
14 | 14 |
|
15 | | -- **Per server licensing cost for servers registered with Azure File Sync.** To use Azure File Sync with a specific Windows File Server, you must first register it with Azure File Sync's Azure resource, the Storage Sync Service. Each server that you register after the first server has a flat monthly fee. Although this fee is very small, it is one component of your bill to consider. To see the current price of the server registration fee for your desired region, see [the File Sync section on Azure Files pricing page](https://azure.microsoft.com/pricing/details/storage/files/). |
| 15 | +- **Per server licensing cost for servers registered with Azure File Sync.** To use Azure File Sync with a specific Windows File Server, you must first register it with Azure File Sync's Azure resource, the Storage Sync Service. Each server that you register after the first server has a flat monthly fee. Although this fee is small, it is one component of your bill to consider. To see the current price of the server registration fee for your desired region, see [the File Sync section on Azure Files pricing page](https://azure.microsoft.com/pricing/details/storage/files/). |
16 | 16 |
|
17 | | -- **Azure Files costs.** Because Azure File Sync is a synchronization solution for Azure Files, it will cause you to consume Azure Files resources. Some of these resources, like storage consumption, are relatively obvious, while others such as transaction and snapshot utilization may not be. For most customers, we recommend using standard file shares with Azure File Sync, although Azure File Sync is fully supported with premium file shares if desired. |
18 | | - - **Storage utilization.** Azure File Sync will replicate any changes you have made to the path on your Windows File Server specified on your server endpoint to your Azure file share, thus causing storage to be consumed. On standard file shares, this means that adding or increasing the size of existing files on server endpoints will cause storage costs to grow, because the changes will be replicated. On premium file shares, changes will be consume provisioned space - it is your responsibility to periodically increase provisioning as needed to account for file share growth. |
| 17 | +- **Azure Files costs.** Azure File Sync consumes resources from your Azure file share. Some of these resources, like storage consumption, are relatively obvious, while others such as transaction and snapshot utilization may not be. For most customers, we recommend using HDD provisioned v2 file shares with Azure File Sync, although Azure File Sync is fully supported on all Azure Files billing models (SSD provisioned v2, SSD provisioned v1, or HDD pay-as-you-go). |
| 18 | + - **Storage utilization.** Azure File Sync replicates any changes you make to your server endpoint to your Azure file share causing storage to be consumed. On provisioned file shares, changes consume provisioned space, so it is your responsibility to periodically increase provisioning as needed to account for file share growth. On pay-as-you-go file shares, adding or increasing the size of existing files on server endpoints causes the used storage costs to grow because the changes are replicated. |
19 | 19 |
|
20 | 20 | - **Snapshot utilization.** Azure File Sync takes share and file-level snapshots as part of regular usage. Although snapshot utilization is always differential, this can contribute in a noticeable way to the total Azure Files bill. |
21 | 21 |
|
22 | | - - **Transactions from churn.** As files change on server endpoints, the changes are uploaded to the cloud share, which generates transactions. When cloud tiering is enabled, additional transactions are generated for managing tiered files, including I/O happening on tiered files, in addition to egress costs. Although the quantity and type of transactions is difficult to predict due to churn rates and cache efficiency, you can use your previous transaction patterns to estimate future costs if you believe your future usage will be similar to your current usage. |
23 | | - |
24 | | - - **Transactions from cloud enumeration.** Azure File Sync enumerates the Azure File Share in the cloud once per day to discover changes that were made directly to the share so that they can sync down to the server endpoints. This scan generates transactions which are billed to the storage account at a rate of one `ListFiles` transaction per directory per day. You can put this number into the [pricing calculator](https://azure.microsoft.com/pricing/calculator/) to estimate the scan cost. |
| 22 | + - **IOPS / throughput utilization**: Azure File Sync drives IOPS and throughput utilization to transfer changes from your server endpoints to your Azure file share. If you are using a provisioned file share, you should monitor your file share usage to ensure that you have enough IOPS and throughput provisioned that you aren't throttled. If you are using a pay-as-you-go file share, you are charged for the IOPS utilization in the form of transactions. Generally, there are two types of transactions to consider: |
| 23 | + - **Transactions from churn.** As files change on server endpoints, the changes are uploaded to the cloud share, which generates transactions. When cloud tiering is enabled, additional transactions are generated for managing tiered files, including I/O happening on tiered files, in addition to egress costs. Although the quantity and type of transactions is difficult to predict due to churn rates and cache efficiency, you can use your previous transaction patterns to estimate future costs if you believe your future usage will be similar to your current usage. |
| 24 | + |
| 25 | + - **Transactions from cloud enumeration.** Azure File Sync enumerates the Azure File Share in the cloud once per day to discover changes that were made directly to the share so that they can sync down to the server endpoints. This scan generates transactions which are billed to the storage account at a rate of one `ListFiles` transaction per directory per day. You can put this number into the [pricing calculator](https://azure.microsoft.com/pricing/calculator/) to estimate the scan cost. |
25 | 26 |
|
26 | | - > [!Tip] |
27 | | - > If you don't know how many folders you have, check out the TreeSize tool from JAM Software GmbH. |
| 27 | + > [!Tip] |
| 28 | + > If you don't know how many folders you have, check out the TreeSize tool from JAM Software GmbH. |
0 commit comments