Snapshot management method and device, equipment and storage medium

Abstract

The invention discloses a snapshot management method and device, equipment and a storage medium, and relates to the technical field of computers, and the method comprises the steps: judging whether to trigger a snapshot deletion operation for a snapshot storage pool or not by monitoring the water level of the snapshot storage pool; if yes, determining a target snapshot deletion proportion, and analyzing snapshot information stored in each volume in the pool to determine a key snapshot; determining a similarity value between the key snapshots and the non-key snapshots in each volume to obtain a target snapshot list; determining a non-key snapshot total capacity, a key snapshot total capacity and a to-be-released capacity based on the target snapshot deletion proportion and the target snapshot list, and triggering and finishing a non-key snapshot deletion operation according to the non-key snapshot total capacity and the to-be-released capacity; and based on the updated to-be-released capacity and the state of a preset key snapshot deletion switch, determining whether to trigger a key snapshot deletion operation at present. According to the invention, dynamic snapshot management can be realized based on the use condition of the snapshot storage pool, and important snapshots are protected.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and particularly to a snapshot management method, apparatus, device, and storage medium. Background Art

[0002] In modern data storage systems, the frequent creation and retention of timed snapshots can lead to rapid consumption of storage space, especially when the storage pool capacity is limited, this problem is particularly prominent.

[0003] However, in existing snapshot management related solutions, a simple fixed number or fixed ratio of snapshot deletion is often adopted, and the fixed snapshot deletion strategy cannot adapt to different usage levels of the storage pool. For example, when the storage pool capacity is sufficient, snapshots may be deleted unnecessarily, increasing the risk of data loss or affecting the data recovery function; while when the storage pool is close to full capacity, the number of snapshots deleted may be insufficient, unable to effectively release space, thus affecting the normal operation of the storage system. In addition, these solutions often handle snapshot deletion roughly, and may accidentally delete important snapshots, which may then lead to incomplete or unavailable parts of the data.

[0004] It can be seen that how to dynamically manage snapshots considering the storage pool capacity and protect the data integrity and availability of important snapshots is an urgent problem for those skilled in the art. Summary of the Invention

[0005] The purpose of the embodiments of the present invention is to provide a snapshot management method, apparatus, device, and storage medium, which can solve the problem of how to dynamically manage snapshots considering the storage pool capacity and protect the data integrity and availability of important snapshots.

[0006] To solve the above technical problems, the embodiments of the present invention provide a snapshot management method, apparatus, device, and storage medium, which can monitor the water level to achieve dynamic snapshot management based on the usage of the snapshot storage pool, avoiding the adverse effects such as poor adaptability caused by the fixed snapshot deletion method in the existing solutions, thereby effectively managing the life cycle of snapshots and improving the utilization rate and management efficiency of the snapshot storage pool; on the other hand, by identifying critical and non-critical snapshots, targeted snapshot deletion operations are performed, so as to ensure the protection of the data integrity and availability of important snapshots while releasing the storage pool space, and ensure the availability and integrity of the data, thereby improving the data protection ability. The specific solutions are as follows:

[0007] In a first aspect, the present invention provides a snapshot management method, including:

[0008] By monitoring the water level of the snapshot storage pool and combining with the pre-configured snapshot deletion policy to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result;

[0009] When the deletion judgment result is yes, determine the target snapshot deletion ratio at the current water level, and analyze the snapshot information stored in each volume in the snapshot storage pool to determine the critical snapshots;

[0010] Based on a preset algorithm, determine the similarity values between the critical snapshots and non-critical snapshots in each volume to obtain the target snapshot list corresponding to the snapshot storage pool;

[0011] Based on the target snapshot deletion ratio and the target snapshot list, determine the total capacity of non-critical snapshots, the total capacity of critical snapshots, and the capacity to be released, and trigger the non-critical snapshot deletion operation according to the total capacity of non-critical snapshots and the capacity to be released;

[0012] After completing the non-critical snapshot deletion operation, update the capacity to be released, and determine whether to trigger the critical snapshot deletion operation currently based on the updated capacity to be released and the status of the preset critical snapshot deletion switch to complete the snapshot management process.

[0013] Optionally, by monitoring the water level of the snapshot storage pool and combining with the pre-configured snapshot deletion policy to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result, including:

[0014] Obtain the pre-configured snapshot deletion policy;

[0015] Obtain the used capacity of the snapshot storage pool based on the preset monitoring time point information, and determine the current water level based on the used capacity and the total capacity information corresponding to the snapshot storage pool;

[0016] By comparing the current water level and the preset water level threshold information in the snapshot deletion policy, determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result.

[0017] Optionally, when the deletion judgment result is yes, determine the target snapshot deletion ratio at the current water level, and analyze the snapshot information stored in each volume in the snapshot storage pool to determine the critical snapshots, including:

[0018] When the deletion judgment result indicates that the current water level is greater than any of the preset water level thresholds in the preset water level threshold information, determine the target snapshot deletion ratio corresponding to the current water level based on the snapshot deletion policy and the deletion judgment result;

[0019] Collect information on the stored snapshots in each volume of the snapshot storage pool, and store the information based on a preset data structure to determine the snapshot information corresponding to each volume; the snapshot information includes snapshot type, number of snapshots, and snapshot capacity.

[0020] Define critical snapshots respectively based on the snapshot information corresponding to each volume to determine the critical snapshots corresponding to each volume.

[0021] Optionally, determine the similarity values between the critical snapshots and non-critical snapshots in each volume based on a preset algorithm to obtain a target snapshot list corresponding to the snapshot storage pool, including:

[0022] Select the current volume from the volumes that have not been selected yet, and sequentially determine the similarity values between each non-critical snapshot and each critical snapshot in the current volume based on a preset algorithm.

