This topic describes how to manage your snapshots and reduce snapshot fees.

Maintain an appropriate number of snapshots

The snapshot fee is based on the amount of storage space used by the snapshots. More snapshots require more disk storage space and result in higher snapshot fees. We recommend that you maintain an appropriate number of snapshots for your specific service requirements. The following table lists recommended retention periods for different scenarios.

Scenario Snapshot creation frequency Retention period Description
Core application Once every day or every other day Several months or longer We recommend that you create and store snapshots based on data importance.
Non-core application Once every week or every other week Several days or weeks We recommend that you create and store snapshots based on data importance.
System disk Whenever needed One or two snapshots We recommend that you do not store critical application data in the system disk.
Software upgrade Delete snapshots immediately after they are used. We recommend that you delete snapshots immediately after they are used to reduce fees.
Modification of critical files
Migration of application data
Test environment

Delete snapshots

You can delete snapshots that are no longer needed to free up space or when the maximum number of snapshots has been reached. For more information, see Delete a snapshot.

Disable unnecessary snapshot policies

You can disable unnecessary snapshot policies to avoid redundancy and reduce the amount of storage space used by snapshots. For more information, see Apply or disable an automatic snapshot policy.
Note To improve the operation error tolerance of your services, we recommend that you retain at least one snapshot policy for core services.