How to quickly and easily optimize snapshot usage costs

The content of this article is about how to quickly and easily optimize the cost of snapshot usage. It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.

How to optimize the cost of using snapshots

Recommended usage scenarios of snapshots

Snapshots are a convenient and efficient means of data protection services , recommended for use in the following business scenarios:

Daily backup of system disks and data disks. You can use snapshots to regularly back up important business data to deal with the risk of data loss caused by misoperations, attacks, viruses, etc.

Change the operating system. Before major operations such as application software upgrade or business data migration, you can create one or more data snapshots. Once any problems occur during the upgrade or migration process, you can use the data snapshots to restore the normal system data state in a timely manner.

Multi-copy application of production data. You can create snapshots of production data to provide near-real-time real production data for applications such as data mining, report query, and development testing.

Retain a reasonable number of snapshots

Snapshots are charged according to the occupied storage capacity, so the more snapshots are retained, the more The larger the storage capacity, the higher the snapshot fees incurred. Therefore, in order to reduce unnecessary snapshot usage costs, it is recommended that you set a reasonable snapshot policy and retain an appropriate number of snapshots based on actual business needs.

Business scenarios and suggestions are shown in the table below.

#In this way, regular backup of data can be achieved without incurring excessive expenses. At the same time, Snapshot supports prepaid storage packages and pay-as-you-go models, allowing you to choose a consumption model that suits you.

How to delete a snapshot that creates a mirror and a disk

The snapshot, mirror, disk, and instance are currently bound, reset the system Disk initialization and disk functions all depend on the above mutual binding relationships. In April 2017, we have decoupled the binding relationship between "image and instance" and "snapshot and disk".

The image of the instance that has been created can be deleted separately. However, after deletion, business operations that rely on the original image data, such as reinitializing the disk operation, will not be able to operate;

The image that has created the disk Snapshots can be deleted individually. After deletion, business operations that rely on the data status of the original snapshot, such as reinitializing disk operations, will become inoperable;

After creating a mirrored snapshot, you need to delete all the snapshots before deleting them. The corresponding image can be deleted.

The above is the detailed content of How to quickly and easily optimize snapshot usage costs. For more information, please follow other related articles on the PHP Chinese website!