Billing of General-purpose NAS file systems

The following table describes the fees that you need to pay after you convert the storage class and use resource plans.

Note 3: Converted base capacity

When you use NAS resource plans to offset storage usage fees, the offset factor varies depending on the file system type, the storage class, and the region of the file system. When you purchase resource plans, you need to convert prices according to the preceding information. For more information, see Offset factors.

As shown in the preceding tables:

• If data is stored in a Capacity NAS file system, you can save 23.83% of the storage cost by converting the storage class and using resource plans, compared with storing all data in the Standard storage class.

• If data is stored in a Premium NAS file system, you can save 64.85% of the storage cost by converting the storage class and using resource plans, compared with storing all data in the Standard storage class.

• If data is stored in a Performance NAS file system, you can save 69.53% of the storage cost by converting the storage class and using resource plans, compared with storing all data in the Standard storage class.

Example 1: Share data for web services

On November 1, 2024, Mr. Wang deployed a shared-storage web service in a Capacity NAS file system in the China (Hangzhou) region. The service is expected to use 500 GiB of storage capacity per hour. In this case, the total fee of the month is USD 30, as shown in the following table.

Example 2: Access IA data

Mr. Zhang created a Performance NAS file system in the China (Hangzhou) region. The storage usage of the file system is 100 GiB per hour in November 2024. 10 GiB of data is stored in the Standard storage class, and 90 GiB of data is stored in the IA storage class. The read traffic of the IA storage class is 1 GiB and the write traffic of the IA storage class is 2 GiB within the month. In this case, the total fee of the month is USD 5.11767, as shown in the following table.

Example 3: Implement cross-region disaster recovery based on NAS file systems

On November 1, 2024, Mr. Zhang stored 150 GiB of files in a Performance NAS file system (File System A) in the China (Beijing) region. To further improve the security and reliability of data and prevent data loss or access interruptions caused by failures in a single region, Mr. Zhang created a cross-region backup policy for the file system to back up data on a regular basis. If exceptions such as natural disasters and power failures occur in a region, Mr. Zhang can still use the data in the backup vault to recreate a file system (File System B), thus ensuring business continuity. In this case, the total fee of the month is USD 59.5418, as shown in the following table.

³ When you back up data, Cloud Backup deduplicates and compresses the data. Therefore, the amount billed in this scenario is the amount of deduplicated and compressed data.

Example 4: Automatically dump and clean up NAS data

On November 1, 2024, Mr. Zhang created a Capacity NAS file system in the China (Beijing) region. The storage usage of the file system is 1,000 GiB per hour. All files are stored in the /mnt directory. To cope with changes in access requirements at different phases, Mr. Zhang configured the following lifecycle rules:

1. Phase 1: Data needs to be frequently accessed in this phase. All files in the /mnt directory are stored in the Standard storage class. This phase lasts 14 days.

2. Phase 2: Data is accessed less than once within 14 days. All files in the /mnt directory are dumped to the IA storage class. This phase lasts 16 days.

3. Phase 3: Data is accessed less than once within 30 days. All files in the /mnt directory are dumped to the Archive storage class. This phase lasts 5 days.

4. Phase 4: Data no longer needs to be retained. Delete all files in the /mnt directory after data is stored in the Archive storage class for 5 days.

In this case, the total fee of the month is USD 55.7425, as shown in the following table.

⁴ The minimum storage duration of the Archive storage class is 60 days. The minimum storage duration starts from the time when a file is modified, which is indicated by the mtime parameter. In this scenario, you are charged for the remaining storage duration of the archive data (60 - 5 = 55 days).

⁵ When files are being dumped, each file has a replica in the storage space of the original storage class and the new storage class. After the files are dumped, the file replicas in the original storage class are deleted. In this case, storage usage fees are incurred for the file replicas.

Example 5: Access archive data

Mr. Zhang created a Performance NAS file system in the China (Hangzhou) region. 100 GiB of data is stored in the file system. A lifecycle policy is configured for the file system to dump data to the Archive storage class 30 days later. On the 60th day, Mr. Zhang performed the following operations in sequence: overwrite 1 GiB of data in the Archive storage class, reduce the data size to 100 GiB, write 2 GiB of data to the Archive storage class, then reduce the data size to 101 GiB. On the 90th day, Mr. Zhang deleted 101 GiB of data from the Archive storage class. In this case, the total fee is USD 33.10626, as shown in the following table.

⁴ The minimum storage duration of the Archive storage class is 60 days. The minimum storage duration starts from the time when a file is modified, which is indicated by the mtime parameter. In this scenario, two penalty fees are incurred for the archive data that is stored for less than 60 days.

• Penalty fee 1: On the 60th day, data is overwritten and deleted within 24 hours. You are charged for the 100 GiB of data that is stored in the Archive storage class for less than 60 days. At this point, the storage duration of the data in the Archive storage class is reset.

• Penalty fee 2: On the 90th day, 101 GiB of data is deleted from the Archive storage class and the data is stored for less than 60 days.

⁵ When files are being dumped, each file has a replica in the storage space of the original storage class and the new storage class. After the files are dumped, the file replicas in the original storage class are deleted. In this case, storage usage fees are incurred for the file replicas.