[0023] For any non-critical snapshot in the current volume, determine the target similarity value from the multiple similarity values corresponding to any current non-critical snapshot based on a preset comparison strategy, and determine whether to update any non-critical snapshot to a critical snapshot by comparing the target similarity value with a preset similarity threshold, and then jump back to the step of selecting the current volume from the volumes that have not been selected yet.

[0024] When all volumes have been traversed, count the snapshot names, critical snapshot types, and similarity values to determine the target snapshot list corresponding to the snapshot storage pool.

[0025] Optionally, trigger the non-critical snapshot deletion operation according to the total capacity of non-critical snapshots and the capacity to be released, including:

[0026] When the total capacity of non-critical snapshots is not less than the capacity to be released, determine the ratio of the non-critical snapshot capacity of each volume to the total capacity of non-critical snapshots based on an equal-proportion release strategy to determine the target ratio corresponding to each volume.

[0027] Determine the first target capacity to be released corresponding to each volume based on the target ratio and the capacity to be released.

[0028] In each volume, sort the non-critical snapshots based on the similarity values, and trigger the non-critical snapshot deletion operation based on the sorting result and the corresponding first target capacity to be released.

[0029] Optionally, determine whether to trigger the critical snapshot deletion operation currently based on the updated capacity to be released and the status of a preset critical snapshot deletion switch, including:

[0030] If the updated capacity to be released is not zero and the status of the preset critical snapshot deletion switch is in the on state, determine the deletion priority information corresponding to the critical snapshots of each type based on the critical snapshot type.

[0031] Determine the capacity of the critical snapshot with the first deletion priority based on the deletion priority information to determine the first critical snapshot capacity;

[0032] Judge whether the first critical snapshot capacity is greater than the updated capacity to be released to obtain the first capacity judgment result;

[0033] If the first capacity judgment result is yes, delete the critical snapshot with the deletion priority information of the first deletion priority based on the equal - ratio release strategy;

[0034] If the first capacity judgment result is no, after deleting the critical snapshot with the deletion priority information of the first deletion priority, determine the current second target capacity to be released, and judge whether the capacity of the second critical snapshot corresponding to the second deletion priority is greater than the current second target capacity to be released to obtain the second capacity judgment result;

[0035] If the second capacity judgment result is yes, delete the critical snapshot with the deletion priority information of the second deletion priority based on the equal - ratio release strategy to complete the critical snapshot deletion operation.

[0036] Optionally, determining whether to trigger the critical snapshot deletion operation currently based on the updated capacity to be released and the state of the preset critical snapshot deletion switch includes:

[0037] If the updated capacity to be released is not zero and the state of the preset critical snapshot deletion switch is off, issue an alarm based on the preset alarm strategy and the updated capacity to be released.

[0038] In a second aspect, the present invention also provides a snapshot management device, including:

[0039] A water level monitoring module, configured to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently by monitoring the water level of the snapshot storage pool and combining the pre - configured snapshot deletion strategy to obtain a deletion judgment result;

[0040] A critical snapshot determination module, configured to determine the target snapshot deletion ratio at the current water level when the deletion judgment result is yes, and determine the critical snapshot by analyzing the snapshot information stored in each volume in the snapshot storage pool;

[0041] A snapshot list determination module, configured to determine the similarity value between the critical snapshots and non - critical snapshots in each volume based on a preset algorithm to obtain a target snapshot list corresponding to the snapshot storage pool;

[0042] A deletion trigger module, configured to determine the total capacity of non - critical snapshots, the total capacity of critical snapshots, and the capacity to be released based on the target snapshot deletion ratio and the target snapshot list, and trigger a non - critical snapshot deletion operation according to the total capacity of non - critical snapshots and the capacity to be released;

[0043] A management completion module, configured to update the capacity to be released after completing the non-critical snapshot deletion operation, and determine whether a critical snapshot deletion operation is currently triggered based on the updated capacity to be released and the status of a preset critical snapshot deletion switch, so as to complete the snapshot management process.

[0044] In a third aspect, the present invention discloses an electronic device, including:

[0045] A memory, configured to store a computer program;

[0046] A processor, configured to execute the computer program to implement the steps of the foregoing disclosed snapshot management method.

[0047] In a fourth aspect, the present invention discloses a computer-readable storage medium, configured to store a computer program; wherein, when the computer program is executed by a processor, the steps of the foregoing disclosed snapshot management method are implemented.

[0048] It can be seen that the present invention monitors the water level of the snapshot storage pool, and combines a pre-configured snapshot deletion policy to determine whether a snapshot deletion operation is currently triggered for the snapshot storage pool to determine the deletion judgment result; when the deletion judgment result is yes, the target snapshot deletion ratio at the current water level is determined, and by analyzing the snapshot information stored in each volume in the snapshot storage pool, critical snapshots are determined; based on a preset algorithm, the similarity value between the critical snapshots and non-critical snapshots in each volume is determined to obtain a target snapshot list corresponding to the snapshot storage pool; based on the target snapshot deletion ratio and the target snapshot list, the total capacity of non-critical snapshots, the total capacity of critical snapshots, and the capacity to be released are determined, and a non-critical snapshot deletion operation is triggered according to the total capacity of non-critical snapshots and the capacity to be released; after completing the non-critical snapshot deletion operation, the capacity to be released is updated, and based on the updated capacity to be released and the status of a preset critical snapshot deletion switch, it is determined whether a critical snapshot deletion operation is currently triggered to complete the snapshot management process.

