CN107943557B - Virtual machine disk incremental snapshot method based on cloud platform - Google Patents
Virtual machine disk incremental snapshot method based on cloud platform Download PDFInfo
- Publication number
- CN107943557B CN107943557B CN201711150779.5A CN201711150779A CN107943557B CN 107943557 B CN107943557 B CN 107943557B CN 201711150779 A CN201711150779 A CN 201711150779A CN 107943557 B CN107943557 B CN 107943557B
- Authority
- CN
- China
- Prior art keywords
- snapshot
- virtual machine
- disk
- base
- file
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
Abstract
The invention discloses a virtual machine disk incremental snapshot method based on a cloud platform, which comprises the following three parts: making an incremental snapshot, managing storage of the incremental snapshot and creating a virtual machine by using the snapshot; in the making process of the incremental snapshot, the base increment is directly uploaded to the gland service without the merging process of the base and disk when the snapshot is uploaded; in the liance service, the snapshot of the virtual machine is stored and managed in a tree logic structure; when a virtual machine is selected to be created from a snapshot, a convert operation is executed on the incremental snapshot, and the whole incremental snapshot chain is traced back forward and a complete snapshot file is merged. The invention does not carry out the step of merging when the virtual machine is snapshot every time, and only extracts the latest incremental data as the snapshot to upload. Time cost is saved from two stages of merging data and uploading data, and snapshot efficiency is improved; the snapshot is stored in the form of an incremental file on the work service, so that the space occupation is greatly saved, and the redundant data is reduced.
Description
Technical Field
The invention relates to the field of cloud computing, in particular to optimization of making, storing and using of disk snapshots of a virtual machine in an openstack project.
Background
The openstack cloud platform is provided with a snapshot function on the management of the virtual machine, wherein the snapshot is used for storing the system state of the virtual machine at a certain moment and can be restored to the state point later.
For the openstack project, the disk image of the virtual machine is stored on the computing node in the qcow2 file format. The disk image of the virtual machine is supported to be overlapped and actually composed in a base + disk form. The disk file is stored in a folder named by the UUID of the virtual machine in a qcow2 format, the backing file is a base mirror image in a raw format and is stored in a _ base folder at the same level as the folder of the virtual machine, and the disk only stores the modification of the base. A snapshot management service (pane) runs on the control node. The process of making the snapshot is to merge the disk and the base of the virtual machine and upload the merged disk and base to the gland service. On one hand, a certain time is consumed in the merging process, and a certain time is consumed when the merged file is transmitted to the company through the network; on the other hand, the snapshot after merging repeatedly contains the base image content that the work has saved, and there is a waste of space.
Disclosure of Invention
The invention aims to solve the problems of time consumption and space occupation of a disk full snapshot scheme in an openstack project, provides a disk incremental snapshot method which is faster in time and more efficient in space, and remarkably reduces the time and space consumption of disk snapshot operation by only making, transmitting and storing disk snapshots in an incremental form.
The purpose of the invention is realized by the following technical scheme: a virtual machine disk incremental snapshot method based on a cloud platform comprises three parts: making an incremental snapshot, managing storage of the incremental snapshot and creating a virtual machine by using the snapshot;
(1) making incremental snapshots
The core idea of the part is that when the snapshot is uploaded, the base increment (new modified part) is directly uploaded to the work service without the merging process of the base and disk; in order to save modified data between two snapshots, a disk increment of the virtual machine is divided into two parts, namely disk _ base and disk, wherein the disk _ base is used for saving all modifications to the base of the virtual machine before the latest snapshot, and the disk saves modifications to the base of the virtual machine after the latest snapshot; therefore, the mirror image of the virtual machine is always kept in the three-layer superposition;
when a snapshot is made for a certain virtual machine for the first time and the snapshot is made for the nth (n >1) time, the changes of base, disk _ base and disk are different;
when a snapshot is made for the first time, the disk file of the virtual machine only contains disk, the backing file of the disk file is base, and the modification of the base since the virtual machine is created is saved; uploading a disk file serving as snapshot data to a glance service, renaming the disk file to be disk _ base, creating a blank incremental file disk in a qcow2 format by taking the disk _ base as a backing file, wherein at the moment, a mirror image file of a virtual machine is changed into a three-layer structure, sequentially from top to bottom, namely disk → disk _ base → base, and then storing the latest modification of the base into the disk file at the top layer;
when the snapshot is made at the nth (n >1) time, the disk increment of the virtual machine comprises disk _ base and disk, wherein the backing file of the disk _ base is base, the backing file of the disk is disk _ base, and the disk is the latest modification to the base; uploading a disk file serving as snapshot data to a gland service, submitting commit to disk _ base by using a qemu-img tool, completely storing all modifications to a base of a virtual machine, deleting the disk, newly building a blank incremental file disk by using the base of the disk _ base as a backing file, restoring a three-layer structure disk → disk _ base → base by using a mirror image file of the virtual machine, and storing the latest modifications to the base into a top-layer disk file;
(2) storage management of incremental snapshots
The core idea of the part is that in the liance service, the snapshot of the virtual machine is stored and managed in a tree logic structure, which is called a snapshot relation tree; meanwhile, a latest snapshot registration table of the virtual machine is added in the database, or a latest snapshot id field latest _ snap _ id is added in the instance table, and the latest snapshot id field is used for registering the id of the latest snapshot of a certain virtual machine (namely the file name of the snapshot on the gland service); simultaneously, adding an incremental dependency information table in a database, or adding a child _ snap _ id field in an image table, wherein the child _ snap _ id field is used for registering an incremental file taking a certain mirror image as a backing file; for the establishment of a snapshot relation tree and the deletion operation of a snapshot node, a latest snapshot registry and an increment dependence information table of a virtual machine are required for auxiliary completion;
when the virtual machine A completes the creation from a certain mirror image base, updating a latest _ snap _ id field of the virtual machine A in a latest snapshot registry of the virtual machine to be the id (namely the file name) of the mirror image base;
after a first snapshot increment snap A-1 of a virtual machine A is uploaded to a gloss service, a qemu-img tool is used for enabling the snap A-1 increment rebase to be on a mirror image base (a file name is obtained by inquiring according to a latest snapshot registry of the virtual machine), a latest _ snap _ id field of the virtual machine A in the latest snapshot registry of the virtual machine is updated to be id of the snap A-1, and the like, after a snapshot made by the virtual machine A is uploaded to the gloss service, rebase is carried out according to a last snapshot id recorded in the latest snapshot registry of the virtual machine, registry of the virtual machine A is updated, registry information is updated, and therefore all snapshots of the virtual machine A are guaranteed to form a linked list structure logically, and a linked list head is a base;
the incremental snapshots of the virtual machines form a snapshot relation tree; the snapshot relationship tree describes a strong dependency relationship between the incremental snapshots, so that when a snapshot is deleted, other incremental snapshots that depend on it will fail; to address this situation, the present invention proposes a snapshot deletion policy: when the snapshot snap A-j is required to be deleted, a subtree taking the snap A-j as a root node is calculated according to an increment dependence information table, then whether the tail end of the subtree is provided with an active virtual machine or not is checked, and if not, the snapshot in the subtree is prompted to be deleted together; if the tail end has active virtual machines, deleting the snapshot is forbidden, or prompting the user that the active virtual machines are also deleted, deleting the tail end virtual machine after the user agrees to delete, and prompting the user that the snapshots in the subtree are deleted together;
(3) creating virtual machines using snapshots
The core task of the part is to merge the incremental snapshot chains to obtain an effective snapshot mirror image, and then download the effective snapshot mirror image to the computing node for creating the virtual machine. When a virtual machine is selected to be created from a snapshot snap A-k, firstly, a qemu-img tool is used for executing a convert operation on the incremental snapshot, and the convert operation can trace back the whole incremental snapshot chain forward and combine the incremental snapshot chain and the complete snapshot file; the full snapshot file is downloaded to the compute node and used as base to create a new virtual machine.
Further, the method also comprises the following optional parts: full snapshot caching
The same snapshot is used for creating the virtual machine, the same merging process is repeated for the corresponding incremental snapshots, the total snapshots obtained through merging can be cached in a place service, when the same snapshot is requested next time, whether the corresponding total snapshots exist or not is searched in the cache, if the corresponding total snapshots exist, the corresponding total snapshots are directly downloaded for use, otherwise, the conventional merging process is carried out and the cache is added, and therefore time consumption generated in the merging process can be reduced to a great extent.
The innovation points and advantages of the invention are as follows:
1. the step of merging is not carried out when the virtual machine is snapshot every time, and only the latest incremental data is extracted to be uploaded as the snapshot. Time cost is saved from two stages of merging data and uploading data, and snapshot efficiency is improved;
2. the snapshot is stored in the form of an incremental file on the work service, so that the space occupation is greatly saved, and the redundant data is reduced.
Drawings
FIG. 1 illustrates a process for making a first snapshot of a virtual machine;
FIG. 2 shows a process for making an n (n >1) th snapshot of a virtual machine;
FIG. 3 shows the change of the snapshot relation tree and the database correlation table in the work service after making a snapshot for a native system virtual machine (created from the native system image);
FIG. 4 is a diagram showing the change of the snapshot relation tree and the database correlation table in the work service after a snapshot is made to a snapshot virtual machine (created from a snapshot mirror);
FIG. 5 illustrates a case where a snapshot without virtual machine dependencies is deleted;
FIG. 6 illustrates the deletion of a snapshot that has virtual machine dependencies;
specifically, the following description is provided: for fig. 3, fig. 4, the dashed arrows indicate that there are several incremental snapshots in the middle. For fig. 5, fig. 6, the dotted line indicates that there is virtual machine dependency at the end.
Detailed Description
The invention is described in further detail below with reference to the figures and specific examples.
1. Making incremental snapshots
The virtual machine is created from a base mirror image, the disk file of the initial virtual machine only contains disk, the backing file of the initial virtual machine is base, modification of the base since the virtual machine is created is saved, the virtual machine mirror image file is of a two-layer structure, and the disk → the base are sequentially arranged from top to bottom.
The flow of making a snapshot of a virtual machine for the first time is shown in fig. 1:
step 1.1, uploading disk files serving as snapshot data to a gloss service;
step 1.2, renaming the disk file as disk _ base;
step 1.3, creating a blank incremental file disk in a qcow2 format by taking disk _ base as backing file;
at this time, the image file of the virtual machine is changed into a three-layer structure, namely disk → disk _ base → base from top to bottom, and then the modification of the base is saved in the disk file at the top layer.
The flow of making a snapshot for the n (n >1) th time of a certain virtual machine is shown in fig. 2:
step 2.1, uploading the disk file serving as snapshot data to a gloss service;
step 2.2, sending the disk data commit to disk _ base;
at this time, all modifications to the base of the virtual machine are completely saved in disk _ base;
step 2.3, deleting disk;
step 2.4, newly building a blank incremental file disk by taking disk _ base as a backing file;
at this point, the virtual machine image file restores the three-tier structure disk → disk _ base → base, after which the latest modifications to base will be saved to the top-level disk file.
2. Storage management of incremental snapshots
2.1 creation of Snapshot Tree
As shown in FIG. 3, when the creation of virtual machine A from a certain mirror base is completed, the latest _ snap _ id field of virtual machine A in the latest snapshot registry of the updated virtual machine is the id of the mirror base.
After the virtual machine A uploads the first snapshot snapA-1, the operation of the gland service on the incremental snapshot management needs to be performed as follows:
and 3.1, executing base operation on the increment snap A-1 uploaded to the gland service, wherein the backing file attribute is set according to the latest _ snap _ id field of the virtual machine A in the latest snapshot registry of the virtual machine, namely the id of the base.
And 3.2, updating the latest _ snap _ id field of the virtual machine A in the latest snapshot registry of the virtual machine into the id of snap A-1.
And 3.3, updating an increment dependence information table, and adding the id of snap A-1 to the child _ snap _ id field of the base.
When the virtual machine A uploads the nth (n >1) snapshot snapA-n, a latest _ snapshot _ id field of the virtual machine A in the latest snapshot registry of the virtual machine is the id of the incremental snapshot snapA- (n-1) at the n-1 th time, and the operation of a company service after uploading the snapshot snapA-n, which is required for managing the incremental snapshot, is as follows:
and 3.4, executing base operation on the increment snap A-n uploaded to the gland service, wherein the backing file attribute is set according to the latest _ snap _ id field of the virtual machine A in the latest snapshot registry of the virtual machine, namely the id of snap A- (n-1).
And 3.5, updating the latest _ snap _ id field of the virtual machine A in the latest snapshot registry of the virtual machine into the id of the snap A-n.
And 3.6, updating an increment dependence information table, and adding the id of the snap A-n to the child _ snap _ id field of the snap A- (n-1).
As shown in FIG. 4, when virtual machine C completes creation from snapshot mirror Snap A-i, virtual machine C's latest _ snap _ id field in the virtual machine's latest snapshot registry is populated with the id (i.e., file name) of Snap A-i.
After the virtual machine C uploads the first snapshot snapsn-1, the operation of the company service on the management of the incremental snapshot is as follows:
and 4.1, executing base operation on the increment snap C-1 uploaded to the gland service, wherein the backing file attribute is set according to the latest _ snap _ id field of the virtual machine C in the latest snapshot registry of the virtual machine, namely the id of snap A-i.
And 4.2, updating the latest _ snap _ id field of the virtual machine C in the latest snapshot registry of the virtual machine into the id of snap C-1.
And 4.3, updating an increment dependence information table, and adding snap-1 to a child _ snap _ id field of snap A-i.
When the virtual machine C uploads the kth (k >1) snapshot snapC-k, a latest _ snapshot _ id field of the virtual machine C in the latest snapshot registry of the virtual machine is the id of the (k-1) th incremental snapshot snapC- (k-1), and the operation of a company service after uploading the snapshot snapC-k, which is required for managing the incremental snapshots, is as follows:
and 4.4, executing base operation on the snap C-k, wherein the backing file attribute is set according to the latest _ snap _ id field of the virtual machine C in the latest snapshot registry of the virtual machine, namely the id of the snap C- (k-1).
And 4.5, updating the latest _ snap _ id field of the virtual machine C in the latest snapshot registry of the virtual machine into the id of the snap C-k.
And 4.6, updating an increment dependence information table, and adding snap-k to a child _ snap _ id field of snap- (k-1).
2.2 deletion of snapshots
Fig. 5 shows a small snapshot relationship tree in which virtual machines a and B are created from mirror base, and virtual machine a is deleted for some reason after 3 snapshots have been created, and virtual machine B is also deleted after 4 snapshots have been created. The virtual machine C is created from the snapshot snap A-2, 2 snapshots are generated, the C still keeps active, the virtual machine D is created from the snapshot snap B-3, the virtual machine D is deleted after one snapshot is generated, the virtual machine E is created from the snapshot snap C-1, the snapshots are not generated, and the E still keeps active.
The first case is shown in fig. 5, and at this time, to delete snapshot snapB-2, the following operations need to be performed:
and setting the snapshot set to be deleted as S and setting the snapshot set to be deleted as { snap B-2} initially.
And calculating the snap B-2 subtree according to the increment dependence information table, firstly adding the snap B-3 of the child node of the snap B-2 into S, and then adding the snap B-4 and the snap D-1 of the child node of the snap B-3 into S to obtain an S set { snap B-2, snap B-3, snap B-4 and snap D-1 }.
It is checked whether an image in set S created a virtual machine that is still valid (i.e., not deleted) and that such an image does not exist in S.
At this point the user is prompted that all snapshots in set S will be deleted.
The second case is shown in fig. 6, where to delete snapshot snapA-2, the following operations are required:
and setting the snapshot set to be deleted as S and setting the snapshot set to be deleted as { snap A-2} initially.
The snap A-2 subtree is calculated according to the increment dependence information table, firstly, the child nodes snap A-3 and snap C-1 of snap A-2 are added into S, then the child nodes snap C-2 of snap C-1 are added into S, and the S set { snap A-2, snap A-3, snap C-1 and snap C-2} is obtained.
Checking whether any image in the set S creates a virtual machine and the virtual machine is still valid (i.e. not deleted), and checking results in that snap A-2 is used to create a virtual machine C, snap C-1 is used to create a virtual machine E, and C and E are still in a valid state.
And prompting a user to delete the virtual machines C and E first and then converting the virtual machines C and E into the first condition, wherein the subsequent corresponding steps are not repeated.
Optional scheme: prompting that the deletion of the snap A-2 snapshot is illegal and prohibiting the execution of the operation.
3. Creating virtual machines using snapshots
The use of incremental snapshots includes two steps:
and 2, downloading the full snapshot file to the computing node for creating the virtual machine.
Optional functions: setting a full snapshot cache
Because the convert process needs a certain time overhead, in order to avoid repeating the same convert process before using the same snapshot for many times, the used total snapshots are cached recently, and the system efficiency can be effectively improved. The snapshot use flow after the cache is introduced is as follows:
And 2, performing convert operation on the incremental file by using a qemu-img tool to obtain a full file.
And 3, putting the combined full file into a cache, and downloading the file to create the virtual machine.
And periodically performing cache cleaning.
The present invention is not limited to the above-described embodiments, and those skilled in the art can implement the present invention in other various embodiments based on the disclosure of the present invention. Therefore, the design of the invention is within the scope of protection, with simple changes or modifications, based on the design structure and thought of the invention.
Claims (1)
1. A virtual machine disk incremental snapshot method based on a cloud platform is characterized by comprising the following three parts: making an incremental snapshot, managing storage of the incremental snapshot and creating a virtual machine by using the snapshot;
(1) making incremental snapshots
When the snapshot is uploaded, the increment of the base is directly uploaded to the gland service without the merging process of the base and disk; dividing the disk increment of the virtual machine into two parts, namely disk _ base and disk, wherein the disk _ base is used for storing all modifications to the base of the virtual machine before the latest snapshot, and the disk stores the modifications to the base of the virtual machine after the latest snapshot; the mirror image of the virtual machine is always kept in the three-layer superposition;
when a snapshot is made for the first time, the disk file of the virtual machine only contains disk, the backing file of the disk file is base, and the modification of the base since the virtual machine is created is saved; uploading a disk file serving as snapshot data to a glance service, renaming the disk file to be disk _ base, creating a blank incremental file disk in a qcow2 format by taking the disk _ base as a backing file, wherein at the moment, a mirror image file of a virtual machine is changed into a three-layer structure, sequentially from top to bottom, namely disk → disk _ base → base, and then storing the latest modification of the base into the disk file at the top layer;
when the snapshot is made at the nth (n >1) time, the disk increment of the virtual machine comprises disk _ base and disk, wherein the backing file of the disk _ base is base, the backing file of the disk is disk _ base, and the disk is the latest modification to the base; uploading a disk file serving as snapshot data to a gland service, using a qemu-img tool to commit the disk data to a disk _ base, completely storing all modifications to the virtual machine base in the disk _ base at the moment, deleting the disk, using the disk _ base as a backing file to newly create a blank incremental file disk, recovering a three-layer structure disk → disk _ base → base by the virtual machine mirror image file, and then storing the latest modifications to the base in a top-layer disk file;
(2) storage management of incremental snapshots
In the liance service, the snapshots of the virtual machine are stored and managed in a tree logic structure, which is called a snapshot relation tree; simultaneously, adding a latest snapshot register table of the virtual machine in the database, or adding a latest snapshot id field latest _ snap _ id in the instance table, wherein the latest snapshot id field is used for registering the id of the latest snapshot of a certain virtual machine, namely the file name of the snapshot on the gland service; simultaneously, adding an incremental dependency information table in a database, or adding a child _ snap _ id field in an image table, wherein the child _ snap _ id field is used for registering an incremental file taking a certain mirror image as a backing file;
when the virtual machine A is completely established from a certain mirror image base, updating a latest _ snap _ id field of the virtual machine A in a latest snapshot registry of the virtual machine A to be the id of the mirror image base;
after a first snapshot increment snap A-1 of a virtual machine A is uploaded to a gloss service, a qemu-img tool is used for enabling snap A-1 increment rebase to be on a mirror image base, a latest _ snap _ id field of the virtual machine A in a latest snapshot registry of the virtual machine A is updated to be id of the snap A-1, a snapshot made each time by the virtual machine A is uploaded to the gloss service, rebase is carried out according to a last snapshot id recorded by the latest snapshot registry of the virtual machine A, registry information is updated, it is guaranteed that all incremental snapshots of the virtual machine A logically form a linked list structure, and a link list head is a base;
the incremental snapshots of the virtual machines form a snapshot relation tree; when the snapshot snap A-j is required to be deleted, a subtree taking the snap A-j as a root node is calculated according to an increment dependence information table, then whether the tail end of the subtree is provided with an active virtual machine or not is checked, and if not, the snapshot in the subtree is prompted to be deleted together; if the tail end has active virtual machines, deleting the snapshot is forbidden, or prompting the user that the active virtual machines are also deleted, deleting the tail end virtual machine after the user agrees to delete, and prompting the user that the snapshots in the subtree are deleted together;
(3) creating virtual machines using snapshots
When a virtual machine is selected to be created from a snapshot snap A-k, firstly, a qemu-img tool is used for executing a convert operation on the incremental snapshot, and the convert operation can trace back the whole incremental snapshot chain forward and combine the incremental snapshot chain and the complete snapshot file; the complete snapshot file is downloaded to a computing node and used as base for creating a new virtual machine;
the virtual machine disk incremental snapshot method further comprises a full snapshot cache, and specifically comprises the following steps: the same snapshot is used for creating a virtual machine, the same merging process is repeated for the corresponding incremental snapshots, the total snapshots obtained through merging are selected to be cached in a global service, when the same snapshot is requested next time, whether the corresponding total snapshots exist or not is searched in the cache, if yes, the corresponding total snapshots are directly downloaded for use, otherwise, the conventional merging process is carried out and the cache is added, and therefore time consumption generated in the merging process is reduced to a great extent.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711150779.5A CN107943557B (en) | 2017-11-18 | 2017-11-18 | Virtual machine disk incremental snapshot method based on cloud platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711150779.5A CN107943557B (en) | 2017-11-18 | 2017-11-18 | Virtual machine disk incremental snapshot method based on cloud platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107943557A CN107943557A (en) | 2018-04-20 |
| CN107943557B true CN107943557B (en) | 2020-07-17 |
Family
ID=61933019
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711150779.5A Active CN107943557B (en) | 2017-11-18 | 2017-11-18 | Virtual machine disk incremental snapshot method based on cloud platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107943557B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109033430A (en) * | 2018-08-13 | 2018-12-18 | 郑州云海信息技术有限公司 | A kind of virtual machine image file storage method and device |
| CN109062672A (en) * | 2018-08-21 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of method, apparatus and storage medium handling disk tree node |
| CN109164988A (en) * | 2018-08-30 | 2019-01-08 | 上海交通大学 | Processor-based virtual machine snapshot method and system |
| CN109324929B (en) * | 2018-09-17 | 2021-11-09 | 郑州云海信息技术有限公司 | Snapshot creating method, device and equipment and readable storage medium |
| CN109358947B (en) * | 2018-10-08 | 2023-01-10 | 郑州云海信息技术有限公司 | Method and system for realizing virtual machine snapshot |
| CN109542588B (en) * | 2018-11-27 | 2021-02-05 | 苏州浪潮智能科技有限公司 | Method and device for managing virtual equipment in cloud environment |
| CN109614055B (en) * | 2018-12-21 | 2022-11-04 | 杭州宏杉科技股份有限公司 | Snapshot creating method and device, electronic equipment and machine-readable storage medium |
| CN110633129A (en) * | 2019-08-23 | 2019-12-31 | 北京浪潮数据技术有限公司 | Continuous data protection method, device and equipment for virtualization platform |
| CN110688259B (en) * | 2019-09-26 | 2024-02-06 | 上海仪电（集团）有限公司中央研究院 | Private cloud backup recovery system and backup recovery method thereof |
| CN112596748B (en) * | 2020-12-28 | 2023-05-16 | 武汉噢易云计算股份有限公司 | Desktop fusion use method, device, equipment and readable storage medium |
| CN112783832B (en) * | 2020-12-30 | 2024-03-22 | 上海鲲鲸云股份有限公司 | Method and device for storing snapshot file |
| CN112860376B (en) * | 2021-02-04 | 2023-08-01 | 北京百度网讯科技有限公司 | Snapshot chain manufacturing method and device, electronic equipment and storage medium |
| CN117130980B (en) * | 2023-10-24 | 2024-02-27 | 杭州优云科技有限公司 | Virtual machine snapshot management method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2006262045B2 (en) * | 2005-06-24 | 2011-11-03 | Catalogic Software, Inc. | System and method for high performance enterprise data protection |
| CN104375877A (en) * | 2014-10-15 | 2015-02-25 | 国云科技股份有限公司 | Virtual machine online snapshot generating and deleting method |
| CN105335253B (en) * | 2015-10-28 | 2019-01-15 | 北京百度网讯科技有限公司 | The method and apparatus for creating virtual machine system disk snapshot |
| CN105260229A (en) * | 2015-10-28 | 2016-01-20 | 北京百度网讯科技有限公司 | Method and device for pulling mirror image files of virtual machines |
| CN107197022B (en) * | 2017-06-02 | 2020-01-10 | 华南理工大学 | OpenStack storage optimization method and system |
-
2017
- 2017-11-18 CN CN201711150779.5A patent/CN107943557B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107943557A (en) | 2018-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107943557B (en) | Virtual machine disk incremental snapshot method based on cloud platform | |
| US20220188003A1 (en) | Distributed Storage Method and Device | |
| CN110447021B (en) | Method, apparatus and system for maintaining consistency of metadata and data between data centers | |
| US10664362B2 (en) | Recovery processing for database in persistent system | |
| US9558078B2 (en) | Point in time database restore from storage snapshots | |
| US7680846B2 (en) | File management program, file management apparatus and file management method | |
| US11321192B2 (en) | Restoration of specified content from an archive | |
| CN104090889B (en) | Data processing method and system | |
| CN100407206C (en) | Method and system for transformation between different version configuration data | |
| US20120079502A1 (en) | Dependency-ordered resource synchronization | |
| US10055299B2 (en) | Clone file backup and restore | |
| US20170063990A1 (en) | Structural Data Transfer over a Network | |
| US11249899B2 (en) | Filesystem management for cloud object storage | |
| US11500817B2 (en) | Asynchronous deletion of large directories | |
| CN104360842B (en) | A kind of service dynamic flow method of combination based on JBPM | |
| CN109542875B (en) | Configuration file generation method and device | |
| CN112287007A (en) | Industrial production data real-time processing method and system based on Flink SQL engine | |
| CN104023061A (en) | High availability cluster scheme of OSS (Open Storage service) for LUSTRE | |
| CN107209707B (en) | Cloud-based staging system preservation | |
| CN116490855A (en) | Efficient backup after restore operations | |
| US20130041868A1 (en) | Data synchronization | |
| CN115525221A (en) | Data updating method, device, equipment and medium | |
| US20210326252A1 (en) | In-array linked list identifier pool scheme | |
| JP5815975B2 (en) | Database apparatus and database reorganization method | |
| CN109683820B (en) | Linux-based storage device tree implementation method |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |