Reverse incremental backup method and device for own data format of virtual machine and medium

Abstract

The invention discloses a reverse incremental backup method and device for a self-owned data format of a virtual machine and a medium, and the method comprises the steps: responding to the obtained last backup point, and reading the change data block information of the backup point; obtaining incremental change data block information of the current backup; creating a virtual machine data file at the current backup point to store virtual machine data, and creating a reverse incremental data file at the previous backup point to store reverse incremental data; checking the position and the size of each data block from the 0 position to the end of the disk of the virtual machine, and respectively processing according to the checking result; respectively checking change data block information recorded on the previous backup point and the current backup point, and if data blocks connected together exist, performing splicing; respectively storing the change data block information recorded on the previous backup point and the current backup point into the corresponding backup points; and deleting the old full data file on the previous backup point.

Description

Technical Field

[0001] The present invention relates to the technical field of computer data disaster recovery backup, and in particular to a reverse incremental backup method, device and computer medium based on a proprietary data format in virtual machine protection. Background Art

[0002] With the rapid development of information technology, the demand for computing infrastructure has continued to increase in the process of informatization construction, and the requirements for hardware equipment, software, maintenance costs and timeliness have become increasingly higher. In order to improve infrastructure utilization and reduce time and money expenditures, hardware virtualization has emerged.

[0003] With the widespread application of virtualization, virtual machines, as the most important basic data, have become a necessary configuration for protection, and there are more and more products that protect virtual machines in virtualization platforms.

[0004] The protection of virtual machines can be divided into backup and recovery, and the derived migration, replication and disaster switching. Backup can be divided into full backup, incremental backup and differential backup. Full backup refers to backing up all the data of the virtual machine; incremental backup refers to backing up the changed data based on the last backup (which can be full or incremental). The incremental backup data depends on the previous backup data, which easily forms a very long backup chain; differential backup refers to backing up the changed data based on the last full backup. The differential backup data only depends on the full backup, and there are only two data chains. In actual use, the most commonly used is the combination of full backup and incremental backup. The first periodic full backup is to generate a complete virtual machine backup data, and then multiple incremental backups are performed based on this full backup. Because incremental backup is only performed on changed data, it is fast and has low overhead, and it will be executed more frequently, which easily forms a very long backup chain. If a piece of data in the chain has a problem, all subsequent backup data will be unavailable. In addition, when the backup dependency chain is very long, recovery will be very slow, and all data in the backup chain needs to be collected. In particular, in actual scenarios, the older data is less important and is likely to be cleared, while the more recent data is more likely to be restored, and the more recent data is likely to be incremental data. In this case, you need to keep going back to find the full data and restore it. Therefore, the latest data is the most important and the most likely to be restored, which gave rise to the reverse incremental backup method. Reverse incremental means incremental in the opposite direction. The latest backup data is always the full data, and the second-to-last data is the reverse increment of this full data, that is, the old data in the changed data.

[0005] At present, some manufacturers' virtual machine protection products have implemented the reverse incremental backup method, but there are still some deficiencies in terms of function and performance: (1) The reverse incremental performance of some products is not high. After all, backup tasks are daily tasks, and recovery is only used when problems occur.

[0006] (2) The reverse incremental backup of some products takes up a lot of space. Each incremental backup point has space redundancy, and the storage cost is too high.

[0007] (3) Without independent control machines, control machine servers, and target proxy virtual machines to collaborate, it is impossible to achieve a highly scalable and high-performance migration system; it is impossible to easily implement virtual machine migration of other types of platforms; and it is impossible to easily integrate with other data migration methods, such as block device data migration and file system data migration. Summary of the invention

[0008] In order to overcome the deficiencies of the above-mentioned prior art, the purpose of the present invention is to provide a method, device and computer storage medium for reverse incremental backup of a virtual machine's own data format, which uses its own data format to implement a reverse incremental backup method, thereby achieving more flexible backup and more efficient recovery.

[0009] To achieve the above object, the present invention proposes a method for reverse incremental backup of a virtual machine's own data format, comprising the following steps: Preferably, in response to obtaining the most recent backup point, reading the changed data block information in the most recent backup point; Get the incremental change data block information of the current backup; A new virtual machine data file is created at the current backup point to store virtual machine data, and a new reverse incremental data file is created at the previous backup point to store reverse incremental data; Check the location and size of each data block from position 0 to the end of the virtual machine disk, and process them separately according to the inspection results; Check the changed data block information recorded at the previous backup point and the current backup point respectively. If there are data blocks that are connected in position, they will be spliced; The changed data block information recorded at the previous backup point and the current backup point is saved to the corresponding backup points respectively; Delete the old full data file on the previous backup point. The reverse incremental data has been saved in the reverse incremental data file of the previous backup node.