[0049] As can be seen from the above technical solution, the application first monitors the water level of the snapshot storage pool, and combines the pre-configured snapshot deletion policy to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result; when the deletion judgment result is yes, the target snapshot deletion ratio at the current water level is determined, and by analyzing the snapshot information stored in each volume in the snapshot storage pool, the critical snapshots are determined; then, based on a preset algorithm, the similarity values between the critical snapshots and non-critical snapshots in each volume are determined to obtain a target snapshot list corresponding to the snapshot storage pool; then, based on the target snapshot deletion ratio and the target snapshot list, the total capacity of non-critical snapshots, the total capacity of critical snapshots, and the capacity to be released are determined, and a non-critical snapshot deletion operation is triggered according to the total capacity of non-critical snapshots and the capacity to be released; after the non-critical snapshot deletion operation is completed, the capacity to be released is updated, and based on the updated capacity to be released and the status of the preset critical snapshot deletion switch, it is determined whether to trigger a critical snapshot deletion operation currently, so as to complete the snapshot management process. That is to say, the present invention provides a dynamic snapshot management method based on the water level of the snapshot storage pool. Whether to trigger snapshot deletion is judged based on the monitored current water level. If triggered, the target snapshot deletion ratio at the current water level is determined, and then the critical snapshots are determined by analyzing the snapshot information stored in each volume in the snapshot storage pool, and the similarity between the critical snapshots and non-critical snapshots in each volume is determined to determine the target snapshot list. Finally, based on the target snapshot list and the target snapshot deletion ratio, non-critical snapshots are deleted first, and after completion, it is judged whether to delete critical snapshots. In this way, on the one hand, it is possible to realize dynamic snapshot management based on the usage of the snapshot storage pool by monitoring the water level, avoiding the adverse effects such as poor adaptability caused by the fixed snapshot deletion method in the existing solutions, so as to effectively manage the life cycle of snapshots and improve the utilization rate and management efficiency of the snapshot storage pool; on the other hand, by identifying the critical and non-critical snapshots, the snapshot deletion operation is carried out targeted, so as to ensure the protection of the data integrity and availability of important snapshots while releasing the storage pool space, and ensure the availability and integrity of the data, thereby improving the data protection ability. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to illustrate the embodiments of the present invention more clearly, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0051] Figure 1 It is a flowchart of a snapshot management method provided by an embodiment of the present invention;

[0052] Figure 2Schematic diagram of a specific snapshot list determination process provided by an embodiment of the present invention;

[0053] Figure 3 Schematic diagram of a snapshot in a certain volume in a snapshot storage pool provided by an embodiment of the present invention;

[0054] Figure 4 Schematic diagram of a specific snapshot deletion process provided by an embodiment of the present invention;

[0055] Figure 5 Schematic diagram of the structure of a snapshot management device provided by an embodiment of the present invention;

[0056] Figure 6 Structural diagram of an electronic device disclosed by the present invention. Specific embodiments

[0057] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0058] The terms "including" and "having" in the specification of the present invention and any variations related to "including" and "having" are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may include unlisted steps or units.

[0059] In order to enable those skilled in the art to better understand the solution of the present invention, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

[0060] See Figure 1 As shown, an embodiment of the present invention discloses a snapshot management method, including:

[0061] Step S11: Determine whether to trigger a snapshot deletion operation on the snapshot storage pool by monitoring the water level of the snapshot storage pool and combining a pre-configured snapshot deletion policy, so as to determine the deletion judgment result.

[0062] Combine Figure 2As shown, in this embodiment, it is necessary to first set the deletion policy of the snapshot. The policy includes: different deletion ratios configured for different water levels, the similarity threshold below which a snapshot is defined as a critical snapshot, whether to delete critical snapshots when the capacity is insufficient, etc. Among them, the deletion ratio can be custom-configured with ratio values at multiple water levels, and the ratio can be directly selected based on the information in the policy during subsequent use. That is, first obtain the pre-configured snapshot deletion policy; then obtain the used capacity of the snapshot storage pool based on the preset monitoring time point information, and determine the current water level based on the used capacity and the total capacity information corresponding to the snapshot storage pool; by comparing the current water level and the preset water level threshold information in the snapshot deletion policy, determine whether to trigger a snapshot deletion operation on the snapshot storage pool to obtain the deletion judgment result. It can be understood that the storage pool water level represents the ratio of the used capacity in the storage pool to the total capacity of the storage pool. As Figure 2 shown, the policy can be configured to start the snapshot deletion process when the used capacity is greater than 85% of the total capacity of the storage pool. Conversely, if it is less than 85%, it is considered that there is still enough space in the storage pool at this time, and there is no need to release space by deleting snapshots, and the water level continues to be monitored.

[0063] Meanwhile, it can be understood that the monitoring can be custom-set to real-time monitoring or periodic monitoring. Among them, periodic monitoring can be implemented through the management software of the storage system, and the preset monitoring time point information can be set to every hour or every day. In this way, it is possible to dynamically determine whether to start the snapshot deletion process by monitoring the usage of the snapshot storage pool, so as to effectively manage the storage pool space and avoid insufficient storage pool space or unnecessary snapshot deletion.

[0064] Step S12: When the deletion judgment result is yes, determine the target snapshot deletion ratio at the current water level, and determine the critical snapshots by analyzing the snapshot information stored in each volume in the snapshot storage pool.

[0065] Specifically, in this embodiment, if the deletion judgment result indicates that a snapshot deletion operation is currently triggered on the snapshot storage pool, the template snapshot deletion ratio at the current water level is determined according to the content related to the deletion ratio in the snapshot deletion policy. That is, when the deletion judgment result shows that the current water level is greater than any of the preset water level thresholds in the preset water level threshold information, the target snapshot deletion ratio corresponding to the current water level is determined based on the snapshot deletion policy and the deletion judgment result. It can be understood that, for example, in a specific implementation, if the current water level of the storage pool is greater than 85% and less than 90%, it is determined that 5% of the total snapshot capacity needs to be deleted; if the current water level is greater than 90% and less than 95%, it is determined that 10% of the total snapshot capacity needs to be deleted; if the current water level is greater than 95%, it is determined that 15% of the total snapshot capacity needs to be deleted.

