CN116756091A - Snapshot management method, electronic device and storage medium - Google Patents
Snapshot management method, electronic device and storage medium Download PDFInfo
- Publication number
- CN116756091A CN116756091A CN202311057814.4A CN202311057814A CN116756091A CN 116756091 A CN116756091 A CN 116756091A CN 202311057814 A CN202311057814 A CN 202311057814A CN 116756091 A CN116756091 A CN 116756091A
- Authority
- CN
- China
- Prior art keywords
- snapshot
- released
- cache
- cache area
- resource
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 62
- 238000000034 method Methods 0.000 claims abstract description 28
- 230000004083 survival effect Effects 0.000 claims description 28
- 230000005012 migration Effects 0.000 claims description 20
- 238000013508 migration Methods 0.000 claims description 20
- 230000009467 reduction Effects 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 14
- 230000000737 periodic effect Effects 0.000 claims description 11
- 238000004140 cleaning Methods 0.000 abstract description 4
- 238000013500 data storage Methods 0.000 abstract description 2
- 230000003139 buffering effect Effects 0.000 description 11
- 238000001514 detection method Methods 0.000 description 10
- 238000012790 confirmation Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 230000006872 improvement Effects 0.000 description 8
- 238000005192 partition Methods 0.000 description 8
- 101001116774 Homo sapiens Methionine-R-sulfoxide reductase B2, mitochondrial Proteins 0.000 description 7
- 102100024862 Methionine-R-sulfoxide reductase B2, mitochondrial Human genes 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013528 artificial neural network Methods 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 238000007796 conventional method Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 238000002372 labelling Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/128—Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a snapshot management method, electronic equipment and a storage medium, and relates to the technical field of data storage, wherein the snapshot management method comprises the following steps: detecting whether the storage resource corresponding to the snapshot is released or not, and obtaining the snapshot corresponding to the released storage resource; after the snapshot corresponding to the released storage resource is detected, the snapshot is migrated into a corresponding cache area according to the snapshot type of the snapshot; one cache area corresponds to one snapshot type, and each cache area is provided with a resource release condition; and releasing the snapshot when the snapshot meets the resource release condition of the corresponding cache region. The method and the device can improve management efficiency, reduce cache time of the snapshot and save storage resources of the cloud platform; in addition, the cloud platform actively releases the snapshot, so that subsequent manual cleaning is avoided, and labor cost is saved.
Description
Technical Field
The present application relates to the field of data storage technologies, and in particular, to a snapshot management method, an electronic device, and a storage medium.
Background
The main function of the snapshot is data backup and recovery. When the storage resource has application failure or file damage, the snapshot is used for carrying out rapid data restoration, so that the data is restored to a state corresponding to a certain available time point.
The storage resource and the snapshot are two independent products, and the life cycle of the two independent products is independent. After the storage resources are released, their corresponding snapshots are not immediately released. The snapshot may continue to occupy the storage space of the cloud platform until the snapshot reaches its corresponding lifecycle, or is manually cleaned by an administrator.
However, the above method may cause waste of storage resources of the cloud platform, and additional manpower cost is required for manually cleaning the snapshot by an administrator.
Disclosure of Invention
In view of the above, the application provides a snapshot management method, electronic equipment and a storage medium, which can improve management efficiency, reduce cache time of snapshots, save storage resources of a cloud platform, avoid subsequent manual cleaning and save labor cost.
In a first aspect, an embodiment of the present application provides a snapshot management method, including:
detecting whether the storage resource corresponding to the snapshot is released or not, and obtaining the snapshot corresponding to the released storage resource;
after detecting that the released storage resource corresponds to the storage resource, according to the snapshot type of the snapshot, migrating the snapshot into a corresponding cache area; one cache area corresponds to one snapshot type, and each cache area is provided with a resource release condition;
And releasing the snapshot when the snapshot meets the resource release condition of the corresponding cache region.
Through adopting this technical scheme, after detecting that the storage resource that the snapshot corresponds is released, according to the snapshot type of snapshot, with the snapshot migration into corresponding buffer area, carry out partition management to the snapshot that the storage resource corresponds that is released, improve management efficiency, when the snapshot satisfies the resource release condition of corresponding buffer area, release the snapshot in advance, be favorable to the release in advance of snapshot, be convenient for reduce the buffer time of snapshot, and then practice thrift cloud platform storage resource, moreover, can make the cloud platform initiatively release the snapshot, reduce the condition emergence of manual clearance snapshot, practice thrift the human cost.
In one possible implementation, the snapshot type includes: periodic snapshots and permanent snapshots;
and according to the snapshot type of the snapshot, migrating the snapshot into a corresponding cache area, including:
when the snapshot type of the snapshot is a permanent snapshot, the snapshot is migrated into a first cache area, and a first resource release condition is set in the first cache area and is used for detecting whether the snapshot in the first cache area is released or not;
And when the snapshot type of the snapshot is a regular snapshot, the snapshot is migrated into a second cache area, and the second cache area is provided with a second resource release condition which is used for detecting whether to release the snapshot in the second cache area.
By adopting the technical scheme, snapshots of different snapshot types are migrated into different cache areas, and partition management is performed on the snapshots, so that management efficiency is improved.
In one possible implementation, the first resource release condition includes: the purpose of the snapshot is only data reduction;
after the snapshot is migrated into the first cache area, the method further includes:
determining a purpose of the snapshot;
releasing the snapshot when the use of the snapshot is only data reduction;
migrating the snapshot to a third cache region when the use of the snapshot includes other uses than data reduction; the third cache region is provided with a first preset cache time, and the first preset cache time is permanent.
By adopting the technical scheme, after the snapshot is migrated into the first cache area, the purpose of the snapshot is confirmed, and when the purpose of the snapshot meets the first release condition, the snapshot is released, so that the storage resources of the cloud platform are saved; when the purpose of the snapshot does not meet the first release condition, the snapshot is migrated to the third cache area for permanent storage, and subsequent unified management is facilitated.
In one possible implementation manner, the detecting whether the storage resource corresponding to the snapshot is released, to obtain the snapshot corresponding to the released storage resource includes:
obtaining each snapshot stored currently, and periodically detecting whether the storage resources corresponding to each snapshot stored currently are released or not, so as to obtain the snapshots corresponding to the released storage resources;
and/or detecting whether there are released storage resources; if the released storage resource exists, detecting whether the released storage resource corresponds to the snapshot in the survival state, and obtaining the snapshot corresponding to the released storage resource.
By adopting the technical scheme, whether the snapshot needs to be migrated or not is determined by periodically detecting whether the storage resource corresponding to the snapshot is released or not, or the snapshot migration is triggered by releasing the storage resource, so that the instantaneity of the snapshot migration can be ensured as much as possible under the condition that the storage resource is released, and the occupation time of the snapshot to the storage resource of the cloud platform is further reduced.
In one possible implementation manner, the second buffer area is provided with a second preset buffer time, and the second resource release condition includes: and under the condition that the second preset caching time is greater than zero, taking the minimum value of the remaining survival time of the snapshot and the second preset caching time as the release time of the snapshot.
Compared with releasing the snapshot at the end of the life cycle of the snapshot, the embodiment of the application compares the current residual survival time of the snapshot with the second preset cache time, takes the minimum value of the current residual survival time of the snapshot and the second preset cache time as the release time of the snapshot, and can enable the release time of the snapshot to be smaller than or equal to the residual survival time of the current snapshot, thereby reducing the cache time of the snapshot and saving the storage resources of the cloud platform.
In one possible implementation, the second resource release condition further includes: and under the condition that the second preset caching time is zero, immediately releasing the snapshot.
By adopting the technical scheme, under the condition that the second preset caching time is zero, the second caching area immediately releases the migrated snapshot.
In one possible implementation, the method further includes:
and displaying the snapshots of different snapshot types in different display areas, wherein one snapshot type corresponds to one display area.
In one possible implementation manner, according to a snapshot type of the snapshot, migrating the snapshot into a corresponding cache area includes:
determining a cache region identifier corresponding to the snapshot type according to the snapshot type of the snapshot; and marking the cache area on the snapshot mark.
Compared with the physical migration partition, the snapshot in the embodiment of the application is logical migration, namely, the physical storage position of the snapshot is maintained unchanged, the snapshot is marked as the corresponding cache area in a marked snapshot or partition display mode, and the consumption of software and hardware resources caused by the migration of the physical storage position is reduced.
In a second aspect, an embodiment of the present application provides a snapshot management device, where the device has a function of implementing the method provided in the first aspect. The functions may be realized by hardware, or may be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.
In a third aspect, an embodiment of the present application provides a storage medium having stored thereon a computer program which, when executed by a processor, implements the snapshot management method of the first aspect.
In a fourth aspect, an embodiment of the present application provides an electronic device, where the electronic device includes a processor and a memory, where the memory is configured to store instructions, and the processor is configured to invoke the instructions in the memory, so that the electronic device performs the snapshot management method according to the first aspect.
In a fifth aspect, embodiments of the present application provide a computer program product for, when run on a computer, causing the computer to perform the snapshot management method as described in the first aspect.
It will be appreciated that the snapshot management device according to the second aspect, the storage medium according to the third aspect, the electronic device according to the fourth aspect, and the computer program product according to the fifth aspect correspond to the method according to the first aspect, and therefore, the advantages achieved by the snapshot management device according to the second aspect may refer to the advantages in the corresponding method provided above, and are not repeated herein.
Drawings
In order to more clearly illustrate the application or the technical solutions of the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the application, and other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is one of the flowcharts of a snapshot management method shown in an exemplary embodiment of the present application;
FIG. 2 is a second flow chart of a snapshot management method according to an exemplary embodiment of the present application;
FIG. 3 is a third flow chart of a snapshot management method shown in an exemplary embodiment of the present application;
FIG. 4 is a fourth flow chart of a snapshot management method shown in an exemplary embodiment of the present application;
FIG. 5 is a fifth flowchart of a snapshot management method according to an exemplary embodiment of the present application
FIG. 6 is a sixth flow chart of a snapshot management method shown in an exemplary embodiment of the present application;
FIG. 7 is a seventh flow chart of a snapshot management method shown in an exemplary embodiment of the present application;
FIG. 8 is a schematic diagram of a snapshot management device according to an exemplary embodiment of the present application;
fig. 9 is a schematic diagram of a hardware structure of an electronic device according to an exemplary embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without any inventive effort, are intended to be within the scope of the application.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities.
That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described.
For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
In the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and the representation may have three relationships, for example, a and/or B may represent: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The terms "first," "second," "third," "fourth" and the like in the description and in the claims and drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.
Referring to fig. 1, fig. 1 is one of flowcharts of a snapshot management method according to an exemplary embodiment of the present application, where an execution subject of the snapshot management method may be a cloud platform.
The flow of this embodiment is shown in fig. 1, and includes the following steps:
step 110, detecting whether the storage resource corresponding to the snapshot is released, and obtaining the snapshot corresponding to the released storage resource.
Specifically, a snapshot and a storage resource are mutually corresponding, wherein if a snapshot is a fully available copy of data in a storage resource, it is indicated that the snapshot and the storage resource have a correspondence.
The copy includes an image of the data of the storage resource at a point in time. The snapshot may be a copy of the data of its corresponding storage resource or a copy of the data of its corresponding storage resource.
The snapshot can be used for data backup and recovery, and can be used for fast data restoration when the storage resource has application failure or file damage, and restoring the data to a state of a certain available time point, but the use of the snapshot is not limited to the state, and the snapshot can be used as a data source for testing and the like.
One storage resource may correspond to multiple snapshots, and one storage resource may also correspond to one snapshot. The storage resources may be, but are not limited to, cloud hard disks (Cloud Block Storage, CBS), file stores (Cloud File Storage, CFS), and the like.
For example, CBS1 corresponds to snapshot 1, snapshot 2, and both snapshot 1 and snapshot 2 may assist CBS1 in data reduction in the event of a CBS1 failure or file corruption.
Storage resources may be freed up for reasons such as end of service. The cloud platform detects whether storage resources corresponding to the snapshot are released or not.
In some embodiments, step 110 may include: and acquiring each snapshot stored currently, and periodically detecting whether the storage resources corresponding to each snapshot stored currently are released or not to obtain the snapshot corresponding to the released storage resources.
The period may be determined according to the actual resource release requirement and the detection of occupied software and hardware resources, which is not specifically limited in the embodiment of the present application.
For example, the period may be set to 1 hour, 6 hours, 12 hours, 24 hours, or the like. The cloud platform detects whether storage resources corresponding to all the snapshots are released or not once every other period.
In other embodiments, step 110 may include: detecting whether the released storage resource exists or not; if the released storage resource exists, detecting whether the released storage resource corresponds to the snapshot in the survival state, and obtaining the snapshot corresponding to the released storage resource.
That is, in this embodiment, if a message that a certain storage resource is released is detected, for example, the cloud platform is triggered to detect whether there is a corresponding snapshot that survives the storage resource, and the snapshot that is in a survived state and corresponds to the released storage resource is used as the snapshot that corresponds to the released storage resource.
That is, the detection mode may be detection at intervals of a preset time, or may satisfy a preset detection condition, for example, a certain storage resource is released, detection is triggered, or a detection mode combining the two.
For example, the cloud platform periodically detects whether storage resources corresponding to all the snapshots are released. When the cloud platform detects that the storage resources are released, the cloud platform detects whether the storage resources have corresponding snapshots or not to survive.
Step 120, after detecting the snapshot corresponding to the released storage resource, migrating the snapshot into the corresponding cache area according to the snapshot type of the snapshot.
Specifically, the cloud platform sets a plurality of cache areas, and one cache area corresponds to one snapshot type. The cache region may cache a snapshot having a corresponding snapshot type.
The snapshot type may be determined based on the lifecycle of the snapshot. If the snapshot type can be classified into a regular snapshot and a permanent snapshot, the regular snapshot is typically released after the life cycle of the snapshot is completed, e.g., the life cycle of a snapshot is 15 days, after the snapshot creation is successfully started, and after 15 days, the snapshot is released.
The life cycle of the periodic snapshot may be set according to practical application requirements, for example, may also be set to 30 days, which is not limited in the embodiment of the present application.
A permanent snapshot is a long-term preserved snapshot that typically requires an administrator to manually clean the permanent snapshot before it can be released.
After the snapshot corresponding to the released storage resource is detected, the cloud platform determines the snapshot type to which the snapshot corresponding to the released storage resource belongs, and the snapshot is migrated into the cache region corresponding to the snapshot type.
And 130, releasing the snapshot when the snapshot meets the resource release condition of the corresponding cache region.
Specifically, each cache area is provided with a resource release condition.
Wherein the release time of the snapshot may be determined based on the resource release condition.
The release time of the snapshot determined based on the resource release condition is less than or equal to the remaining survival time of the snapshot when the snapshot is migrated into the cache region.
After the snapshot is migrated to the corresponding cache region, the cloud platform detects whether the snapshot meets the resource release condition of the corresponding cache region in real time, and releases the snapshot when the snapshot meets the resource release condition of the corresponding cache region.
For easy understanding, the snapshot management method of the present embodiment is specifically illustrated below:
assuming that the storage resource is CBS1, CBS1 corresponds to snapshot 1, and the snapshot type of snapshot 1 is a regular snapshot. Assuming that the cache area 1 corresponds to a regular snapshot, the resource release condition of the cache area 1 is that the snapshot cache time is up to 24 hours.
The cloud platform detects whether CBS1 is released. After detecting that CBS1 is released, the cloud platform migrates snapshot 1 into cache region 1. After the snapshot 1 is migrated into the cache area 1, the cloud platform detects in real time whether the snapshot 1 meets the resource release condition of the cache area 1, that is, the cloud platform compares the current residual survival time of the snapshot 1 with the snapshot cache time in the resource release condition, and takes the snapshot cache time in the resource release condition as the release time of the snapshot 1 under the condition that the snapshot cache time in the resource release condition is smaller than the current residual survival time of the snapshot 1.
That is, upon detecting that the cache time of snapshot 1 in cache area 1 reaches 24 hours, the cloud platform releases snapshot 1.
According to the embodiment, after the fact that the storage resources corresponding to the snapshots are released is detected, the snapshots are migrated into the corresponding cache areas according to the snapshot types of the snapshots, and partition management is carried out on the snapshots corresponding to the released storage resources, so that management efficiency is improved; the embodiment can enable the release time of the snapshot to be smaller than or equal to the residual survival time when the snapshot is migrated into the corresponding cache region, so that when the snapshot meets the resource release condition of the corresponding cache region, the snapshot is released, and most of the situations are equivalent to the snapshot release in advance, the cache time of the snapshot is reduced, and the storage resources of the cloud platform are saved; in addition, the cloud platform actively releases the snapshot, so that subsequent manual cleaning is avoided, and labor cost is saved.
Referring to fig. 2, fig. 2 is a second flowchart of a snapshot management method according to an exemplary embodiment of the present application, and this embodiment is a further description of the foregoing embodiments, mainly describing: and the cloud platform moves the snapshot into the specific process of the corresponding cache region according to the snapshot type of the snapshot.
The flow of this embodiment is shown in fig. 2, and includes the following steps:
step 210, detecting whether the storage resource corresponding to the snapshot is released, and obtaining the snapshot corresponding to the released storage resource.
Step 220, after detecting the snapshot corresponding to the released storage resource, when the snapshot type of the snapshot is a permanent snapshot, migrating the snapshot into the first cache area; when the snapshot type of the snapshot is a regular snapshot, the snapshot is migrated into the second cache region.
Specifically, in some embodiments, snapshot types include permanent snapshots and regular snapshots.
And the cloud platform is provided with a first cache area and a second cache area corresponding to the snapshot type, wherein the first cache area corresponds to the permanent snapshot, and the second cache area corresponds to the periodic snapshot.
After the snapshot corresponding to the released storage resource is detected, when the snapshot type of the snapshot is a permanent snapshot, the cloud platform migrates the snapshot into a first cache area; when the snapshot type of the snapshot is a regular snapshot, the cloud platform migrates the snapshot into the second cache region.
The first cache region is provided with a first resource release condition, and the cloud platform detects whether to release the snapshot in the first cache region according to the first resource release condition. The second cache region is provided with a second resource release condition, and the cloud platform detects whether to release the snapshot in the second cache region according to the second resource release condition.
And step 230, releasing the snapshot when the snapshot meets the resource release condition of the corresponding cache region.
Step 210 and step 230 of this embodiment are similar to step 110 and step 130 of the previous embodiment, and are not repeated here.
According to the embodiment, the snapshots of the permanent snapshots are migrated into the first cache area, the snapshots of the regular snapshots are migrated into the second cache area, the snapshots of different snapshot types are migrated into different cache areas, and partition management is performed on the snapshots, so that the management efficiency is improved.
Referring to fig. 3, fig. 3 is a third flowchart of a snapshot management method according to an exemplary embodiment of the present application, which is a further improvement of the foregoing embodiment, and the main improvement is that: after the snapshot is migrated into the first cache area, the cloud platform releases the snapshot.
The flow of this embodiment is shown in fig. 3, and includes the following steps:
in step 310, it is detected whether the storage resource corresponding to the snapshot is released, and a snapshot corresponding to the released storage resource is obtained.
Step 320, after detecting the snapshot corresponding to the released storage resource, when the snapshot type of the snapshot is a permanent snapshot, migrating the snapshot into the first cache area.
At step 330, the purpose of the snapshot is determined.
Specifically, the first resource release condition includes that the purpose of the snapshot is only data reduction. After the snapshot is migrated into the first cache area, the cloud platform determines the purpose of the snapshot to detect whether the snapshot in the first cache area meets a first resource release condition.
In some embodiments, where the attribute information of the snapshot includes a purpose of the snapshot, the cloud platform may confirm the purpose of the snapshot by querying the attribute information of the snapshot.
Step 340, releasing the snapshot when the purpose of the snapshot meets the first resource release condition; and when the purpose of the snapshot does not meet the first resource release condition, migrating the snapshot to a third cache area.
Wherein the first resource release condition includes: the purpose of the snapshot is simply data reduction.
Specifically, in the case that the cloud platform determines that the purpose of the permanent snapshot is only data restoration, since the storage resources corresponding to the permanent snapshot are already released, the purpose of data restoration has no practical value, that is, the permanent snapshot has no cache value. Thus, when the purpose of the permanent snapshot is simply data reduction, the cloud platform releases the snapshot.
In the case that the cloud platform determines that the purpose of the permanent snapshot includes other purposes besides data restoration, such as quick deployment, although the storage resources corresponding to the permanent snapshot have been released, the purpose of data restoration has no actual value, and other purposes have actual value, that is, the permanent snapshot has a caching value. Therefore, when the purpose of the snapshot does not meet the first resource release condition, the cloud platform migrates the permanent snapshot from the first cache region to the third cache region. The third cache region is provided with a first preset cache time, and the first preset cache time is permanent.
After the snapshot is migrated to the third cache region, the snapshot will be permanently cached in the third cache region until manually cleaned.
Step 310 and step 320 of the present embodiment are similar to step 210 and step 220 of the previous embodiment, and are not repeated here.
Referring to Table 1 below, table 1 is a snapshot cache comparison table when the snapshot type is a permanent snapshot.
TABLE 1
For example, when the snapshot type is a permanent snapshot, as shown in table 1, in the case that the snapshot type is a permanent snapshot and the snapshot is only restored for data, the traditional method is to permanently save the snapshot until manually delete the snapshot after the storage resource is released, and the application releases the snapshot immediately after the storage resource is released. Since the storage resources corresponding to the snapshot have been freed, the snapshot has no caching value. Therefore, the traditional method permanently reserves the snapshot to waste the storage resources of the cloud platform, and the application immediately releases the snapshot to save the storage resources of the cloud platform.
As shown in table 1, in the case that the snapshot type is a permanent snapshot and the snapshot use is data restoration and quick deployment, the traditional method is to permanently save the snapshot after the storage resource is released, and the application is to permanently save the snapshot by migrating into the third cache area after the storage resource is released. Although the snapshots are permanently stored, the method and the system migrate the permanently stored snapshots to the same cache area, so that the permanently stored snapshots are convenient to be uniformly managed subsequently.
In the embodiment, after the snapshot is migrated into the first cache area, the purpose of the snapshot is confirmed, and when the purpose of the snapshot meets the first release condition, the snapshot is released, so that the storage resources of the cloud platform are saved; when the purpose of the snapshot does not meet the first release condition, the snapshot is migrated to the third cache area for permanent storage, and subsequent unified management is facilitated.
Referring to fig. 4, fig. 4 is a flowchart of a snapshot management method according to an exemplary embodiment of the present application, which is a further improvement of the foregoing embodiment, and the main improvement is that: the cloud platform determines the specific process of use of the snapshot.
The flow of this embodiment is shown in fig. 4, and includes the following steps:
In step 410, it is detected whether the storage resource corresponding to the snapshot is released, and the snapshot corresponding to the released storage resource is obtained.
Step 420, after detecting the snapshot corresponding to the released storage resource, when the snapshot type of the snapshot is a permanent snapshot, migrating the snapshot into the first cache area.
Step 430, send an acknowledgement message for confirming the snapshot usage.
Specifically, after the snapshot is migrated into the first cache area, the cloud platform sends a confirmation message for confirming the purpose of the snapshot.
When the attribute information of the snapshot includes the snapshot purpose, the snapshot purpose is changed, and the snapshot purpose obtained by directly inquiring the attribute information of the snapshot by the cloud platform is incorrect under the condition that the snapshot purpose is not changed in the attribute information of the snapshot. Therefore, the cloud platform can accurately confirm the snapshot purpose by sending the confirmation message for confirming the snapshot purpose.
In some embodiments, the confirmation message may be a mail, and the cloud platform sends the mail for confirming the use of the snapshot to the snapshot manager, but is not limited thereto, and may be set according to requirements in practical applications.
Step 440, confirming the use of the snapshot according to the use information replied in response to the confirmation message.
Specifically, the cloud platform receives a purpose message replied in response to the confirmation message, the purpose message carries purpose information, and the purpose of the snapshot is confirmed according to the purpose information.
In some embodiments, the usage message may be mail, but is not limited thereto, and may be set according to requirements in practical applications. And the cloud platform receives the mail replied by the snapshot manager and confirms the purpose of the snapshot according to the purpose information in the mail.
In some embodiments, the usage information may be text information illustrating usage of the snapshot, and the usage information may also be code information characterizing usage of the snapshot, one code characterizing each usage of the snapshot. For example, "1" characterizes data restoration and "2" characterizes rapid deployment.
The method of confirming the snapshot usage in steps 430 to 400 is merely an example, and in the practical application process, the electronic device may also determine the snapshot usage according to the usage record of the snapshot, or may determine the snapshot usage according to other manners, which is not limited in the embodiment of the present application.
Step 450, releasing the snapshot when the purpose of the snapshot meets the first resource release condition; and when the purpose of the snapshot does not meet the first resource release condition, migrating the snapshot to a third cache area.
Step 410, step 420 and step 450 of the present embodiment are similar to step 310, step 320 and step 340 of the previous embodiments, and are not repeated here.
In this embodiment, the use of the snapshot is confirmed by sending the confirmation message, so as to accurately confirm the use of the snapshot, which is further beneficial to subsequently judging whether the use of the snapshot meets the first resource release condition.
In some embodiments, the second cache region is provided with a second preset cache time. Specifically, the second cache area is provided with a second preset cache time, wherein the second preset cache time is a value greater than or equal to 0.
The second resource release condition includes: and under the condition that the second preset caching time is greater than zero, taking the minimum value of the remaining survival time of the snapshot and the second preset caching time as the release time of the snapshot.
When the snapshot is migrated into the second cache area, the electronic device records the current residual survival time of the snapshot, compares the residual survival time with the second preset cache time under the condition that the second preset cache time is greater than zero, and takes the residual survival time as the resource release time of the snapshot if the residual survival time of the snapshot is less than the second preset cache time; and if the remaining survival time of the snapshot is greater than the second preset cache time, taking the second preset cache time as the resource release time of the snapshot.
And under the condition that the second preset caching time is greater than 0, the second caching area caches the migrated snapshot in a time-limited mode.
And under the condition that the second preset caching time is equal to 0, the second caching area does not cache the migrated snapshot and releases the snapshot immediately.
And when the cloud platform detects that the snapshot in the second cache region meets the second resource release condition, releasing the snapshot. And when the cloud platform detects that the snapshot in the second cache region does not meet the second resource release condition, continuing to cache the snapshot.
Referring to Table 2 below, table 2 is a snapshot cache comparison table for the case where the snapshot type is a regular snapshot.
TABLE 2
For example, table 2 is a snapshot cache comparison table when the snapshot type is a regular snapshot, and as shown in table 2, in the case that the snapshot type is a regular snapshot, the conventional method is to cache the snapshot according to the remaining survival time of the snapshot after the storage resource is released. In the application, when the snapshot type is the regular snapshot and the second preset caching time is 0, the snapshot in the second caching area is released immediately after the storage resource is released. According to the method and the device, when the snapshot type is the regular snapshot and the second preset caching time is 4 days, the second caching area caches the snapshot for 4 days at most, so that the caching time is greatly reduced, and the storage resources of the cloud platform are saved.
In this embodiment, the minimum value of the remaining survival time of the snapshot and the second preset buffering time is used as the release time of the snapshot, so that the buffering time is reduced, and the storage resources of the cloud platform are saved.
FIG. 5 is a fifth flow chart of a snapshot management method shown in an exemplary embodiment of the present application, as shown in FIG. 5, in an exemplary embodiment, the snapshot management method may include:
in step 501, a storage resource is created.
At step 502, a snapshot is created.
In step 503, the snapshot is stored in the original buffer.
In step 504, the snapshot of the original buffer is periodically checked.
In step 505, it is detected whether the storage resource corresponding to the snapshot is released.
In the case that the storage resource corresponding to the snapshot is released, step 506 is performed; in the case that the storage resource corresponding to the snapshot is not released, step 504 is performed.
In the above steps, each snapshot currently stored is periodically detected to obtain a snapshot corresponding to the released storage resource, in other embodiments, whether the released storage resource exists or not may also be detected, and if the released storage resource exists, whether the released storage resource corresponds to a snapshot in a surviving state is detected, so as to obtain a snapshot corresponding to the released storage resource.
In the actual application process, the snapshot mode is periodically detected or the storage resources are released, so that the detection mode is triggered, the snapshot corresponding to the released storage resources is obtained, the snapshot can be set according to the actual application requirements, and the embodiment of the application is not limited.
At step 506, the snapshot type of the snapshot is validated.
In the case that the snapshot type of the snapshot is a permanent snapshot, step 507 is performed; in the case that the snapshot type of the snapshot is a regular snapshot, step 512 is performed.
In step 507, the permanent snapshot is migrated to the first cache region.
Step 508, send a confirmation message confirming the snapshot usage.
Step 509, it is detected whether the snapshot also includes other uses in addition to data reduction.
Executing step 510 when the snapshot has other uses in addition to the data reduction use; when the snapshot has no other purpose other than data reduction, step 511 is performed.
And step 510, migrating the snapshot to a third cache area for permanent storage until manual deletion.
Step 511, release the snapshot.
At step 512, the periodic snapshot is migrated to the second cache region.
In step 513, the second preset buffering time is 0.
That is, it is detected whether the second preset buffering time of the second buffering area is 0.
In case the second preset buffering time is 0, step 511 is performed; if the second preset buffering time is not 0, step 514 is performed.
Step 514, detecting whether the remaining survival time is greater than a second preset buffering time.
If the remaining survival time is less than the second preset buffering time, step 515 is performed; in the event that the remaining survival time is greater than the second preset buffering time, step 516 is performed.
At step 515, after the remaining survival time has been reached, the snapshot is released.
That is, after the cache time of the snapshot in the second cache area reaches the remaining survival time, the snapshot is released.
In step 516, after the second preset buffering time is reached, the snapshot is released.
That is, after the cache time of the snapshot in the second cache area reaches the second preset cache time, the snapshot is released.
Referring to fig. 6, fig. 6 is a flowchart of a snapshot management method according to an exemplary embodiment of the present application, which is a further improvement of the foregoing embodiment, and the main improvement is that: and carrying out partition display on the snapshot.
The flow of this embodiment is shown in fig. 6, and includes the following steps:
at step 610, snapshots of different snapshot types are displayed in different display areas.
Specifically, the cloud platform sets corresponding display areas according to snapshot types, and one snapshot type corresponds to one display area. The cloud platform sets a first display area and a second display area according to snapshot types, such as permanent snapshots and periodic snapshots, wherein the snapshots of the permanent snapshots are displayed in the first display area, and the snapshots of the periodic snapshots are displayed in the second display area.
For example, snapshot types of snapshot 1 and snapshot 2 are permanent snapshots, and snapshot types of snapshot 3 and snapshot 4 are regular snapshots. Snapshot 1 and snapshot 2 are shown in the first display area and snapshot 3 and snapshot 4 are shown in the second display area.
After the snapshot is released, the cloud platform deletes the corresponding snapshot in the display area.
The snapshot migration in the embodiment of the application can be logically migration, namely, the physical storage position of the snapshot is maintained unchanged, and the logical migration of the snapshot is realized in a partition display mode.
For example, physical location 1 stores snapshot 1, physical location 2 stores snapshot 2, physical location 3 stores snapshot 3, and physical location 4 stores snapshot 4.
And the storage resource corresponding to the snapshot 3 is released, and the physical position 3 still stores the snapshot 3 in the process of migrating the snapshot 3 into the corresponding cache area, but the display area of the snapshot 3 is changed into the display area corresponding to the snapshot type.
According to the embodiment, different areas of the snapshot are displayed according to the snapshot type of the snapshot, on one hand, the cached snapshot is clearly known, and the snapshot is further beneficial to managing the snapshot.
Referring to fig. 7, fig. 7 is a flowchart of a snapshot management method according to an exemplary embodiment of the present application, which is a further improvement of the foregoing embodiment, and the main improvement is that: the snapshot is marked.
Step 710, determining a cache area identifier corresponding to the snapshot type according to the snapshot type of the snapshot, and marking the snapshot with the cache area identifier.
Specifically, according to the snapshot type of the snapshot, the migration of the snapshot into the corresponding cache region may include: maintaining the physical storage address of the snapshot unchanged, determining a cache area identifier corresponding to the snapshot type according to the storage type of the snapshot, and marking the cache area identifier on the snapshot.
Wherein one snapshot type corresponds to one cache region identifier. The application does not limit the form of the first mark and the second mark, and only the snapshots of different cache areas can be distinguished according to the first mark and the second mark.
For example, the cache area corresponding to the regular snapshot is identified as cache area a, and the cache area corresponding to the permanent snapshot is identified as cache area B.
The step of migrating the periodic snapshot to the cache area a may include: the periodic snapshot is marked in the cache area A, and after marking, the stored physical address of the periodic snapshot is still unchanged without address 1.
The resource release condition of the cache area a is specifically a second resource release condition, and the second resource release condition may include: and taking the minimum value of the residual survival time of the snapshot and the second preset cache time as the release time of the snapshot.
Thus, the present embodiment may reduce the shelf life of the snapshot marked as cache region a (i.e., the regular snapshot) and reduce the storage cost of the cloud platform as compared to releasing the regular snapshot after the end of the life cycle.
If the physical address of the permanent snapshot is address2, and the storage resource corresponding to the permanent snapshot is released, the step of migrating the permanent snapshot to the cache area B may include: the permanent snapshot is marked in the cache area B, and after marking, the stored physical address of the permanent snapshot is still unchanged without address 2.
For the permanent snapshot marked as the cache area B, if the purpose of the permanent snapshot is only data reduction, the snapshot is a useless snapshot, so that the permanent snapshot can be released, and the storage cost of the cloud platform is reduced; if the use of the permanent snapshot includes other uses in addition to data reduction, indicating that the permanent snapshot is a useful snapshot, the permanent snapshot may be permanently saved. For example, the permanent snapshot is marked as a cache area C, and the first preset cache time of the cache area C is permanent.
The snapshot migration in the embodiment is realized in a labeling mode, so that an administrator can conveniently and quickly confirm the snapshot type of the snapshot according to the identification, the snapshot management is further facilitated, and the consumption of software and hardware resources caused by the migration of the physical storage position is reduced.
Fig. 8 is a schematic structural view of a snapshot management device according to an exemplary embodiment of the present application, as shown in fig. 8, and in an exemplary embodiment, the device includes: a detection module 810, an migration module 820, and a release module 830. The modules referred to in the embodiments of the present application may be a series of computer program instruction segments capable of completing specific functions, or may be functional modules formed by matching computer program instruction segments with hardware, where the modules are divided into a logic function division, and may have another division manner when actually implemented, which is not limited in the present application. Wherein:
The detection module 810 is configured to detect whether a storage resource corresponding to the snapshot is released, and obtain a snapshot corresponding to the released storage resource;
an migration module 820, configured to migrate, after detecting a snapshot corresponding to the released storage resource, the snapshot into a corresponding cache area according to a snapshot type of the snapshot; one cache area corresponds to one snapshot type, and each cache area is provided with a resource release condition;
and a releasing module 830, configured to release the snapshot when the snapshot meets a resource release condition of the corresponding cache area.
In some embodiments, the snapshot types include: periodic snapshots and permanent snapshots;
the migration module 820 specifically is configured to: when the snapshot type of the snapshot is a permanent snapshot, the snapshot is migrated into a first cache area, and a first resource release condition is set in the first cache area and is used for detecting whether the snapshot in the first cache area is released or not;
the migration module 820 specifically is configured to: and when the snapshot type of the snapshot is a regular snapshot, the snapshot is migrated into a second cache area, and the second cache area is provided with a second resource release condition which is used for detecting whether to release the snapshot in the second cache area.
In some embodiments, the first resource release condition comprises: the purpose of the snapshot is only data reduction;
the migration module 820 includes a confirmation unit, a release unit and a migration unit; wherein:
a confirmation unit for determining the purpose of the snapshot;
the releasing unit is used for releasing the snapshot when the purpose of the snapshot is only data reduction;
a migration unit, configured to migrate the snapshot to a third cache area when the uses of the snapshot include uses other than data reduction; the third cache region is provided with a first preset cache time, and the first preset cache time is permanent.
In some embodiments, the detection module 810 is specifically configured to: obtaining each snapshot stored currently, and periodically detecting whether the storage resources corresponding to each snapshot stored currently are released or not, so as to obtain the snapshots corresponding to the released storage resources;
and/or detecting whether there are released storage resources; if the released storage resource exists, detecting whether the released storage resource corresponds to the snapshot in the survival state, and obtaining the snapshot corresponding to the released storage resource.
In some embodiments, the second buffer area is set with a second preset buffer time, and the second resource release condition includes: and under the condition that the second preset caching time is greater than zero, taking the minimum value of the remaining survival time of the snapshot and the second preset caching time as the release time of the snapshot.
In some embodiments, the snapshot is released immediately if the second preset cache time is zero.
In some embodiments, the snapshot management device further comprises a presentation module;
and the display module is used for displaying the snapshots of different snapshot types in different display areas, and one snapshot type corresponds to one display area.
In some embodiments, the snapshot management device further includes a marking module;
the marking module is used for determining a cache area identifier corresponding to the snapshot type according to the snapshot type of the snapshot; and marking the cache area on the snapshot mark.
Specifically, the snapshot management device provided in this embodiment can implement all the method steps implemented by the method embodiment and achieve the same technical effects, and the parts and beneficial effects that are the same as those of the method embodiment in this embodiment are not described in detail herein.
Fig. 9 is a schematic diagram of a hardware structure of an electronic device 900 according to an exemplary embodiment of the present application, and as shown in fig. 9, the electronic device 900 may include a processor 901, a memory 902, and a communication bus 903. The memory 902 is used to store one or more computer programs 904. One or more computer programs 904 are configured to be executed by the processor 901. The one or more computer programs 904 include instructions that can be used to implement the snapshot management methods described above for execution in the electronic device 900.
It is to be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 900. In other embodiments, electronic device 900 may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components.
The processor 901 may include one or more processing units, such as: processor 901 may include an application processor (application processor, AP), a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a DSP, a CPU, a baseband processor, and/or a neural-network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.
A memory may also be provided in processor 901 for storing instructions and data. In some embodiments, the memory in the processor 901 is a cache memory. The memory may hold instructions or data that the processor 901 has just used or recycled. If the processor 901 needs to reuse the instruction or data, it may be called directly from the memory. Repeated accesses are avoided and the latency of the processor 901 is reduced, thereby improving the efficiency of the system.
In some embodiments, processor 901 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a SIM interface, and/or a USB interface, among others.
In some embodiments, memory 902 may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, memory, plug-in hard disk, smart Media Card (SMC), secure Digital (SD) Card, flash Card (Flash Card), at least one disk storage device, flash memory device, or other volatile solid state storage device.
The present embodiment also provides a storage medium, which may be a non-transitory computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the snapshot management method in the above embodiment.
The embodiment also provides a chip which is electrically connected with the electronic equipment and used for controlling the electronic equipment to execute the related method steps to realize the snapshot management method in the embodiment.
The present embodiment also provides a computer program product which, when run on a computer, causes the computer to perform the above-described related steps to implement the snapshot management method in the above-described embodiments.
The electronic device, the storage medium, the computer program product, or the chip provided in this embodiment are used to execute the corresponding methods provided above, so that the beneficial effects thereof can be referred to the beneficial effects of the corresponding methods provided above, and will not be described herein.
From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated unit may be stored in a readable storage medium if implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of specific embodiments of the present application, and the scope of the present application is not limited thereto, but any changes or substitutions within the technical scope of the present application should be covered by the scope of the present application.
Claims (10)
1. A snapshot management method, comprising:
detecting whether the storage resource corresponding to the snapshot is released or not, and obtaining the snapshot corresponding to the released storage resource;
after the snapshot corresponding to the released storage resource is detected, the snapshot is migrated into a corresponding cache area according to the snapshot type of the snapshot; one cache area corresponds to one snapshot type, and each cache area is provided with a resource release condition;
and releasing the snapshot when the snapshot meets the resource release condition of the corresponding cache region.
2. The snapshot management method according to claim 1, wherein the snapshot type includes: periodic snapshots and permanent snapshots;
and according to the snapshot type of the snapshot, migrating the snapshot into a corresponding cache area, including:
when the snapshot type of the snapshot is a permanent snapshot, the snapshot is migrated into a first cache area, and a first resource release condition is set in the first cache area and is used for detecting whether the snapshot in the first cache area is released or not;
And when the snapshot type of the snapshot is a regular snapshot, the snapshot is migrated into a second cache area, and the second cache area is provided with a second resource release condition which is used for detecting whether to release the snapshot in the second cache area.
3. The snapshot management method according to claim 2, wherein the first resource release condition includes: the purpose of the snapshot is only data reduction;
after the snapshot is migrated into the first cache area, the method further includes:
determining a purpose of the snapshot;
releasing the snapshot when the use of the snapshot is only data reduction;
migrating the snapshot to a third cache region when the use of the snapshot includes other uses than data reduction; the third cache region is provided with a first preset cache time, and the first preset cache time is permanent.
4. The snapshot management method according to claim 3, wherein the detecting whether the storage resource corresponding to the snapshot is released, and obtaining the snapshot corresponding to the released storage resource, includes:
obtaining each currently stored snapshot, and periodically detecting whether storage resources corresponding to each currently stored snapshot are released or not to obtain the snapshot corresponding to the released storage resources; and/or the number of the groups of groups,
Detecting whether the released storage resource exists or not; if the released storage resource exists, detecting whether the released storage resource corresponds to the snapshot in the survival state, and obtaining the snapshot corresponding to the released storage resource.
5. The snapshot management method according to claim 2, wherein the second buffer area is provided with a second preset buffer time, and the second resource release condition includes:
and under the condition that the second preset caching time is greater than zero, taking the minimum value of the remaining survival time of the snapshot and the second preset caching time as the release time of the snapshot.
6. The snapshot management method according to claim 5, wherein the second resource release condition further comprises:
and under the condition that the second preset caching time is zero, immediately releasing the snapshot.
7. The snapshot management method according to claim 1, wherein the method further comprises:
and displaying the snapshots of different snapshot types in different display areas, wherein one snapshot type corresponds to one display area.
8. The snapshot management method according to claim 1, wherein the migration of the snapshot into the corresponding cache region according to the snapshot type of the snapshot includes:
Determining a cache region identifier corresponding to the snapshot type according to the snapshot type of the snapshot;
and marking the cache area on the snapshot mark.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the snapshot management method of any of claims 1-8 when the computer program is executed by the processor.
10. A storage medium having stored thereon a computer program which, when executed by a processor, implements the snapshot management method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311057814.4A CN116756091A (en) | 2023-08-22 | 2023-08-22 | Snapshot management method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311057814.4A CN116756091A (en) | 2023-08-22 | 2023-08-22 | Snapshot management method, electronic device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116756091A true CN116756091A (en) | 2023-09-15 |
Family
ID=87955595
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311057814.4A Pending CN116756091A (en) | 2023-08-22 | 2023-08-22 | Snapshot management method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116756091A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110688056A (en) * | 2018-07-05 | 2020-01-14 | 北京忆恒创源科技有限公司 | Storage medium replacement for NVM groups |
| CN110895513A (en) * | 2018-09-12 | 2020-03-20 | 华为技术有限公司 | System garbage recycling method and garbage recycling method in solid state disk |
| CN111124745A (en) * | 2018-10-30 | 2020-05-08 | 伊姆西Ip控股有限责任公司 | Method, apparatus, and computer-readable storage medium for managing storage system |
| CN111198856A (en) * | 2019-12-31 | 2020-05-26 | 北京旷视科技有限公司 | File management method and device, computer equipment and storage medium |
| CN111736961A (en) * | 2020-08-18 | 2020-10-02 | 鹏城实验室 | Virtual machine release method and device, storage medium and electronic equipment |
| CN112181590A (en) * | 2020-09-25 | 2021-01-05 | 烽火通信科技股份有限公司 | Method, device and equipment for deleting resources in cloud platform and readable storage medium |
| CN115981574A (en) * | 2023-03-10 | 2023-04-18 | 阿里巴巴（中国）有限公司 | Snapshot storage method, system, equipment and storage medium |
-
2023
- 2023-08-22 CN CN202311057814.4A patent/CN116756091A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110688056A (en) * | 2018-07-05 | 2020-01-14 | 北京忆恒创源科技有限公司 | Storage medium replacement for NVM groups |
| CN110895513A (en) * | 2018-09-12 | 2020-03-20 | 华为技术有限公司 | System garbage recycling method and garbage recycling method in solid state disk |
| CN111124745A (en) * | 2018-10-30 | 2020-05-08 | 伊姆西Ip控股有限责任公司 | Method, apparatus, and computer-readable storage medium for managing storage system |
| CN111198856A (en) * | 2019-12-31 | 2020-05-26 | 北京旷视科技有限公司 | File management method and device, computer equipment and storage medium |
| CN111736961A (en) * | 2020-08-18 | 2020-10-02 | 鹏城实验室 | Virtual machine release method and device, storage medium and electronic equipment |
| CN112181590A (en) * | 2020-09-25 | 2021-01-05 | 烽火通信科技股份有限公司 | Method, device and equipment for deleting resources in cloud platform and readable storage medium |
| CN115981574A (en) * | 2023-03-10 | 2023-04-18 | 阿里巴巴（中国）有限公司 | Snapshot storage method, system, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10817386B2 (en) | Virtual machine recovery method and virtual machine management device | |
| CN102594849B (en) | Data backup and recovery method and device, virtual machine snapshot deleting and rollback method and device | |
| US9830327B2 (en) | Method, device, node and system for managing file in distributed data warehouse | |
| US11615000B2 (en) | Method and backup server for processing expired backups | |
| CN110753084B (en) | Uplink data reading method, cache server and computer readable storage medium | |
| US10846301B1 (en) | Container reclamation using probabilistic data structures | |
| CN110019063B (en) | Method for computing node data disaster recovery playback, terminal device and storage medium | |
| RU2665272C1 (en) | Method and apparatus for restoring deduplicated data | |
| US9104447B2 (en) | Restoring a previous version of a virtual machine image | |
| CN109542841B (en) | Method for creating data snapshot in cluster and terminal equipment | |
| CN112463059B (en) | Write data processing method and device, electronic equipment and storage medium | |
| CN113641446A (en) | Memory snapshot creating method, device and equipment and readable storage medium | |
| CN116756091A (en) | Snapshot management method, electronic device and storage medium | |
| CN109522373B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN112988247B (en) | Log processing method and device, electronic equipment and readable storage medium | |
| CN115373882A (en) | Storage system fault recovery method, system, computer equipment and storage medium | |
| CN115640280A (en) | Data migration method and device | |
| CN110704249A (en) | Method, device and system for ensuring application consistency | |
| CN114675776A (en) | Resource storage method and device, storage medium and electronic equipment | |
| CN112463741A (en) | Cleaning method for aggregated large files and related equipment | |
| US20150163110A1 (en) | Registration Reconciliation Influenced by Expired Registration Records | |
| CN110658989B (en) | System and method for backup storage garbage collection | |
| CN112015586B (en) | Data reconstruction calculation method and related device | |
| CN109933566B (en) | File reading and writing method, device, equipment and computer readable storage medium | |
| CN116361388A (en) | Data processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230915 |
|
| RJ01 | Rejection of invention patent application after publication |