[0010] Preferably, the step of checking the position and size of each data block from position 0 to the end of the virtual machine disk and processing them respectively according to the checking results comprises the following steps: In response to the data block being only in the changed data block of the previous backup point, the corresponding data of the previous backup point is read and saved into the data file of the current backup point, and the changed data block information is recorded at the current backup point; In response to the data block being only in the changed data block of the current backup point, the empty data is written into the reverse incremental data file of the previous backup point, and the changed data block information is recorded at the previous backup point; the corresponding position data of the data block is read from the source virtual machine, saved to the virtual machine data file of the current backup point, and the changed data block information is recorded at the current backup point; In response to the data block being in the changed data block of both the previous backup point and the current backup point, the data corresponding to the data block at the previous backup point is read, written to the reverse incremental data file at the previous backup point, and the changed data block information is recorded at the previous backup point; the data corresponding to the position of the data block is read from the source virtual machine data block, written to the virtual machine data file at the current backup point, and the changed data block information is recorded at the current backup point; In response to the data block not being in the changed data block information of either the previous backup point or the current backup point, no processing is performed.

[0011] Preferably, before responding to obtaining the most recent backup point and reading the changed data block information in the most recent backup point, the following steps are also included: The most recent backup point is obtained. If the most recent backup point is not obtained, a full backup is performed uniformly regardless of the backup type specified. The backup types include full backup and reverse incremental backup.

[0012] Preferably, the changed data block information records the data block information of each virtual machine disk, including the position and size of the data block in the virtual machine disk.

[0013] Preferably, the changed data block information is divided into full changed data blocks and incremental changed data blocks according to different backup types.

[0014] Preferably, checking the position and size of each data block includes: The data blocks are fixedly configured to a specific size, and the position of each data block is checked; the specific size is the minimum unit of the changed data block.

[0015] To achieve the above purpose, the present invention also discloses a reverse incremental backup device of a virtual machine's own data format, comprising: A changed data block information reading module, configured to read the changed data block information in the most recent backup point in response to obtaining the most recent backup point; The incremental change data block information acquisition module is used to obtain the incremental change data block information of the current backup; A data file creation module is used to create a virtual machine data file at the current backup point to store virtual machine data, and to create a reverse incremental data file at the previous backup point to store reverse incremental data; The data block check processing module is used to check the position and size of each data block from the 0 position to the end of the virtual machine disk, and process them separately according to the check results; The data block splicing module is used to check the changed data block information recorded at the previous backup point and the current backup point respectively, and if there are data blocks that are connected in position, they are spliced; The changed data block information saving module is used to save the changed data block information recorded at the previous backup point and the current backup point to the corresponding backup points respectively; The full data file deletion module is used to delete the old full data file at the previous backup point. The reverse incremental data has been saved in the reverse incremental data file of the previous backup node.

[0016] Preferably, the data block inspection processing module is specifically used for: In response to the data block being only in the changed data block of the previous backup point, the corresponding data of the previous backup point is read and saved into the data file of the current backup point, and the changed data block information is recorded at the current backup point; In response to the data block being only in the changed data block of the current backup point, the empty data is written into the reverse incremental data file of the previous backup point, and the changed data block information is recorded at the previous backup point; the corresponding position data of the data block is read from the source virtual machine, saved to the virtual machine data file of the current backup point, and the changed data block information is recorded at the current backup point; In response to the data block being in the changed data block of both the previous backup point and the current backup point, the data corresponding to the data block at the previous backup point is read, written to the reverse incremental data file at the previous backup point, and the changed data block information is recorded at the previous backup point; the data corresponding to the position of the data block is read from the source virtual machine data block, written to the virtual machine data file at the current backup point, and the changed data block information is recorded at the current backup point; If the data block is not in the changed data block information of the previous backup point or the current backup point, it will not be processed.

[0017] Preferably, the device also includes a full backup module for obtaining the most recent backup point. If the most recent backup point is not obtained, a full backup is performed uniformly regardless of which backup type is specified. The backup types include full backup and reverse incremental backup.

[0018] To achieve the above object, the present invention further discloses a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to execute any of the above-mentioned methods for reverse incremental backup of a virtual machine's own data format.

[0019] Compared with the prior art, one aspect of the method, device and computer storage medium for reverse incremental backup of a virtual machine's own data format of the present invention has the following advantages: The backup data and the changed block information in the embodiment of the present invention are isolated, and the speed is fast when only the changed block information is obtained, and there is no need to read the data file; The backup data in the embodiment of the present invention is valid data that is continuously saved, does not waste space, and has good support for deduplication; The embodiment of the present invention is aimed at reverse incremental backup of a general virtual machine and is applicable to all virtual platforms; The new backup point backup data generated by the reverse incremental method in the embodiment of the present invention is a full amount of data. When restoring, there is no need to find the backup data chain and read the data separately, so the recovery speed of the latest backup point is fast. The backup data generated by the embodiment of the present invention has a shorter backup chain and a faster recovery for more recent data; and most recovery operations are performed on new data, which better meets customer needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a flowchart of the steps of the reverse incremental backup method of the virtual machine's own data format disclosed by the present invention; Figure 2 It is a structural framework diagram of the virtual machine's own data format reverse incremental backup device disclosed in the present invention; Figure 3 A schematic diagram of disk change block information disclosed in an embodiment of the present invention; Figure 4 The figure is a flow chart of a reverse incremental backup method disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0021] The following describes the implementation of the present invention through specific examples and in conjunction with the accompanying drawings. Those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific examples, and the details in this specification can also be modified and changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention.

[0022] In order to better understand the technical solution of the present invention, the inherent data format and reverse incremental backup of the present invention are now described: The proprietary data format includes backup point metadata, change block information (CBT), and disk data blocks.

[0023] The backup point metadata contains all metadata information of the backup, such as the basic configuration of the backed-up virtual machine (CPU, memory, disk, network and other device configurations), time, backup type and backup options.

[0024] The changed data block information records the data block information of each virtual machine disk. The data block contains its location and size in the virtual machine disk. In the case of full data, it is the data block of the disk's valid data, and in the case of incremental data, it is the data block of the disk's changes.

[0025] Disk data blocks store disk data. Unlike the original disk format, the disk data here is saved continuously and there is no invalid data.

[0026] Reverse incremental backup is to achieve the reverse configuration of data storage when performing incremental backup at an existing backup point; that is, the latest full data is saved at the latest backup point, and the old data covered by the incremental data is saved in the previous backup point. This is more conducive to data security and more convenient for virtual machine recovery.

[0027] As attached Figure 1 , Attachment Figure 4 As shown, a method for reverse incremental backup of a virtual machine's own data format disclosed in an embodiment of the present invention includes the following steps: Step S1, in response to obtaining the most recent backup point, reading the changed data block information in the most recent backup point; Step S2, obtaining the incremental change data block information of the current backup; Step S3, creating a new virtual machine data file at the current backup point to store virtual machine data, and creating a new reverse incremental data file at the previous backup point to store reverse incremental data; Step S4, checking the position and size of each data block from position 0 to the end of the virtual machine disk, and processing them respectively according to the inspection results; Step S5, respectively checking the changed data block information recorded at the previous backup point and the current backup point, and if there are data blocks that are connected in position, splicing them; Step S6, saving the changed data block information recorded at the previous backup point and the current backup point to the corresponding backup points respectively; Step S7, delete the old full data file on the previous backup point. At this time, the reverse incremental data has been saved in the reverse incremental data file of the previous backup node.

[0028] Specifically, to perform a reverse incremental backup, you need to first do a full backup and one or several reverse incremental backups. If the most recent backup point is not obtained, it means that the first full backup has not been performed. In addition, to obtain the incremental change data block information of the current backup, that is, to obtain the incremental data of the virtual machine, there are different methods for different platforms. VMware and Hyper-V (Windows 2016 and later versions) provide public interface calls for implementation. Most other platforms must independently implement the method of obtaining change blocks, which belongs to the prior art and will not be repeated here. In this implementation scheme, the data of a disk file of the virtual machine is processed, and the virtual machine may have more than one disk file. For multiple disk files, the process is consistent.

[0029] Furthermore, before step S1, the following steps are also included: The most recent backup point is obtained. If the most recent backup point is not obtained, a full backup is performed uniformly regardless of the backup type specified. The backup types include full backup and reverse incremental backup.

[0030] Specifically, the most recent backup point is obtained. If it is not obtained, a full backup is performed regardless of the specified backup type (full or reverse incremental). If the most recent backup point is obtained, the changed data block information file in the backup point (full backup or reverse incremental backup) is read. The changed data block information file is a full changed data block information file or an incremental changed data block information file.

[0031] Further in a preferred embodiment of the present invention, in step S4, the virtual machine disk is checked from position 0 to the end of the disk, and the position and size of each data block are processed separately, wherein the data block is preferably fixed to a specific size, and the position of each data block is checked, and the specific size is the minimum unit of the changed data block, and there are the following four situations: (1) In response to the data block being only in the changed data block of the previous backup point, the corresponding data of the previous backup point is read and saved into the data file of the current backup point, and the changed data block information is recorded at the current backup point; Specifically, at this time, this block of data is not in the data change block of the current backup point, that is, no change occurs in the time period from the last backup to the current backup.

[0032] (2) In response to the data block being only in the changed data block of the current backup point, the empty data is written into the reverse incremental data file of the previous backup point, and the changed data block information is recorded at the previous backup point; the corresponding position data of the data block is read from the source virtual machine, saved to the virtual machine data file of the current backup point, and the changed data block information is recorded at the current backup point; Specifically, at this time, the data block is not in the last backup point, and is a newly added data block. Because the changed data block information records the location and length of the data block, the real data still needs to be read from the disk of the source virtual machine and saved and recorded.

[0033] (3) In response to a data block being in the changed data block of both the previous backup point and the current backup point, the data corresponding to the data block at the previous backup point is read, written to the reverse incremental data file at the previous backup point, and the changed data block information is recorded at the previous backup point; the data corresponding to the position of the data block is read from the source virtual machine data block, written to the virtual machine data file at the current backup point, and the changed data block information is recorded at the current backup point; Specifically, at this time, this piece of data has changed in the last backup and was recorded. It has changed again in the current backup and needs to be recorded again.

[0034] If the data block is not in the changed data block information of the previous backup point or the current backup point, it will not be processed.

[0035] Further, see Appendix Figure 3 The changed data block information records the data block information of each virtual machine disk, including the location and size of the data block in the virtual machine disk. The changed data block information is divided into full changed data blocks and incremental changed data blocks according to the backup type.

[0036] As attached Figure 2 , Attachment Figure 4 As shown, the present invention also discloses a reverse incremental backup device of a virtual machine's own data format, comprising: The changed data block information reading module 100 is used to read the changed data block information in the most recent backup point in response to obtaining the most recent backup point; The incremental change data block information acquisition module 200 is used to acquire the incremental change data block information of the current backup; A data file creation module 300 is used to create a virtual machine data file at the current backup point to store virtual machine data, and to create a reverse incremental data file at the previous backup point to store reverse incremental data; The data block check processing module 400 is used to check the position and size of each data block from position 0 to the end of the virtual machine disk, and process them respectively according to the check results; The data block splicing module 500 is used to check the changed data block information recorded at the previous backup point and the current backup point respectively, and if there are data blocks that are connected in position, splice them; The changed data block information saving module 600 is used to save the changed data block information recorded at the previous backup point and the current backup point to the corresponding backup points respectively; The full data file deletion module 700 is used to delete the old full data file at the previous backup point. The reverse incremental data has been saved in the reverse incremental data file of the previous backup node.

[0037] Specifically, to perform a reverse incremental backup, you need to first do a full backup and one or several reverse incremental backups. If the most recent backup point is not obtained, it means that the first full backup has not been performed. In addition, to obtain the incremental change data block information of the current backup, that is, to obtain the incremental data of the virtual machine, there are different methods depending on the platform. VMware and Hyper-V (Windows 2016 and later versions) provide public interface call implementations. Most other platforms must independently implement the method of obtaining the change block, which belongs to the prior art and will not be repeated here. In this implementation scheme, the data of a disk file of the virtual machine is processed, and the virtual machine may have more than one disk file. For multiple disk files, the process is consistent.

[0038] Furthermore, the device also includes a full backup module, which is used to obtain the most recent backup point. If the most recent backup point is not obtained, a full backup is performed uniformly regardless of which backup type is specified. The backup types include full backup and reverse incremental backup.

[0039] Specifically, the most recent backup point is obtained. If it is not obtained, a full backup is performed regardless of the specified backup type (full or reverse incremental). If the most recent backup point is obtained, the changed data block information file in the backup point (full backup or reverse incremental backup) is read. The changed data block information file is a full changed data block information file or an incremental changed data block information file.

[0040] Further in a preferred embodiment of the present invention, the data block check processing module 400 is specifically used to check the position and size of each data block from position 0 to the end of the virtual machine disk, and process them separately, wherein the data block is preferably fixed to a specific size, and the position of each data block is checked. The specific size is the minimum unit of the changed data block, and there are the following four situations: (1) In response to the data block being only in the changed data block of the previous backup point, the corresponding data of the previous backup point is read and saved into the data file of the current backup point, and the changed data block information is recorded at the current backup point; Specifically, at this time, this block of data is not in the data change block of the current backup point, that is, no change occurs in the time period from the last backup to the current backup.

[0041] (2) In response to the data block being only in the changed data block of the current backup point, the empty data is written into the reverse incremental data file of the previous backup point, and the changed data block information is recorded at the previous backup point; the corresponding position data of the data block is read from the source virtual machine, saved to the virtual machine data file of the current backup point, and the changed data block information is recorded at the current backup point; Specifically, at this time, the data block is not in the last backup point, and is a newly added data block. Because the changed data block information records the location and length of the data block, the real data still needs to be read from the disk of the source virtual machine and saved and recorded.

[0042] (3) In response to a data block being in the changed data block of both the previous backup point and the current backup point, the data corresponding to the data block at the previous backup point is read, written to the reverse incremental data file at the previous backup point, and the changed data block information is recorded at the previous backup point; the data corresponding to the position of the data block is read from the source virtual machine data block, written to the virtual machine data file at the current backup point, and the changed data block information is recorded at the current backup point; Specifically, at this time, this piece of data has changed in the last backup and was recorded. It has changed again in the current backup and needs to be recorded again.

[0043] If the data block is not in the changed data block information of the previous backup point or the current backup point, it will not be processed.

[0044] Furthermore, the changed data block information records the data block information of each virtual machine disk, including the location and size of the data block in the virtual machine disk; the changed data block information is divided into full changed data blocks and incremental changed data blocks according to different backup types.

[0045] It should be noted that this device corresponds to the backup method. For other undescribed parts, please refer to the contents of the above method and will not be repeated here.

[0046] The present invention also discloses a computer-readable storage medium, wherein the computer-executable instructions are used to execute one or a combination of the steps of the above method embodiments when executed by a computer processor.

[0047] The computer storage medium of the embodiment of the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. Examples of computer-readable storage media include, but are not limited to, electrical, optical, magnetic, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples of computer-readable storage media include, but are not limited to: an electrical connection with one or more wirings, a portable computer disk box, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical fiber, an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device or device.

[0048] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program codes. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, device, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0049] Computer program code for performing the operation of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0050] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Any person skilled in the art may modify and alter the above embodiments without violating the spirit and scope of the present invention. Therefore, the scope of protection of the present invention shall be as set forth in the claims.

Claims

1. A method for reverse incremental backup of a virtual machine's own data format, comprising the following steps: In response to obtaining the most recent backup point, reading the changed data block information in the most recent backup point; Get the incremental change data block information of the current backup; A new virtual machine data file is created at the current backup point to store virtual machine data, and a new reverse incremental data file is created at the previous backup point to store reverse incremental data; Check the location and size of each data block from position 0 to the end of the virtual machine disk, and process them separately according to the inspection results; Check the changed data block information recorded at the previous backup point and the current backup point respectively. If there are data blocks that are connected in position, they will be spliced; The changed data block information recorded at the previous backup point and the current backup point is saved to the corresponding backup points respectively; Delete the old full data file on the previous backup point. The reverse incremental data has been saved in the reverse incremental data file of the previous backup node.

2. A method for reverse incremental backup of a virtual machine's own data format as claimed in claim 1, characterized in that: The checking of the position and size of each data block includes: The data blocks are fixedly configured to a specific size, and the position of each data block is checked; the specific size is the minimum unit of the changed data block.

3. A method for reverse incremental backup of a virtual machine's own data format as claimed in claim 2, characterized in that: The process of checking the position and size of each data block from position 0 to the end of the virtual machine disk and processing them respectively according to the checking results includes the following steps: In response to the data block being only in the changed data block of the previous backup point, the data of the previous backup point is read and saved into the data file of the current backup point, and the changed data block information is recorded at the current backup point; In response to the data block being only in the changed data block of the current backup point, the empty data is written into the reverse incremental data file of the previous backup point, and the changed data block information is recorded at the previous backup point; Read the corresponding position data of the data block from the source virtual machine, save it to the virtual machine data file of the current backup point, and record the changed data block information at the current backup point; In response to the data block being in the changed data block of both the previous backup point and the current backup point, the data corresponding to the data block at the previous backup point is read, written to the reverse incremental data file of the previous backup point, and the changed data block information is recorded at the previous backup point; Read the corresponding position data of the data block from the source virtual machine data block, write it to the virtual machine data file of the current backup point, and record the changed data block information at the current backup point; In response to the data block not being in the changed data block information of either the previous backup point or the current backup point, no processing is performed.

4. A method for reverse incremental backup of a virtual machine's own data format as claimed in claim 1, characterized in that: Before the response to obtaining the most recent backup point and reading the changed data block information in the most recent backup point, the following steps are also included: The most recent backup point is obtained. If the most recent backup point is not obtained, a full backup is performed uniformly regardless of the backup type specified. The backup types include full backup and reverse incremental backup.

5. A method for reverse incremental backup of a virtual machine's own data format as claimed in claim 1, characterized in that: The changed data block information records the data block information of each virtual machine disk, including the location and size of the data block in the virtual machine disk.

6. A method for reverse incremental backup of a virtual machine's own data format as claimed in claim 1, characterized in that: The changed data block information is divided into full changed data blocks and incremental changed data blocks according to different backup types.

7. A reverse incremental backup device of a virtual machine's own data format, comprising: A changed data block information reading module, configured to read the changed data block information in the most recent backup point in response to obtaining the most recent backup point; The incremental change data block information acquisition module is used to obtain the incremental change data block information of the current backup; A data file creation module is used to create a virtual machine data file at the current backup point to store virtual machine data, and to create a reverse incremental data file at the previous backup point to store reverse incremental data; The data block check processing module is used to check the position and size of each data block from the 0 position to the end of the virtual machine disk, and process them separately according to the check results; The data block splicing module is used to check the changed data block information recorded at the previous backup point and the current backup point respectively, and if there are data blocks that are connected in position, they are spliced; The changed data block information saving module is used to save the changed data block information recorded at the previous backup point and the current backup point to the corresponding backup points respectively; The full data file deletion module is used to delete the old full data file at the previous backup point. The reverse incremental data has been saved in the reverse incremental data file of the previous backup node.

8. A virtual machine's own data format reverse incremental backup device as claimed in claim 7, characterized in that: The data block inspection processing module is specifically used for: In response to the data block being only in the changed data block of the previous backup point, the corresponding data of the previous backup point is read and saved into the data file of the current backup point, and the changed data block information is recorded at the current backup point; In response to the data block being only in the changed data block of the current backup point, the empty data is written into the reverse incremental data file of the previous backup point, and the changed data block information is recorded at the previous backup point; Read the corresponding position data of the data block from the source virtual machine, save it to the virtual machine data file of the current backup point, and record the changed data block information at the current backup point; In response to the data block being in the changed data block of both the previous backup point and the current backup point, the data corresponding to the data block at the previous backup point is read, written to the reverse incremental data file of the previous backup point, and the changed data block information is recorded at the previous backup point; Read the corresponding position data of the data block from the source virtual machine data block, write it to the virtual machine data file of the current backup point, and record the changed data block information at the current backup point; In response to the data block not being in the changed data block information of either the previous backup point or the current backup point, no processing is performed.

9. A virtual machine's own data format reverse incremental backup device as claimed in claim 8, characterized in that: The device also includes a full backup module for obtaining the most recent backup point. If the most recent backup point is not obtained, a full backup is performed uniformly regardless of which backup type is specified. The backup types include full backup and reverse incremental backup.

10. A computer-readable storage medium storing a computer program, wherein the computer program is used to execute a method for reverse incremental backup of a virtual machine's own data format as described in any one of claims 1 to 6.

Images