[0066] Combined with Figure 2As shown in the figure, further, when determining to perform snapshot deletion, it is necessary to not only determine the target snapshot deletion ratio, but also collect snapshot information and perform the first round of key snapshot definition. Specifically, first collect the information of the snapshots stored in each volume in the snapshot storage pool, and store the information based on a preset data structure to determine the snapshot information corresponding to each volume; the snapshot information includes snapshot type, number of snapshots, and snapshot capacity; then perform key snapshot definition respectively based on the snapshot information corresponding to each volume to determine the key snapshots corresponding to each volume. It should be understood that for each volume in the storage pool, traverse all the snapshots therein, obtain snapshot information such as snapshot type, number, capacity, and policy information from the metadata of the storage system or the snapshot management module, and then the collected snapshot information can be stored in a special data structure, such as a hash table containing volume identifiers and snapshot information, and perform a round of key snapshot definition, such as defining the first snapshot, the last snapshot, the snapshot used by the user for mounting, the locked snapshot, etc. in the volume as key snapshots. In this way, comprehensive information collection and detailed classification of snapshots can be carried out, especially initially defining key type snapshots, so as to better protect important snapshots during the snapshot management process.

[0067] Step S13: Determine the similarity values between the key snapshots and non-key snapshots in each volume based on a preset algorithm to obtain a target snapshot list corresponding to the snapshot storage pool.

[0068] In this embodiment, combined with Figure 2 As shown in the figure, after determining the key snapshots, it is necessary to further define them by analyzing the similarity between the snapshots, that is, determine the key snapshots, and then the target snapshot list including all volumes can be obtained based on the finally determined key snapshots, non-key snapshots and related information. Specifically, described from the perspective of any volume, first select the current volume from the volumes that have not been selected yet, and sequentially determine the similarity values between each non-key snapshot and each key snapshot in the current volume based on a preset algorithm; for any non-key snapshot in the current volume, determine the target similarity value from the multiple similarity values corresponding to any current non-key snapshot based on a preset comparison strategy, and determine whether to update any non-key snapshot to a key snapshot by comparing the target similarity value with a preset similarity threshold, and then jump back to the step of selecting the current volume from the volumes that have not been selected yet; when all volumes have been traversed, count the snapshot names, key snapshot types, and similarity values to determine the target snapshot list corresponding to the snapshot storage pool. Among them, methods such as data hashing or feature vectors can be used to determine the similarity values between the snapshots. For example, for file system-based storage, the hash value of the file content or the feature vector of the file metadata can be calculated, and then the similarity value between two snapshots can be determined based on these values. For example, in a specific implementation, there are 12 snapshots in volume A, combined with Figure 3The first 7 snapshots in Volume A are shown as follows: snap1, snap2, snap3, snap4, snap5, snap6, and snap7, where A1, B1, C1, D1…I8, J7 are the data in the snapshots. Since snap1 is the first snapshot and snap7 is the locked snapshot, snap1 and snap7 can be initially defined as critical snapshots. The similarity values and criticality analysis of the other snapshots (snap2, snap3, snap4, snap5, snap6) are as follows:

[0069] 1) The similarity between snap2 and snap1 is 80%, and the similarity between snap2 and snap7 is 0%. Finally, the similarity of snap2 is 80%, which is greater than 20%. Proceed to the analysis of the next snapshot;

[0070] 2) The similarity between snap3 and snap1 is 40%, and the similarity between snap3 and snap7 is 0%. Finally, the similarity of snap3 is 40%, which is greater than 20%. Proceed to the analysis of the next snapshot;

[0071] 3) The similarity between snap4 and snap1 is 0%, and the similarity between snap3 and snap7 is 0%. Finally, the similarity of snap3 is 0%, which is less than 20%. Then snap4 becomes a critical snapshot, and the recursive algorithm is used to re-analyze the similarity values of the snapshots between snap1 and snap4;

[0072] 4) The similarity between snap2 and snap1 is 80%, and the similarity between snap2 and snap4 is 0%. Finally, the similarity of snap2 is 80%, which is greater than 20%. Proceed to the analysis of the next snapshot;

[0073] 5) The similarity between snap3 and snap1 is 40%, and the similarity between snap3 and snap7 is 20%. Finally, the similarity of snap3 is 40%, which is greater than 20%. Proceed to the analysis of the next snapshot;

[0074] 6) The similarity between snap5 and snap4 is 30%, and the similarity between snap5 and snap7 is 0%. Finally, the similarity of snap5 is 30%, which is greater than 20%. Proceed to the analysis of the next snapshot;

[0075] 7) The similarity between snap6 and snap4 is 0%, and the similarity between snap6 and snap7 is 40%. Finally, the similarity of snap6 is 40%, which is greater than 20%. Proceed to the analysis of the next snapshot;

[0076] And so on, find the key snapshots in the volume and the similarity values between other snapshots and the key snapshots, update the key or non-key attributes of the snapshots, and process other volumes in the same way. Finally, output a list of target snapshots for all volumes, which contains information such as the key or non-key attributes of the snapshots, snapshot capacity, snapshot name, volume to which it belongs, similarity value, etc. An example of the target snapshot list is shown in Table 1 below.

[0077] Table 1

[0078]

[0079] It can be seen from this that the target snapshot list not only contains the key or non-key attributes of the snapshots, but also records the key snapshot types for the key snapshots.

[0080] In this way, through the snapshot similarity analysis, the second round of key snapshot definition is carried out, which further optimizes the snapshot management, improves the rationality of the key snapshot definition, and lays a solid foundation for the subsequent targeted snapshot deletion operation according to the capacity situations of non-key snapshots and key snapshots.

