Shulou(Shulou.com)06/02 Report--

This article will explain in detail the methods of optimizing the cost of using snapshots. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

How to optimize the cost of snapshot usage

Snapshots recommend scenarios

As a convenient and efficient data protection service, snapshot is recommended to be used in the following business scenarios:

Daily backup of system disk and data disk. You can use snapshots to back up important business data on a regular basis to deal with the risk of data loss caused by misoperation, attacks, viruses, etc.

Replace the operating system. Before major operations such as application software upgrade or business data migration, you can create one or more data snapshots. If there are any problems during the upgrade or migration process, you can restore to the normal system data state in time through the data snapshots.

Multi-copy application of production data. By creating snapshots of production data, you can provide near-real-time production data for applications such as data mining, report query, development testing, and so on.

Keep a reasonable number of snapshots

Snapshots are charged according to the storage capacity occupied, so the more snapshots are retained, the more storage capacity is consumed, and the snapshot fees will increase. Therefore, in order to reduce the unnecessary cost of using snapshots, it is recommended that you set a reasonable snapshot policy and retain an appropriate number of snapshots according to your actual business needs.

Business scenarios and recommendations are shown in the table below.

In this way, regular backup of data can be achieved without overly expensive costs. At the same time, snapshots support prepaid storage packages and postpaid by quantity, making it easy for you to choose a consumption model that is suitable for you.

How to delete snapshots that create mirrors and disks

Snapshots, mirrors, disks, and instances are currently bound. Resetting the system disk initialization disk feature all depends on the binding relationship between the above. In April 2017, we decoupled the binding relationship between "mirror and instance" and "snapshot and disk".

The image of the created instance can be deleted separately, but after deletion, it is similar to the business operation that depends on the original mirror data, such as reinitializing the disk.

Create a snapshot of the disk, which can be deleted separately. Similarly, after deletion, business operations that depend on the original snapshot data state, such as reinitializing the disk, cannot be operated.

A snapshot of a mirror has been created. Before deleting, you need to delete the corresponding mirror before deleting it.

This is the end of the way to optimize the cost of snapshot use. I hope the above content can be helpful to you and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.