CN114518936A - Virtual machine incremental backup method, system, device and storage medium - Google Patents
Virtual machine incremental backup method, system, device and storage medium Download PDFInfo
- Publication number
- CN114518936A CN114518936A CN202210098091.1A CN202210098091A CN114518936A CN 114518936 A CN114518936 A CN 114518936A CN 202210098091 A CN202210098091 A CN 202210098091A CN 114518936 A CN114518936 A CN 114518936A
- Authority
- CN
- China
- Prior art keywords
- virtual
- virtual machine
- virtual disk
- sub
- disk
- 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
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000009225 cognitive behavioral therapy Methods 0.000 description 25
- 230000006870 function Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 241000700605 Viruses Species 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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
- 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
-
- 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/4557—Distribution of virtual machine instances; Migration and load balancing
Abstract
The invention discloses a virtual machine incremental backup method, a system, a device and a storage medium. The virtual machine incremental backup method comprises the following steps: confirming that the number of times of incremental backup of the virtual machine is the first time, and listing virtual disks; generating a first sub-virtual disk; redirecting the data updating operation of the virtual machine from the virtual disk to the first sub virtual disk, and setting the virtual disk to be in a read-only state; backing up a virtual disk; confirming that the number of times of incremental backup of the virtual machine is not the first time, and generating a second sub virtual disk; redirecting the data updating operation of the virtual machine from the third sub virtual disk to the second sub virtual disk, and setting the third sub virtual disk to be in a read-only state; backing up a third sub virtual disk; and merging the third sub virtual disk to the virtual disk, and deleting the third sub virtual disk. The invention realizes the incremental backup of the virtual machine under the condition of not installing the CBT, improves the performance of the virtual machine and reduces the execution complexity and the cost of the incremental backup of the virtual machine.
Description
Technical Field
The present application relates to the field of virtual machine technologies, and in particular, to a method, a system, an apparatus, and a storage medium for incremental backup of a virtual machine.
Background
Hyper-V is virtual machine management software released by Microsoft, and a virtual machine can be created on a Windows system through Hyper-V. Key business data of enterprise users are usually stored in the Hyper-V virtual machine. In order to avoid data loss stored in the Hyper-V virtual machine caused by misoperation, system failure, natural disasters, computer viruses and the like, a user needs to regularly back up the Hyper-V virtual machine. Incremental backups are in place in order to reduce the amount of data that needs to be backed up each time a user backs up a Hyper-V virtual machine. Incremental backups only backup data blocks that have changed since the last backup. When a user performs incremental backup on a Hyper-V virtual machine, a Windows block modification tracking (CBT) driver developed by a manufacturer of backup software needs to be installed on a Hyper-V host. When the data of the virtual machine is changed, the CBT intervenes in real time, intercepts and captures the data blocks for recording the change and backups the data blocks. And the quick acquisition and backup of all changed data blocks are realized. After the backup is completed, the CBT clears the recorded data blocks and re-records the changed data blocks until the next backup.
However, the current use of CBTs for incremental backup of Hyper-V virtual machines has the following problems:
1. manufacturers need to additionally develop a CBT driver, so that the cost is increased;
2. the CBT needs to be realized by combining with the bottom technology of an operating system, and the execution complexity is high;
3. unlike a general application program, the CBT runs in a Windows kernel mode (kernel mode), and once the CBT has an error, the system is easily unstable, such as blue screen, crash, system crash, and the like;
4. in order to realize real-time Hyper-V virtual machine incremental backup, CBT intervention is needed when the data of the virtual machine is changed, and the performance of write data of the Hyper-V virtual machine is influenced.
Disclosure of Invention
The present invention aims to solve at least to some extent one of the technical problems existing in the prior art.
Therefore, an object of the embodiments of the present invention is to provide a method for incremental backup of a virtual machine, where the method implements incremental backup of the virtual machine without installing a CBT, improves performance of the virtual machine, and reduces cost.
Another object of an embodiment of the present invention is to provide a virtual machine incremental backup system.
In order to achieve the technical purpose, the technical scheme adopted by the embodiment of the invention comprises the following steps:
in a first aspect, an embodiment of the present invention provides a virtual machine incremental backup method, including the following steps:
confirming that the number of times of the incremental backup of the virtual machine is the first time, and listing the virtual disks of the virtual machine;
generating a first sub-virtual disk of the virtual machine;
redirecting the data updating operation of the virtual machine from the virtual disk to the first sub-virtual disk, and setting the virtual disk to be in a read-only state;
backing up the virtual disk;
confirming that the number of times of the incremental backup of the virtual machine is not the first time, and generating a second sub virtual disk of the virtual machine;
redirecting the data updating operation of the virtual machine from a third sub virtual disk to the second sub virtual disk, and setting the third sub virtual disk to be in a read-only state, wherein the third sub virtual disk is a sub virtual disk generated in the last incremental backup of the virtual machine;
backing up the third sub virtual disk;
merging the third sub virtual disk to the virtual disk, and deleting the third sub virtual disk.
According to the incremental backup method of the virtual machine, the sub-virtual disk written with the updated data is generated, and the incremental backup of the virtual machine is realized through the backup sub-virtual disk, so that the real-time incremental backup of the virtual machine can be realized without the intervention of CBT when the data of the virtual machine is changed, the performance of the virtual machine is improved, the execution complexity and the cost of the incremental backup of the virtual machine are reduced, the serious instability of a system caused by the error of the CBT is avoided, and the stability of the virtual machine is improved; and after the sub virtual disk backup is finished, the sub virtual disks are merged and deleted, so that the memory occupation of the virtual machine is reduced, and the performance of the virtual machine is further improved.
In addition, the incremental backup method for a virtual machine according to the above embodiment of the present invention may further have the following additional technical features:
further, in the incremental backup method for a virtual machine according to the embodiment of the present invention, the generating a first sub virtual disk of the virtual machine includes:
creating a first checkpoint of the virtual machine;
and generating the first sub-virtual disk according to the first check point.
Further, in an embodiment of the present invention, the redirecting the data update operation of the virtual machine from the virtual disk to the first child virtual disk includes:
redirecting data update operations of the virtual machine from the virtual disk to the first child virtual disk through the first checkpoint.
Further, in an embodiment of the present invention, the determining that the number of times of the incremental backup of the virtual machine is not the first time, and generating a second sub virtual disk of the virtual machine includes:
creating a second checkpoint of the virtual machine;
and generating the second sub virtual disk according to the second check point.
Further, in an embodiment of the present invention, the redirecting the data update operation of the virtual machine from the third child virtual disk to the second child virtual disk includes:
redirecting data update operations of the virtual machine from the third child virtual disk to the second child virtual disk through the second checkpoint.
Further, in an embodiment of the present invention, after the step of backing up the third child virtual disk, the method further includes the following steps:
and deleting a third check point, wherein the third check point is a virtual machine check point created when the third sub virtual disk is generated.
In a second aspect, an embodiment of the present invention provides a virtual machine incremental backup system, including:
the virtual disk display module is used for determining that the number of times of incremental backup of the virtual machine is the first time and listing the virtual disks of the virtual machine;
the sub virtual disk generation module is used for generating a first sub virtual disk of the virtual machine, confirming that the number of times of incremental backup of the virtual machine is not the first time, and generating a second sub virtual disk of the virtual machine;
a disk redirection module, configured to redirect a data update operation of the virtual machine from the virtual disk to the first sub virtual disk and set the virtual disk to a read-only state, and to redirect a data update operation of the virtual machine from a third sub virtual disk to the second sub virtual disk and set the third sub virtual disk to a read-only state;
the disk backup module is used for backing up the virtual disk and backing up the third sub virtual disk;
and the disk merging module is used for merging the third sub virtual disk to the virtual disk and deleting the third sub virtual disk.
Further, in an embodiment of the present invention, the child virtual disk generation module includes:
a checkpoint creation module to create a first checkpoint of the virtual machine and to create a second checkpoint of the virtual machine.
In a third aspect, an embodiment of the present invention provides a virtual machine incremental backup apparatus, including:
at least one processor;
at least one memory for storing at least one program;
when executed by the at least one processor, the at least one program causes the at least one processor to implement the method for incremental backup of a virtual machine.
In a fourth aspect, an embodiment of the present invention provides a storage medium, in which a processor-executable program is stored, where the processor-executable program is used to implement the method for incremental backup of a virtual machine when executed by a processor.
Advantages and benefits of the present invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application:
the embodiment of the invention generates the sub virtual disk written with the updated data and realizes the incremental backup of the virtual machine by backing up the sub virtual disk, so that the real-time incremental backup of the virtual machine can be realized without the intervention of CBT when the data of the virtual machine is changed, the performance of the virtual machine is improved, the execution complexity and the cost of the incremental backup of the virtual machine are reduced, the serious instability phenomenon of a system caused by the error of the CBT is avoided, and the stability of the virtual machine is improved; and after the sub virtual disk backup is finished, the sub virtual disks are merged and deleted, so that the memory occupation of the virtual machine is reduced, and the performance of the virtual machine is further improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description is made on the drawings of the embodiments of the present application or the related technical solutions in the prior art, and it should be understood that the drawings in the following description are only for convenience and clarity of describing some embodiments in the technical solutions of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic flowchart of an embodiment of a virtual machine incremental backup method according to the present invention;
FIG. 2 is a schematic structural diagram of an embodiment of a virtual machine incremental backup system according to the present invention;
fig. 3 is a schematic structural diagram of an embodiment of an incremental backup device of a virtual machine according to the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative and are only for the purpose of explaining the present application and are not to be construed as limiting the present application. The step numbers in the following embodiments are provided only for convenience of illustration, the order between the steps is not limited at all, and the execution order of each step in the embodiments can be adapted according to the understanding of those skilled in the art.
The terms "first," "second," "third," and "fourth," etc. in the description and claims of the invention and in the accompanying drawings are used for distinguishing between different elements and not for describing a particular sequential order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
Hyper-V is the virtual machine management software released by Microsoft, and a virtual machine can be created on a Windows system through Hyper-V. Key business data of enterprise users are usually stored in the Hyper-V virtual machine. In order to avoid data loss stored in the Hyper-V virtual machine caused by misoperation, system failure, natural disasters, computer viruses and the like, a user needs to regularly back up the Hyper-V virtual machine. Incremental backups are in place in order to reduce the amount of data that needs to be backed up each time a user backs up a Hyper-V virtual machine. Incremental backups only backup data blocks that have changed since the last backup. When a user performs incremental backup on a Hyper-V virtual machine, a Windows block modification tracking (CBT) driver developed by a manufacturer of backup software needs to be installed on a Hyper-V host. When the data of the virtual machine is changed, the CBT intervenes in real time, intercepts and captures the data blocks for recording the change and backups the data blocks. And the quick acquisition and backup of all changed data blocks are realized. After the backup is completed, the CBT clears the recorded data blocks and re-records the changed data blocks until the next backup.
However, the current use of CBTs for incremental backup of Hyper-V virtual machines has the following problems:
1. manufacturers need to additionally develop a CBT driver, so that the cost is increased;
2. the CBT needs to be realized by combining with the bottom technology of an operating system, and the execution complexity is high;
3. unlike a general application program, the CBT runs in a Windows kernel mode (kernel mode), and once the CBT has an error, the system is easily unstable, such as blue screen, crash, system crash, and the like;
4. in order to realize real-time Hyper-V virtual machine incremental backup, CBT intervention is needed when the data of the virtual machine is changed, and the performance of write data of the Hyper-V virtual machine is influenced.
The invention provides a virtual machine incremental backup method and a virtual machine incremental backup system, which are characterized in that a sub-virtual disk written with updated data is generated, and the incremental backup of a virtual machine is realized by backing up the sub-virtual disk, so that the real-time virtual machine incremental backup can be realized without the intervention of CBT when the data of the virtual machine is changed, the performance of the virtual machine is improved, the execution complexity and the cost of the virtual machine incremental backup are reduced, the serious instability of the system caused by the error of the CBT is avoided, and the stability of the virtual machine is improved; and after the sub virtual disk backup is finished, the sub virtual disks are merged and deleted, so that the memory occupation of the virtual machine is reduced, and the performance of the virtual machine is further improved.
The following describes a virtual machine incremental backup method and system according to an embodiment of the present invention in detail with reference to the accompanying drawings, and first, a virtual machine incremental backup method according to an embodiment of the present invention will be described with reference to the accompanying drawings.
Referring to fig. 1, an embodiment of the present invention provides a virtual machine incremental backup method, where the virtual machine incremental backup method in the embodiment of the present invention may be applied to a terminal, a server, or software running in the terminal or the server. The terminal may be, but is not limited to, a tablet computer, a notebook computer, a desktop computer, and the like. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, middleware service, a domain name service, a security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like. The incremental backup method of the virtual machine in the embodiment of the invention mainly comprises the following steps:
s101, confirming that the number of times of incremental backup of the virtual machine is the first time, and listing virtual disks of the virtual machine;
specifically, when the incremental backup of the virtual machine in the embodiment of the present invention is not performed, the virtual disk is a disk used for reading and writing data in the virtual machine, and the data update in the virtual machine is written into the virtual disk.
S102, generating a first sub virtual disk of the virtual machine;
and the first sub-virtual disk and the virtual disk have the same format.
S102 may be further divided into the following steps S1021-S1022:
step S1021, a first check point of the virtual machine is established;
the first checkpoint is used for generating the readable and writable first sub virtual disk and redirecting data updating operation of the virtual machine from the virtual disk to the first sub virtual disk.
Step S1022, generating the first sub virtual disk according to the first checkpoint.
S103, redirecting the data updating operation of the virtual machine from the virtual disk to the first sub virtual disk, and setting the virtual disk to be in a read-only state;
specifically, according to step S1021, the data update operation of the virtual machine is redirected from the virtual disk to the first sub-virtual disk through the first check point.
After the data updating operation of the virtual machine is redirected from the virtual disk to the first sub-virtual disk, the virtual disk is set to be in a read-only state, and data stored in the virtual disk is prevented from being changed.
S104, backing up the virtual disk;
specifically, it may be understood that, in the backup process of the virtual disk, if the virtual disk is in a readable and writable state, the virtual machine may perform a data writing operation on the virtual disk at the same time, so that the virtual disk is updated in the backup process, and the data obtained by the backup is inconsistent dirty data. As shown in step S103, in the embodiment of the present invention, the virtual disk is in a read-only state. Therefore, in the backup process of the virtual disk, the virtual machine cannot write data into the virtual disk, that is, the virtual disk and the data therein are not modified, so that the consistency between the backup data and the data in the virtual disk is ensured.
S105, confirming that the number of times of incremental backup of the virtual machine is not the first time, and generating a second sub virtual disk of the virtual machine;
and the format of the second sub virtual disk is the same as that of the virtual disk.
Specifically, when the number of times of the incremental backup of the virtual machine is not the first time, it can be known from steps S101 to S104 that a child virtual disk storing updated data already exists in the virtual machine, that is, the child virtual disk generated in the last incremental backup. And when the incremental backup of the virtual machine is carried out at the time, generating a new sub virtual disk, namely the second sub virtual disk.
S105 may be further divided into the following steps S1051-S1052:
step S1051, creating a second check point of the virtual machine;
the second checkpoint is used for generating a readable and writable second sub virtual disk, and redirecting the data updating operation of the virtual machine from the sub virtual disk generated in the last incremental backup to the second sub virtual disk.
Step S1052, generating the second sub virtual disk according to the second checkpoint.
S106, redirecting the data updating operation of the virtual machine from a third sub virtual disk to the second sub virtual disk, and setting the third sub virtual disk to be in a read-only state;
and the third sub-virtual disk is a sub-virtual disk generated in the last incremental backup of the virtual machine. It is understood that, when the number of incremental backups is the second time, the third sub-virtual disk is equivalent to the first sub-virtual disk generated in the first incremental backup (steps S101 to S104).
Specifically, according to step S1051, the data update operation of the virtual machine is redirected from the third sub virtual disk to the second sub virtual disk through the second check point.
After the data updating operation of the virtual machine is redirected from the third sub virtual disk to the second sub virtual disk, the third sub virtual disk is set to a read-only state, and data (updating data between the first incremental backup and the second incremental backup) stored in the third sub virtual disk is prevented from being changed.
S107, backing up the third sub virtual disk;
specifically, according to the step S104, it can be understood that, in the backup process of the third sub-virtual disk, if the third sub-virtual disk is in a readable and writable state, the virtual machine may perform a data writing operation on the third sub-virtual disk at the same time, so that the third sub-virtual disk is updated in the backup process, and the backed-up data is inconsistent dirty data. As shown in step S106, in the embodiment of the present invention, the third sub virtual disk is in a read-only state. Therefore, in the backup process of the third sub virtual disk, the virtual machine cannot write data into the third sub virtual disk, that is, the third sub virtual disk and the data therein are not modified, so that consistency between the backup data and the data in the third sub virtual disk is ensured.
And S108, merging the third sub virtual disk to the virtual disk, and deleting the third sub virtual disk.
Specifically, in the embodiment of the present invention, after the step of backing up the third child virtual disk, the method further includes the following steps:
and deleting a third check point, wherein the third check point is a virtual machine check point created when the third sub virtual disk is generated.
As can be seen from step S106, when the number of times of the incremental backup is the second time, the third sub-virtual disk is equivalent to the first sub-virtual disk generated in the first incremental backup (steps S101 to S104), and it can be understood that the third checkpoint is equivalent to the first checkpoint.
After the incremental backup of the virtual machine is completed, the performance reduction of the virtual machine caused by the simultaneous existence of a plurality of check points in the virtual machine is avoided by deleting the third check point.
As can be seen from step S105(S102), the format of the third sub-virtual disk (which is equivalent to the first sub-virtual disk when the current incremental backup is the second incremental backup) is the same as that of the virtual disk, and disk merging can be achieved. Therefore, after the third checkpoint is deleted, in order to avoid performance degradation of the virtual machine due to the fact that multiple sub virtual disks exist in the virtual machine at the same time, the third sub virtual disk is merged into the virtual disk, and the third sub virtual disk in the virtual machine is deleted, that is, the sub virtual disk generated in the last incremental backup is merged into the virtual disk of the virtual machine and deleted.
After the incremental backup is completed, only the second check point, the second sub-virtual disk and the virtual disk are reserved in the virtual machine, so that the influence of the incremental backup method of the virtual machine on the performance of the virtual machine is minimized.
Next, a virtual machine incremental backup system proposed according to an embodiment of the present application is described with reference to the drawings.
Fig. 2 is a schematic structural diagram of a virtual machine incremental backup system according to an embodiment of the present application.
The system specifically comprises:
a virtual disk display module 201, configured to determine that the number of times of incremental backup of the virtual machine is the first time, and list virtual disks of the virtual machine;
a sub-virtual disk generation module 202, configured to generate a first sub-virtual disk of the virtual machine, and to determine that the number of times of incremental backup of the virtual machine is not the first time, and generate a second sub-virtual disk of the virtual machine;
a disk redirection module 203, configured to redirect the data update operation of the virtual machine from the virtual disk to the first sub virtual disk and set the virtual disk to a read-only state, and redirect the data update operation of the virtual machine from a third sub virtual disk to the second sub virtual disk and set the third sub virtual disk to a read-only state;
a disk backup module 204, configured to backup the virtual disk and backup the third sub-virtual disk;
a disk merging module 205, configured to merge the third sub virtual disk into the virtual disk, and delete the third sub virtual disk.
In an embodiment of the present invention, the child virtual disk generation module includes:
a checkpoint creation module to create a first checkpoint of the virtual machine and to create a second checkpoint of the virtual machine.
It can be seen that the contents in the foregoing method embodiments are all applicable to this system embodiment, the functions specifically implemented by this system embodiment are the same as those in the foregoing method embodiment, and the advantageous effects achieved by this system embodiment are also the same as those achieved by the foregoing method embodiment.
Referring to fig. 3, an embodiment of the present application provides a virtual machine incremental backup apparatus, including:
at least one processor 301;
at least one memory 302 for storing at least one program;
when executed by the at least one processor 301, the at least one program causes the at least one processor 301 to implement the method for incremental backup of a virtual machine.
Similarly, the contents of the method embodiments are all applicable to the apparatus embodiments, the functions specifically implemented by the apparatus embodiments are the same as the method embodiments, and the beneficial effects achieved by the apparatus embodiments are also the same as the beneficial effects achieved by the method embodiments.
In alternative embodiments, the functions/acts noted in the block diagrams may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Furthermore, the embodiments presented and described in the flowcharts of the present application are provided by way of example in order to provide a more thorough understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed and in which sub-operations described as part of larger operations are performed independently.
Furthermore, although the present application is described in the context of functional modules, it should be understood that, unless otherwise stated to the contrary, one or more of the functions and/or features may be integrated in a single physical device and/or software module, or one or more functions and/or features may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion regarding the actual implementation of each module is not necessary for an understanding of the present application. Rather, the actual implementation of the various functional modules in the apparatus disclosed herein will be understood within the ordinary skill of an engineer, given the nature, function, and internal relationship of the modules. Accordingly, those skilled in the art can, using ordinary skill, practice the present application as set forth in the claims without undue experimentation. It is also to be understood that the specific concepts disclosed are merely illustrative of and not intended to limit the scope of the application, which is defined by the appended claims and their full scope of equivalents.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium, which includes programs for enabling a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to 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 (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.
The logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable programs that can be considered for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with a program execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the programs from the program execution system, apparatus, or device and execute the programs. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the program execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable program execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In the foregoing description of the specification, reference to the description of "one embodiment/example," "another embodiment/example," or "certain embodiments/examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described, it will be understood by those of ordinary skill in the art that: numerous changes, modifications, substitutions and alterations can be made to the embodiments without departing from the principles and spirit of the application, the scope of which is defined by the claims and their equivalents.
While the present application has been described with reference to the preferred embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (10)
1. A virtual machine incremental backup method is characterized by comprising the following steps:
confirming that the number of times of the incremental backup of the virtual machine is the first time, and listing the virtual disks of the virtual machine;
generating a first sub-virtual disk of the virtual machine;
redirecting the data updating operation of the virtual machine from the virtual disk to the first sub-virtual disk, and setting the virtual disk to be in a read-only state;
backing up the virtual disk;
confirming that the number of times of the incremental backup of the virtual machine is not the first time, and generating a second sub virtual disk of the virtual machine;
redirecting the data updating operation of the virtual machine from a third sub virtual disk to the second sub virtual disk, and setting the third sub virtual disk to be in a read-only state, wherein the third sub virtual disk is a sub virtual disk generated in the last incremental backup of the virtual machine;
backing up the third sub virtual disk;
merging the third sub virtual disk to the virtual disk, and deleting the third sub virtual disk.
2. The method for incremental backup of a virtual machine according to claim 1, wherein the generating a first child virtual disk of the virtual machine includes:
creating a first checkpoint of the virtual machine;
and generating the first sub-virtual disk according to the first check point.
3. The method for incremental backup of a virtual machine according to claim 2, wherein said redirecting the data update operation of the virtual machine from the virtual disk to the first child virtual disk comprises:
redirecting data update operations of the virtual machine from the virtual disk to the first child virtual disk through the first checkpoint.
4. The method according to claim 1, wherein the step of generating the second sub virtual disk of the virtual machine, which is performed after confirming that the number of times of the incremental backup of the virtual machine is not the first time, comprises:
creating a second checkpoint of the virtual machine;
and generating the second sub virtual disk according to the second check point.
5. The method for incremental backup of a virtual machine according to claim 4, wherein the redirecting the data update operation of the virtual machine from a third child virtual disk to the second child virtual disk comprises:
redirecting data update operations of the virtual machine from the third child virtual disk to the second child virtual disk through the second checkpoint.
6. The incremental backup method for the virtual machine according to claim 1, further comprising, after the step of backing up the third child virtual disk, the steps of:
and deleting a third check point, wherein the third check point is a virtual machine check point created when the third sub virtual disk is generated.
7. A virtual machine incremental backup system, comprising:
the virtual disk display module is used for confirming that the number of times of the incremental backup of the virtual machine is the first time and listing the virtual disks of the virtual machine;
the sub virtual disk generation module is used for generating a first sub virtual disk of the virtual machine, confirming that the number of times of incremental backup of the virtual machine is not the first time, and generating a second sub virtual disk of the virtual machine;
a disk redirection module, configured to redirect a data update operation of the virtual machine from the virtual disk to the first sub virtual disk and set the virtual disk to a read-only state, and to redirect a data update operation of the virtual machine from a third sub virtual disk to the second sub virtual disk and set the third sub virtual disk to a read-only state;
the disk backup module is used for backing up the virtual disk and backing up the third sub-virtual disk;
and the disk merging module is used for merging the third sub virtual disk to the virtual disk and deleting the third sub virtual disk.
8. The incremental backup system for virtual machine according to claim 7, wherein said child virtual disk generation module comprises:
a checkpoint creation module to create a first checkpoint of the virtual machine and to create a second checkpoint of the virtual machine.
9. An incremental backup device for a virtual machine, comprising:
at least one processor;
at least one memory for storing at least one program;
when executed by the at least one processor, the at least one program causes the at least one processor to implement a virtual machine incremental backup method as claimed in any one of claims 1-6.
10. A storage medium having stored therein a program executable by a processor, characterized in that: the processor executable program when executed by a processor is for implementing a virtual machine incremental backup method as claimed in any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210098091.1A CN114518936A (en) | 2022-01-27 | 2022-01-27 | Virtual machine incremental backup method, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210098091.1A CN114518936A (en) | 2022-01-27 | 2022-01-27 | Virtual machine incremental backup method, system, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114518936A true CN114518936A (en) | 2022-05-20 |
Family
ID=81596445
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210098091.1A Pending CN114518936A (en) | 2022-01-27 | 2022-01-27 | Virtual machine incremental backup method, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114518936A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103678045A (en) * | 2013-12-31 | 2014-03-26 | 曙光云计算技术有限公司 | Data backup method for virtual machines |
| US20150186823A1 (en) * | 2013-12-26 | 2015-07-02 | Infosys Limited | Methods, systems and computer-readable media for componentizing a business requirement |
| CN104781791A (en) * | 2011-12-05 | 2015-07-15 | 持续电信解决方案公司 | Universal pluggable cloud disaster recovery system |
| CN112256400A (en) * | 2020-10-29 | 2021-01-22 | 上海英方软件股份有限公司 | Virtual machine snapshot management method and device |
| CN113377445A (en) * | 2021-08-16 | 2021-09-10 | 北京升鑫网络科技有限公司 | Method and device for starting multiple operating systems from online disk |
| CN113626261A (en) * | 2021-10-13 | 2021-11-09 | 苏州浪潮智能科技有限公司 | Data backup method, device and equipment and computer readable storage medium |
-
2022
- 2022-01-27 CN CN202210098091.1A patent/CN114518936A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104781791A (en) * | 2011-12-05 | 2015-07-15 | 持续电信解决方案公司 | Universal pluggable cloud disaster recovery system |
| US20150186823A1 (en) * | 2013-12-26 | 2015-07-02 | Infosys Limited | Methods, systems and computer-readable media for componentizing a business requirement |
| CN103678045A (en) * | 2013-12-31 | 2014-03-26 | 曙光云计算技术有限公司 | Data backup method for virtual machines |
| CN112256400A (en) * | 2020-10-29 | 2021-01-22 | 上海英方软件股份有限公司 | Virtual machine snapshot management method and device |
| CN113377445A (en) * | 2021-08-16 | 2021-09-10 | 北京升鑫网络科技有限公司 | Method and device for starting multiple operating systems from online disk |
| CN113626261A (en) * | 2021-10-13 | 2021-11-09 | 苏州浪潮智能科技有限公司 | Data backup method, device and equipment and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7831769B1 (en) | System and method for performing online backup and restore of volume configuration information | |
| CN109582443A (en) | Virtual machine standby system based on distributed storage technology | |
| US11093387B1 (en) | Garbage collection based on transmission object models | |
| CN103810058A (en) | Backup method, equipment and system for virtual machine | |
| US20040199521A1 (en) | Method, system, and program for managing groups of objects when there are different group types | |
| US10503620B1 (en) | Parity log with delta bitmap | |
| US7984023B2 (en) | Method and utility for copying files from a faulty disk | |
| US9734022B1 (en) | Identifying virtual machines and errors for snapshots | |
| US10387262B1 (en) | Federated restore of single instance databases and availability group database replicas | |
| CN112269679B (en) | Database persistence method, system, equipment and storage medium of cloud platform | |
| US10176052B2 (en) | Snapshot backup with unified restore information | |
| US20210326271A1 (en) | Stale data recovery using virtual storage metadata | |
| US11334456B1 (en) | Space efficient data protection | |
| CN114518936A (en) | Virtual machine incremental backup method, system, device and storage medium | |
| US10664346B2 (en) | Parity log with by-pass | |
| US11675931B2 (en) | Creating vendor-neutral data protection operations for vendors' application resources | |
| US10880388B1 (en) | Automatic redirection in scale-out cluster environments that perform distributed deduplication | |
| CN109241011B (en) | Virtual machine file processing method and device | |
| US10884874B1 (en) | Federated restore of availability group database replicas | |
| US10938919B1 (en) | Registering client devices with backup servers using domain name service records | |
| US11520668B2 (en) | Vendor-neutral models of vendors' application resources | |
| US11372732B2 (en) | Systems and methods for agentless and accelerated backup of a database | |
| US10379962B1 (en) | De-duplicating backup files based on data evolution | |
| US20210124513A1 (en) | Power reduction in distributed storage systems | |
| CN117573612A (en) | Directory snapshot management method and device of distributed file system |
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: 20220520 |
|
| RJ01 | Rejection of invention patent application after publication |