[0081] Step S14: Based on the target snapshot deletion ratio and the target snapshot list, determine the total non-key snapshot capacity, total key snapshot capacity, and the capacity to be released, and trigger the non-key snapshot deletion operation according to the total non-key snapshot capacity and the capacity to be released.

[0082] Combined with Figure 4 As shown, after determining the target snapshot list, based on the target snapshot list and the previously determined target snapshot deletion ratio, the total snapshot capacity size, the total capacity sizes of key snapshots and non-key snapshots, and the total capacity size to be released can be quickly calculated. Then, based on the total capacity to be released and the total non-key snapshot capacity, a judgment is made to follow different deletion processes according to the judgment results, either proportional deletion or full deletion. Regarding the relevant steps of proportional deletion, when the total non-key snapshot capacity is not less than the capacity to be released, first determine the ratio of the non-key snapshot capacity of each volume to the total non-key snapshot capacity based on the proportional release strategy to determine the corresponding target ratio for each volume; based on the target ratio and the capacity to be released, determine the corresponding first target capacity to be released for each volume; in each volume, sort the non-key snapshots based on the similarity value, and trigger the non-key snapshot deletion operation based on the sorting result and the corresponding first target capacity to be released.

[0083] In a specific implementation, if the current water level is 92% and the total snapshot capacity is 1T (the total key snapshot capacity is 300G and the total non-key snapshot capacity is 700G), then according to the snapshot deletion strategy, the total capacity to be released can be , the specific process of deleting non-critical snapshots at this time is as follows: Since the total capacity of non-critical snapshots > the total capacity to be released (700G > 100G), an equal-proportion release strategy is adopted, that is, determine the proportion of the total capacity of non-critical snapshots in each volume to the total capacity of all non-critical snapshots. As shown in Table 1 above, the total capacity of non-critical snapshots in Volume A is 70G, accounting for 10% of the total capacity of non-critical snapshots. Then the capacity to be deleted from Volume A is 10G (10% of the total released capacity of 100G). This can not only ensure the size of the released capacity but also ensure that the larger the capacity occupied, the larger the release. Further, in Volume A, non-critical snapshots are sorted according to similarity, and those with high similarity are preferentially deleted. When the accuracy is insufficient, one more or one less snapshot is deleted upward at the same time. For example, in Volume A, snap2 is first deleted, which is less than 10G. If one more snapshot is deleted upward, then snap8 is deleted. If one less snapshot is deleted downward, then snap8 is not deleted. And so on, delete non-critical snapshots with high similarity in the volume to release the capacity space.

[0084] In addition, when performing equal-proportion deletion of non-critical snapshots in this embodiment, the non-critical snapshots can be further classified. Specifically, it can be achieved by analyzing attributes such as the importance of the content in the snapshots, the similarity and correlation between non-critical snapshots, and the location of the snapshots to further classify the non-critical snapshots, define the deletion priority for each category, and delete them in sequence based on the priority until the deleted capacity reaches the total capacity to be released. In this way, the precise management of snapshots in the storage pool can be further optimized.

[0085] Step S15: After completing the operation of deleting non-critical snapshots, update the capacity to be released, and determine whether the current critical snapshot deletion operation is triggered based on the updated capacity to be released and the state of the preset critical snapshot deletion switch to complete the snapshot management process.

[0086] Specifically, in this embodiment, considering the situation where the total capacity of non-critical snapshots < the total capacity to be released, after the non-critical snapshot deletion operation is completed, the capacity to be released is updated, and it is considered whether the critical snapshot deletion switch is turned on. If it is turned on, the hierarchical deletion process of critical snapshots is triggered; otherwise, an alarm is issued. Regarding the relevant steps of the hierarchical deletion process of critical snapshots: If the updated capacity to be released is not zero and the state of the preset critical snapshot deletion switch is the on state, the deletion priority information corresponding to various types of critical snapshots is determined based on the critical snapshot type; based on the deletion priority information, the capacity of the critical snapshot with the first deletion priority is determined to determine the first critical snapshot capacity; it is judged whether the first critical snapshot capacity is greater than the updated capacity to be released to obtain a first capacity judgment result; if the first capacity judgment result is yes, the critical snapshot with the deletion priority information of the first deletion priority is deleted based on the equal proportion release strategy; if the first capacity judgment result is no, after deleting the critical snapshot with the deletion priority information of the first deletion priority, the current second target capacity to be released is determined, and it is judged whether the second critical snapshot capacity corresponding to the second deletion priority is greater than the current second target capacity to be released to obtain a second capacity judgment result; if the second capacity judgment result is yes, the critical snapshot with the deletion priority information of the second deletion priority is deleted based on the equal proportion release strategy to complete the critical snapshot deletion operation. It can be seen that when deleting critical snapshots, the deletion priority is determined in combination with the critical snapshot type, and then the critical snapshots are deleted in sequence according to the priority until the deleted capacity reaches the updated capacity to be released, or all critical snapshots are deleted. In this way, snapshots that are important for data integrity, availability, etc. can be better protected. For example, mounted snapshots and locked snapshots will not be easily deleted, thus ensuring the normal use of data and compliance requirements.

[0087] In a specific implementation manner, assume that the total capacity of non-critical snapshots is 60G, that is, the total capacity of non-critical snapshots < the total capacity to be released (60G < 100G). Then, all non-critical snapshots are deleted first, and further judgment is made. Further, it is first judged whether the critical snapshot deletion switch is turned on. If it is not turned on, an alarm is issued, indicating that the non-critical snapshot space is insufficient, and the capacity release gap is 40G; if it is turned on, the capacity that needs to be released for critical snapshots is calculated, such as 40G; then, according to the classification importance of critical snapshots, critical snapshots are deleted hierarchically. The deletion is carried out in the order of the first snapshot, the identified critical snapshot, the last snapshot, the locked snapshot, etc. The snapshot in use during mounting is not deleted. That is, the first snapshot of all volumes is deleted first, and then it is compared whether the released capacity is greater than or equal to 40G. If it is satisfied, the process ends; if it is not satisfied, the critical snapshot of the next priority is continued to be deleted, and so on.

