適用於Azure NetApp Files 的成本模型Cost model for Azure NetApp Files

瞭解 Azure NetApp Files 的成本模型可協助您管理服務的費用。Understanding the cost model for Azure NetApp Files helps you manage your expenses from the service.

如需跨區域複寫的專用成本模型,請參閱 跨區域複寫的成本模型For cost model specific to cross-region replication, see Cost model for cross-region replication.

容量耗用量的計算Calculation of capacity consumption

Azure NetApp Files 的計費依據是布建的儲存體容量。Azure NetApp Files is billed on provisioned storage capacity. 布建的容量是藉由建立容量集區來配置。Provisioned capacity is allocated by creating capacity pools. 容量集區會依每小時遞增的 $/provisioned-GiB/month 計費。Capacity pools are billed based on $/provisioned-GiB/month in hourly increments. 單一容量集區的大小下限為 4 TiB,容量集區則可在 1 TiB 的增量下展開。The minimum size for a single capacity pool is 4 TiB, and capacity pools can be subsequently expanded in 1-TiB increments. 磁片區是在容量集區中建立的。Volumes are created within capacity pools. 每個磁片區都會被指派一個從集區布建容量遞減的配額。Each volume is assigned a quota that decrements from the pools-provisioned capacity. 可以指派給磁片區的配額範圍從最小 100 GiB 到最多 100 TiB。The quota that can be assigned to volumes ranges from a minimum of 100 GiB to a maximum of 100 TiB.

針對使用中的磁片區,根據配額的容量耗用量是以邏輯 (有效的) 容量為基礎,不論是使用中的檔案系統或快照集資料。For an active volume, capacity consumption against quota is based on logical (effective) capacity, either on active filesystem or snapshot data. 磁片區只能包含與設定大小 (配額) 一樣多的資料。A volume can only contain so much data as the set size (quota).

容量集區中針對其布建數量所使用的總容量是集區中所有磁片區實際耗用量的總和:The total used capacity in a capacity pool against its provisioned amount is the sum of the actual consumption of all volumes within the pool:

顯示已使用的總容量計算的運算式。

快照集的容量耗用量Capacity consumption of snapshots

Azure NetApp Files 中快照集的容量耗用量會依父磁片區的配額收費。The capacity consumption of snapshots in Azure NetApp Files is charged against the quota of the parent volume. 因此,它會與磁片區所屬的容量集區共用相同的計費費率。As a result, it shares the same billing rate as the capacity pool to which the volume belongs. 不過,與使用中的磁片區不同的是,快照耗用量是根據取用的增量容量來測量。However, unlike the active volume, snapshot consumption is measured based on the incremental capacity consumed. Azure NetApp Files 快照集本質上是差異。Azure NetApp Files snapshots are differential in nature. 根據資料的變更率,快照集的容量通常會比使用中磁片區的邏輯容量更少。Depending on the change rate of the data, the snapshots often consume much less capacity than the logical capacity of the active volume. 例如,假設您有一個 500 GiB 磁片區的快照集,其中只包含10個 GiB 的差異資料。For example, assume that you have a snapshot of a 500-GiB volume that only contains 10 GiB of differential data. 針對作用中檔案系統與快照集的磁片區配額計算的容量耗用量是 510 GiB,而不是 1000 GiB。The capacity consumption that is counted towards the volume quota for the active filesystem and snapshot would be 510 GiB, not 1000 GiB. 一般來說,根據快照頻率和應用程式的每日區塊層級變更率) ,建議假設有20% 的容量可以保留一周的快照集資料 (。As a general rule, a recommended 20% of capacity can be assumed to retain a week's worth of snapshot data (depending on snapshot frequency and application daily block level change rates).

下圖說明這些概念。The following diagram illustrates the concepts.

  • 假設容量集區具有 40 TiB 的布建容量。Assume a capacity pool with 40 TiB of provisioned capacity. 集區包含三個磁片區:The pool contains three volumes:
    • 磁片區1被指派配額 20 TiB,有13個 TiB (12 個 TiB 使用中,1個 TiB 快照集) 的耗用量。Volume 1 is assigned a quota of 20 TiB and has 13 TiB (12 TiB active, 1 TiB snapshots) of consumption.
    • 磁片區2的配額指派為 1 TiB,且具有 450 GiB 的耗用量。Volume 2 is assigned a quota of 1 TiB and has 450 GiB of consumption.
    • 磁片區3指派了14個 TiB 的配額,但具有 8.8 TiB (8 TiB 主動、800 GiB 快照) 的耗用量。Volume 3 is assigned a quota of 14 TiB but has 8.8 TiB (8 TiB active, 800 GiB snapshots) of consumption.
  • 容量集區會以 40 TiB 的容量計費 (布建的數量) 。The capacity pool is metered for 40 TiB of capacity (the provisioned amount). 22.25 TiB 的容量是從磁片區1、2和 3) (13 TiB、450 GiB 和 8.8 TiB 配額來取用。22.25 TiB of capacity is consumed (13 TiB, 450 GiB and 8.8 TiB of quota from Volumes 1, 2 and 3). 容量集區具有 17.75 TiB 的剩餘容量。The capacity pool has 17.75 TiB of capacity remaining.

圖表顯示具有三個磁片區的容量集區。

下一步Next steps