[0088] Furthermore, regarding alarms, it can be understood that alarms generally occur when the total capacity of non-critical snapshots is less than the capacity to be released and the critical snapshot deletion switch is not turned on. That is, if the updated capacity to be released is not zero and the state of the preset critical snapshot deletion switch is off, an alarm is generated based on the preset alarm policy and the updated capacity to be released. The information sent during the alarm can be generated based on a pre-configured template, such as "Insufficient space in non-critical snapshots, the release capacity gap is **(total capacity to be released minus the total capacity of non-critical snapshots), it is recommended...", and then the alarm information can be sent through channels such as the microphone and the front-end page to remind the user that the space released by the snapshot is insufficient. If you want to ensure the continuity of the business, you need to increase the deletion ratio or manually delete the data. In this way, the overall management performance of the storage system is improved.

[0089] In summary, the snapshot management method disclosed by the present invention has the following beneficial effects:

[0090] (1) Optimize the storage pool space management. Dynamically adjust the snapshot deletion ratio according to the actual usage of the storage pool, which can effectively avoid the situation of insufficient or excessive occupation of the storage pool space. For example, during the peak usage period of the storage pool, a certain proportion of snapshots are reasonably deleted to release space and ensure the normal operation of the storage system; during the low usage period of the storage pool, unnecessary snapshot deletions are avoided to protect the recoverability of the data.

[0091] (2) Improve the data protection ability. By classifying snapshots in detail and determining critical snapshots based on similarity, snapshots that are important for data integrity, availability, etc. can be better protected. For example, mounted snapshots and locked snapshots will not be easily deleted, thus ensuring the normal use of the data and compliance requirements.

[0092] (3) Improve the overall efficiency of the storage system. A reasonable snapshot management scheme reduces unnecessary snapshot storage and improves the read and write performance of the storage system. At the same time, through targeted snapshot deletion operations, the complexity of snapshot management is reduced, and the overall management efficiency of the storage system is improved.

[0093] It can be seen that the present invention monitors the water level of the snapshot storage pool, and combines the pre-configured snapshot deletion policy to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result; when the deletion judgment result is yes, the target snapshot deletion ratio at the current water level is determined, and by analyzing the snapshot information stored in each volume in the snapshot storage pool, the critical snapshots are determined; the similarity values between the critical snapshots and the non-critical snapshots in each volume are determined based on a preset algorithm to obtain a target snapshot list corresponding to the snapshot storage pool; the total capacity of the non-critical snapshots, the total capacity of the critical snapshots and the capacity to be released are determined based on the target snapshot deletion ratio and the target snapshot list, and the non-critical snapshot deletion operation is triggered according to the total capacity of the non-critical snapshots and the capacity to be released; after the non-critical snapshot deletion operation is completed, the capacity to be released is updated, and based on the updated capacity to be released and the status of the preset critical snapshot deletion switch, it is determined whether to trigger a critical snapshot deletion operation currently, so as to complete the snapshot management process.

[0094] As can be seen from the above technical solution, the application first monitors the water level of the snapshot storage pool, and combines the pre-configured snapshot deletion policy to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result; when the deletion judgment result is yes, the target snapshot deletion ratio at the current water level is determined, and the snapshot information stored in each volume in the snapshot storage pool is analyzed to determine the key snapshots; then, based on a preset algorithm, the similarity values between the key snapshots and non-key snapshots in each volume are determined to obtain a target snapshot list corresponding to the snapshot storage pool; then, based on the target snapshot deletion ratio and the target snapshot list, the total capacity of non-key snapshots, the total capacity of key snapshots, and the capacity to be released are determined, and a non-key snapshot deletion operation is triggered according to the total capacity of non-key snapshots and the capacity to be released; after the non-key snapshot deletion operation is completed, the capacity to be released is updated, and based on the updated capacity to be released and the status of the preset key snapshot deletion switch, it is determined whether to trigger a key snapshot deletion operation currently, so as to complete the snapshot management process. That is, the present invention provides a dynamic snapshot management method based on the water level of the snapshot storage pool. Whether to trigger snapshot deletion is judged based on the monitored current water level. If triggered, the target snapshot deletion ratio at the current water level is determined, and then the key snapshots are determined by analyzing the snapshot information stored in each volume in the snapshot storage pool, and the similarity between the key snapshots and non-key snapshots in each volume is determined to determine the target snapshot list. Finally, based on the target snapshot list and the target snapshot deletion ratio, non-key snapshots are deleted first, and after completion, it is judged whether to delete key snapshots. In this way, on the one hand, it is possible to realize dynamic snapshot management based on the usage of the snapshot storage pool by monitoring the water level, avoiding the adverse effects such as poor adaptability caused by the fixed snapshot deletion method in the existing solutions, so as to effectively manage the life cycle of snapshots and improve the utilization rate and management efficiency of the snapshot storage pool; on the other hand, by identifying the key and non-key of snapshots, targeted snapshot deletion operations are carried out, so as to ensure the protection of the data integrity and availability of important snapshots while releasing the storage pool space, and ensure the availability and integrity of data, thereby improving the data protection ability.

[0095] See Figure 5 As shown, an embodiment of the present invention further provides a snapshot management device, including:

[0096] A water level monitoring module 11, configured to monitor the water level of the snapshot storage pool and combine the pre-configured snapshot deletion policy to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result;

[0097] A key snapshot determination module 12, configured to determine the target snapshot deletion ratio at the current water level when the deletion judgment result is yes, and analyze the snapshot information stored in each volume in the snapshot storage pool to determine the key snapshots;

[0098] A snapshot list determination module 13, configured to determine a similarity value between key snapshots and non-key snapshots in each volume based on a preset algorithm, so as to obtain a target snapshot list corresponding to the snapshot storage pool;

[0099] A deletion trigger module 14, configured to determine the total capacity of non-key snapshots, the total capacity of key snapshots, and the capacity to be released based on the target snapshot deletion ratio and the target snapshot list, and trigger a non-key snapshot deletion operation according to the total capacity of non-key snapshots and the capacity to be released;

[0100] A management completion module 15, configured to update the capacity to be released after the non-key snapshot deletion operation is completed, and determine whether to trigger a key snapshot deletion operation currently based on the updated capacity to be released and the state of a preset key snapshot deletion switch, so as to complete the snapshot management process.

[0101] Since the embodiments of the device part correspond to the above embodiments, the embodiments of the device part are described with reference to the embodiments of the above method part and will not be elaborated here.

[0102] It can be seen that the present invention determines whether to trigger snapshot deletion based on the monitored current water level. If triggered, it determines the target snapshot deletion ratio at the current water level, then determines key snapshots by analyzing the snapshot information stored in each volume in the snapshot storage pool, and determines the similarity between key snapshots and non-key snapshots in each volume to determine the target snapshot list. Finally, based on the target snapshot list and the target snapshot deletion ratio, non-key snapshots are deleted first, and after completion, it is determined whether to delete key snapshots. In this way, on the one hand, it is possible to monitor the water level to achieve dynamic snapshot management based on the usage of the snapshot storage pool, avoiding the adverse effects such as poor adaptability caused by the fixed snapshot deletion method in the existing solution, thereby effectively managing the life cycle of snapshots and improving the utilization rate and management efficiency of the snapshot storage pool; on the other hand, by identifying key and non-key snapshots and performing snapshot deletion operations in a targeted manner, it is possible to ensure the protection of the data integrity and availability of important snapshots while releasing the storage pool space, and guarantee the availability and integrity of the data, thereby improving the data protection ability.

[0103] Further, an embodiment of the present invention also discloses an electronic device, Figure 6It is a structural diagram of an electronic device shown according to an exemplary embodiment. The content in the figure should not be regarded as any limitation on the scope of use of the present invention. The electronic device may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. Among them, the memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the snapshot management method disclosed in any of the foregoing embodiments. In addition, the electronic device in this embodiment may specifically be an electronic computer.

[0104] In this embodiment, the power supply 23 is used to provide working voltages for each hardware device on the electronic device; the communication interface 24 can create a data transmission channel between the electronic device and external devices, and the communication protocol it follows is any communication protocol applicable to the technical solution of the present invention, and specific limitations are not imposed on it here; the input / output interface 25 is used to obtain external input data or output data to the outside, and its specific interface type can be selected according to specific application needs, and specific limitations are not imposed here.

[0105] In addition, as a carrier for resource storage, the memory 22 may be a read-only memory, a random access memory, a magnetic disk, or an optical disc, etc. The resources stored thereon may include an operating system 221, a computer program 222, etc., and the storage method may be transient storage or permanent storage.

[0106] Among them, the operating system 221 is used to manage and control each hardware device and the computer program 222 on the electronic device, and it may be Windows Server, Netware, Unix, Linux, etc. In addition to the computer program that can be used to complete the snapshot management method executed by the electronic device disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs that can be used to complete other specific tasks.

[0107] Furthermore, the present invention also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the snapshot management method disclosed above is implemented. For the specific steps of this method, reference may be made to the corresponding content disclosed in the foregoing embodiments, and details are not repeated here.

[0108] In this specification, the various embodiments are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts among the various embodiments can be referred to each other. For the device disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the description in the method part.

[0109] Those skilled in the art may further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0110] The steps of the methods or algorithms described in combination with the embodiments disclosed herein can be directly implemented by hardware, software modules executed by a processor, or a combination of both. The software modules can be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the technical field.

[0111] Finally, it should also be noted that in this text, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the existence of additional identical elements in the process, method, article or device comprising the element.

[0112] The technical solutions provided by the present invention have been introduced in detail above. Specific examples have been used herein to elaborate on the principles and implementation manners of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation manners and application scopes. In summary, the content of this specification should not be construed as a limitation to the present invention.

Claims

1. A snapshot management method, characterized in that, Including: Monitoring the water level of the snapshot storage pool, and combining with the pre-configured snapshot deletion policy to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result; When the deletion judgment result is yes, determine the target snapshot deletion ratio at the current water level, and analyze the snapshot information stored in each volume in the snapshot storage pool to determine the critical snapshots; Determine the similarity values between the critical snapshots and non-critical snapshots in each volume based on a preset algorithm to obtain a target snapshot list corresponding to the snapshot storage pool; Determine the total capacity of non-critical snapshots, the total capacity of critical snapshots, and the capacity to be released based on the target snapshot deletion ratio and the target snapshot list, and trigger a non-critical snapshot deletion operation according to the total capacity of non-critical snapshots and the capacity to be released; After completing the non-critical snapshot deletion operation, update the capacity to be released, and determine whether to trigger a critical snapshot deletion operation currently based on the updated capacity to be released and the status of the preset critical snapshot deletion switch, so as to complete the snapshot management process.

2. The snapshot management method according to claim 1, wherein The step of monitoring the water level of the snapshot storage pool, and combining with the pre-configured snapshot deletion policy to determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently, so as to determine the deletion judgment result, includes: Obtain the pre-configured snapshot deletion policy; Obtain the used capacity of the snapshot storage pool based on the preset monitoring time point information, and determine the current water level based on the used capacity and the total capacity information corresponding to the snapshot storage pool; Judge whether to trigger a snapshot deletion operation on the snapshot storage pool currently by comparing the current water level and the preset water level threshold information in the snapshot deletion policy, so as to determine the deletion judgment result.

3. The snapshot management method according to claim 2, wherein The step of when the deletion judgment result is yes, determine the target snapshot deletion ratio at the current water level, and analyze the snapshot information stored in each volume in the snapshot storage pool to determine the critical snapshots, includes: When the deletion judgment result indicates that the current water level is greater than any one of the preset water level thresholds in the preset water level threshold information, determine the target snapshot deletion ratio corresponding to the current water level based on the snapshot deletion policy and the deletion judgment result; Collect information on the snapshots stored in each volume in the snapshot storage pool, and store the information based on a preset data structure to determine the snapshot information corresponding to each volume; the snapshot information includes snapshot type, number of snapshots, and snapshot capacity; Define critical snapshots respectively based on the snapshot information corresponding to each volume to determine the critical snapshots corresponding to each volume.

4. The snapshot management method according to any one of claims 1 to 3, characterized in that The step of determining the similarity values between the critical snapshots and non-critical snapshots in each volume based on a preset algorithm to obtain a target snapshot list corresponding to the snapshot storage pool, includes: Select the current volume from the volumes that have not been selected yet, and determine the similarity values between each non-critical snapshot and each critical snapshot in the current volume in sequence based on a preset algorithm; For any of the non-critical snapshots in the current volume, determine a target similarity value from multiple similarity values corresponding to any of the current non-critical snapshots based on a preset comparison strategy, and determine whether to update any of the non-critical snapshots to a critical snapshot by comparing the target similarity value with a preset similarity threshold, and then re-jump to the step of selecting the current volume from the volumes that have not been selected yet; When all volumes have been traversed, count the snapshot names, critical snapshot types, and the similarity values to determine a target snapshot list corresponding to the snapshot storage pool.

5. The snapshot management method according to claim 1, wherein The triggering of the non-critical snapshot deletion operation according to the total capacity of the non-critical snapshots and the capacity to be released includes: When the total capacity of the non-critical snapshots is not less than the capacity to be released, determine the ratio of the non-critical snapshot capacity of each volume to the total capacity of the non-critical snapshots based on an equal-proportion release strategy to determine the target ratio corresponding to each volume; Determine the first target capacity to be released corresponding to each volume based on the target ratio and the capacity to be released; In each volume, sort the non-critical snapshots based on the similarity value, and trigger the non-critical snapshot deletion operation based on the sorting result and the corresponding first target capacity to be released.

6. The snapshot management method according to claim 5, wherein The determining whether to trigger the critical snapshot deletion operation currently based on the updated capacity to be released and the state of the preset critical snapshot deletion switch includes: If the updated capacity to be released is not zero and the state of the preset critical snapshot deletion switch is the on state, determine the deletion priority information corresponding to the critical snapshots of each type based on the critical snapshot type; Determine the capacity of the critical snapshot with the first deletion priority based on the deletion priority information to determine the first critical snapshot capacity; Judge whether the first critical snapshot capacity is greater than the updated capacity to be released to obtain a first capacity judgment result; If the first capacity judgment result is yes, delete the critical snapshot with the deletion priority information of the first deletion priority based on the equal-proportion release strategy; If the first capacity judgment result is no, after deleting the critical snapshot with the deletion priority information of the first deletion priority, determine the current second target capacity to be released, and judge whether the second critical snapshot capacity corresponding to the second deletion priority is greater than the current second target capacity to be released to obtain a second capacity judgment result; If the second capacity judgment result is yes, delete the critical snapshot with the deletion priority information of the second deletion priority based on the equal-proportion release strategy to complete the critical snapshot deletion operation.

7. The snapshot management method according to claim 1, wherein The determining whether to trigger the critical snapshot deletion operation currently based on the updated capacity to be released and the state of the preset critical snapshot deletion switch includes: If the updated capacity to be released is not zero and the state of the preset critical snapshot deletion switch is the off state, issue an alarm based on a preset alarm strategy and the updated capacity to be released.

8. A snapshot management device, characterized in that, Including: A water level monitoring module, which is used to monitor the water level of the snapshot storage pool, and determine whether to trigger a snapshot deletion operation on the snapshot storage pool currently by combining the pre-configured snapshot deletion policy, so as to determine the deletion judgment result; A key snapshot determination module, which is used to determine the target snapshot deletion ratio at the current water level and determine the key snapshots by analyzing the snapshot information stored in each volume in the snapshot storage pool when the deletion judgment result is yes; A snapshot list determination module, which is used to determine the similarity value between the key snapshots and non-key snapshots in each volume based on a preset algorithm to obtain a target snapshot list corresponding to the snapshot storage pool; A deletion trigger module, which is used to determine the total capacity of non-key snapshots, the total capacity of key snapshots, and the capacity to be released based on the target snapshot deletion ratio and the target snapshot list, and trigger a non-key snapshot deletion operation according to the total capacity of non-key snapshots and the capacity to be released; A management completion module, which is used to update the capacity to be released after completing the non-key snapshot deletion operation, and determine whether to trigger a key snapshot deletion operation currently based on the updated capacity to be released and the state of a preset key snapshot deletion switch, so as to complete the snapshot management process.

9. An electronic device, characterized in that, Comprising: A memory, which is used to store computer programs; A processor, which is used to implement the steps of the snapshot management method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein the computer program implements the steps of the snapshot management method according to any one of claims 1 to 7 when executed by a processor.

Images