Data static recovery method, device, equipment and readable storage medium

Abstract

The present invention provides a method, device, equipment and readable storage medium for static data recovery. The method includes: the VOI underlying client creates a first incremental file and a second incremental file respectively, and mounts the first incremental file as an updated operating system boot disk, and mounts the second incremental file as a static system disk; the data recovery module of the updated operating system reads the to-be-recovered mark of the VOI disk metadata area; if the to-be-recovered mark of the VOI disk metadata area is 1, the registry key value and system file in the hierarchical protection space are synchronized to the second incremental file mounted as a static system disk. Through the present invention, the problem of incomplete contents of the registry key value and / or system file causing abnormality of the updated operating system is avoided during the process of synchronizing the registry key value and system file for data recovery during the operation of the updated operating system.

Description

Technical Field

[0001] The present invention relates to the field of desktop cloud technology, and in particular to a data static recovery method, device, equipment and readable storage medium. Background Art

[0002] In an operating system with Windows image layering enabled, after the operating system update is completed, the registry key values ​​and system files in the layered protection space need to be synchronized to the updated operating system for data recovery. However, in the process of synchronizing the registry key values ​​and system files in the layered protection space to the updated operating system for data recovery, since the updated operating system is constantly changing during operation, the registry key values ​​and system files will also change at any time. If the data of the registry key values ​​and system files are restored during the change process, there is a certain probability that the contents of the registry key values ​​and / or system files will be incomplete, resulting in some system function abnormalities. Summary of the invention

[0003] The main purpose of the present invention is to provide a data static recovery method, device, equipment and readable storage medium, aiming to solve the problem that data incompleteness may occur during data recovery of registry key values ​​and system files during the operation of an updated operating system, resulting in abnormalities in the updated operating system.

[0004] In a first aspect, the present invention provides a static data recovery method, the static data recovery method comprising:

[0005] After the operating system update is completed, the VOI underlying client creates a first incremental file and a second incremental file based on the system image file in the qcow2 format of the updated operating system, respectively, and mounts the first incremental file as the updated operating system boot disk, and mounts the second incremental file as a static system disk, wherein the first incremental file and the second incremental file are differential image files with the same root;

[0006] The updated operating system is started based on the first incremental file mounted as the updated operating system startup disk. After the updated operating system is started, the data recovery module of the updated operating system reads the to-be-recovered mark of the metadata area of ​​the VOI disk;

[0007] If the to-be-restored flag of the VOI disk metadata area is 1, the data recovery module of the updated operating system synchronizes the registry key values ​​and system files in the layered protection space to the second incremental file mounted as a static system disk.

[0008] Optionally, the static data recovery method further includes:

[0009] When the operating system update is completed, the VOI underlying client sets the pending recovery flag of the VOI disk metadata area to 1.

[0010] Optionally, after the step of reading the to-be-restored mark in the metadata area of ​​the VOI disk, the method further includes:

[0011] If the to-be-restored flag of the VOI disk metadata area is 0, no processing is performed.

[0012] Optionally, after the step of synchronizing the registry key value and the system file in the hierarchical protection space to the virtual disk corresponding to the second incremental file, the method further includes:

[0013] The VOI bottom-level client reads the recovery completion mark of the VOI disk metadata area;

[0014] If the recovery completion flag of the VOI disk metadata area is 0, no processing is performed;

[0015] If the recovery completion mark of the VOI disk metadata area is 1, the VOI underlying client deletes the first incremental file, mounts the second incremental file as the updated operating system boot disk, and sets the recovery completion mark of the VOI disk metadata area to 0.

[0016] Optionally, after the step of synchronizing the registry key value and the system file in the hierarchical protection space to the virtual disk corresponding to the second incremental file, the method further includes:

[0017] After detecting that the synchronization is completed, the data recovery module of the updated operating system sets the to-be-recovered flag of the VOI disk metadata area to 0, and sets the recovery completion flag of the VOI disk metadata area to 1.

[0018] In a second aspect, the present invention further provides a data static recovery system, the data static recovery system comprising a data recovery module of an updated operating system and a VOI underlying client, wherein:

[0019] The VOI underlying client is used to create a first incremental file and a second incremental file based on the system image file of the updated operating system in the qcow2 format after the operating system is updated, and mount the first incremental file as the updated operating system boot disk and the second incremental file as the static system disk, wherein the first incremental file and the second incremental file are differential image files with the same root;

[0020] A data recovery module for the updated operating system, used for starting the updated operating system based on the first incremental file mounted as the startup disk of the updated operating system, after the updated operating system is started, the data recovery module for the updated operating system reads the to-be-recovered mark of the metadata area of ​​the VOI disk;

[0021] The data recovery module of the updated operating system is used to synchronize the registry key values ​​and system files in the layered protection space to the second incremental file mounted as a static system disk if the to-be-recovered mark of the VOI disk metadata area is 1.

[0022] Furthermore, in one embodiment, the VOI underlying client is also used for:

[0023] The VOI bottom-level client reads the recovery completion mark of the VOI disk metadata area;

[0024] If the recovery completion flag of the VOI disk metadata area is 0, no processing is performed;

[0025] If the recovery completion mark of the VOI disk metadata area is 1, the VOI underlying client deletes the first incremental file, mounts the second incremental file as the updated operating system boot disk, and sets the recovery completion mark of the VOI disk metadata area to 0.

[0026] Furthermore, in one embodiment, the data recovery module of the updated operating system is further used to:

[0027] After detecting that the synchronization is completed, the data recovery module of the updated operating system sets the to-be-recovered flag of the VOI disk metadata area to 0, and sets the recovery completion flag of the VOI disk metadata area to 1.

[0028] In a third aspect, the present invention also provides a data static recovery device, which includes a processor, a memory, and a data static recovery program stored in the memory and executable by the processor, wherein when the data static recovery program is executed by the processor, the steps of the data static recovery method as described above are implemented.

[0029] In a fourth aspect, the present invention further provides a readable storage medium, on which a data static recovery program is stored, wherein when the data static recovery program is executed by a processor, the steps of the data static recovery method as described above are implemented.

[0030] In the present invention, after the operating system update is completed, the VOI underlying client creates a first incremental file and a second incremental file respectively based on the system image file in the qcow2 format of the updated operating system, and mounts the first incremental file as the updated operating system startup disk, and mounts the second incremental file as the static system disk, wherein the first incremental file and the second incremental file are differential image files with the same root; the updated operating system is started based on the first incremental file mounted as the updated operating system startup disk, and after the updated operating system is started, the data recovery module of the updated operating system reads the to-be-restored mark of the VOI disk metadata area; if the to-be-restored mark of the VOI disk metadata area is 1, the data recovery module of the updated operating system synchronizes the registry key values ​​and system files in the hierarchical protection space to the second incremental file mounted as the static system disk. Through the present invention, after the operating system update is completed, the VOI underlying client creates a first incremental file and a second incremental file respectively, and the VOI underlying client mounts the first incremental file as an updated operating system startup disk, so that the updated operating system can be started based on the first incremental file mounted as the updated operating system startup disk, and mounts the second incremental file as a static system disk, so that when the data recovery module of the updated operating system reads the to-be-recovered mark of the VOI disk metadata area as 1, the data recovery module of the updated operating system synchronizes the registry key value and system file in the hierarchical protection space to the second incremental file mounted as the static system disk, thereby avoiding the problem that the contents of the registry key value and / or system file are incomplete during the process of synchronizing the registry key value and system file for data recovery during the operation of the updated operating system, resulting in abnormality of the updated operating system. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A schematic diagram of the hardware structure of a static data recovery device involved in an embodiment of the present invention;

[0032] Figure 2 A schematic diagram of a flow chart of an embodiment of a static data recovery method of the present invention;

[0033] Figure 3 It is a schematic diagram of the functional modules of an embodiment of a static data recovery system of the present invention.

[0034] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0035] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0036] In a first aspect, an embodiment of the present invention provides a static data recovery device, which may be a device having a data processing function, such as a personal computer (PC), a notebook computer, or a server.

[0037] Reference Figure 1 , Figure 1 The hardware structure diagram of the data static recovery device involved in the embodiment of the present invention. In the embodiment of the present invention, the data static recovery device may include a processor 1001 (such as a central processing unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components; the user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard); the network interface 1004 may optionally include a standard wired interface, a wireless interface (such as a wireless fidelity WIreless-FIdelity, WI-FI interface); the memory 1005 may be a high-speed random access memory (random access memory, RAM), or a stable memory (non-volatile memory), such as a disk storage, and the memory 1005 may optionally be a storage device independent of the aforementioned processor 1001. Those skilled in the art will understand that Figure 1 The hardware structure shown in the figure does not constitute a limitation of the present invention, and may include more or less components than those shown in the figure, or combine certain components, or arrange the components differently.

[0038] Continue to refer to Figure 1 , Figure 1 The memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a data static recovery program. The processor 1001 may call the data static recovery program stored in the memory 1005 and execute the data static recovery method provided in the embodiment of the present invention.

[0039] In a second aspect, an embodiment of the present invention provides a method for static data recovery.

[0040] In one embodiment, referring to Figure 2 , Figure 2 FIG. 1 is a flow chart of an embodiment of a static data recovery method of the present invention. Figure 2 As shown, the static data recovery method includes:

[0041] Step S10, after the operating system update is completed, the VOI underlying client creates a first incremental file and a second incremental file based on the system image file in the qcow2 format of the updated operating system, and mounts the first incremental file as the updated operating system boot disk, and mounts the second incremental file as a static system disk, wherein the first incremental file and the second incremental file are differential image files with the same root;

[0042] In this embodiment, after the operating system is updated, the VOI underlying client creates a first incremental file and a second incremental file based on the system image file of the updated operating system in the qcow2 format, wherein the first incremental file and the second incremental file are differential image files with the same root. Through the windos virtual disk technology, the VOI underlying client mounts the first incremental file as the updated operating system boot disk and mounts the second incremental file as a static system disk.

[0043] Step S20, the updated operating system is started based on the first incremental file mounted as the updated operating system startup disk. After the updated operating system is started, the data recovery module of the updated operating system reads the to-be-recovered mark in the metadata area of ​​the VOI disk;

[0044] In this embodiment, the updated operating system is started based on the first incremental file mounted as the updated operating system startup disk. After the updated operating system is started, the updated operating system loads the data recovery module, and the data recovery module of the updated operating system reads the to-be-recovered mark in the VOI disk metadata area.

[0045] Step S30, if the to-be-restored mark of the VOI disk metadata area is 1, the data recovery module of the updated operating system synchronizes the registry key values ​​and system files in the hierarchical protection space to the second incremental file mounted as a static system disk.

[0046] In this embodiment, the to-be-restored mark of the VOI disk metadata area read in step S20 is detected. If the detection result is that the to-be-restored mark of the VOI disk metadata area is 1, the data recovery module of the updated operating system synchronizes the registry key values ​​and system files in the layered protection space to the second incremental file mounted as a static system disk, thereby avoiding the situation where the updated operating system is constantly changing during operation, causing the registry key values ​​and system files to change at any time, thereby ensuring the integrity of the contents of the registry key values ​​and / or system files during the process of the data recovery module synchronizing the registry key values ​​and system files in the layered protection space to the second incremental file mounted as a static system disk for data recovery.

[0047] In this embodiment, after the operating system update is completed, the VOI underlying client creates a first incremental file and a second incremental file respectively based on the system image file in the qcow2 format of the updated operating system, and mounts the first incremental file as the updated operating system boot disk, and mounts the second incremental file as a static system disk, wherein the first incremental file and the second incremental file are differential image files with the same root; the updated operating system is started based on the first incremental file mounted as the updated operating system boot disk, and after the updated operating system is started, the data recovery module of the updated operating system reads the to-be-restored mark of the VOI disk metadata area; if the to-be-restored mark of the VOI disk metadata area is 1, the data recovery module of the updated operating system synchronizes the registry key values ​​and system files in the hierarchical protection space to the second incremental file mounted as the static system disk. Through this embodiment, after the operating system update is completed, the VOI underlying client creates a first incremental file and a second incremental file respectively, and the VOI underlying client mounts the first incremental file as an updated operating system startup disk for the updated operating system to start based on the first incremental file mounted as the updated operating system startup disk, and mounts the second incremental file as a static system disk for the updated operating system. When the to-be-recovered mark of the VOI disk metadata area read by the data recovery module of the updated operating system is 1, the data recovery module of the updated operating system synchronizes the registry key values ​​and system files in the hierarchical protection space to the second incremental file mounted as the static system disk, thereby avoiding the problem of incomplete contents of the registry key values ​​and / or system files during the process of synchronizing the registry key values ​​and system files for data recovery during the operation of the updated operating system, resulting in abnormalities in the updated operating system.

[0048] Furthermore, in one embodiment, the static data recovery method further includes:

[0049] When the operating system update is completed, the VOI underlying client sets the pending recovery flag of the VOI disk metadata area to 1.

[0050] In this embodiment, when the operating system update is completed, the VOI underlying client sets the to-be-restored mark of the VOI disk metadata area to 1, so that the data recovery module of the updated operating system reads the to-be-restored mark of the VOI disk metadata area, and then executes the step of synchronizing the registry key values ​​and system files in the hierarchical protection space to the virtual disk corresponding to the second incremental file.

[0051] Furthermore, in one embodiment, after the step of reading the to-be-restored mark in the metadata area of ​​the VOI disk, the method further includes:

[0052] If the to-be-restored flag of the VOI disk metadata area is 0, no processing is performed.

[0053] In this embodiment, the to-be-restored mark of the VOI disk metadata area read in step S20 is checked. If the detection result is that the to-be-restored mark of the VOI disk metadata area is 0, it means that the updated operating system has completed the step of synchronizing the registry key values ​​and system files in the layered protection space to the virtual disk corresponding to the second incremental file. Therefore, if the to-be-restored mark of the VOI disk metadata area is 0, no processing is performed.

[0054] Furthermore, in one embodiment, after the step of synchronizing the registry key value and the system file in the hierarchical protection space to the virtual disk corresponding to the second incremental file, the method further includes:

[0055] The VOI bottom-level client reads the recovery completion mark of the VOI disk metadata area;

[0056] If the recovery completion flag of the VOI disk metadata area is 0, no processing is performed;

[0057] If the recovery completion mark of the VOI disk metadata area is 1, the VOI underlying client deletes the first incremental file, mounts the second incremental file as the updated operating system boot disk, and sets the recovery completion mark of the VOI disk metadata area to 0.

[0058] In this embodiment, the VOI bottom layer client reads the recovery completion mark of the VOI disk metadata area, and detects the read recovery completion mark of the VOI disk metadata area.

[0059] If the detection result is that the recovery completion mark of the VOI disk metadata area is 0, it means that the data recovery module of the updated operating system has not yet set the recovery completion mark of the VOI disk metadata area to 1, that is, the data recovery module of the updated operating system has not yet completed the step of synchronizing the registry key values ​​and system files in the layered protection space to the virtual disk corresponding to the second incremental file, or the VOI underlying client has completed the step of deleting the first incremental file and mounting the second incremental file as the updated operating system boot disk. Therefore, if the recovery completion mark of the VOI disk metadata area is 0, no processing will be performed.

[0060] If the detection result is that the recovery completion mark of the VOI disk metadata area is 1, it means that the data recovery module of the updated operating system has completed the step of synchronizing the registry key value and system file in the layered protection space to the virtual disk corresponding to the second incremental file, then the VOI underlying client deletes the first incremental file and mounts the second incremental file as the updated operating system startup disk, so that the updated operating system can be started based on the second incremental file mounted as the updated operating system startup disk. Further, the VOI underlying client sets the recovery completion mark of the VOI disk metadata area to 0 to avoid repeating the step of the VOI underlying client deleting the first incremental file and mounting the second incremental file as the updated operating system startup disk.

[0061] Furthermore, in one embodiment, after the step of synchronizing the registry key value and the system file in the hierarchical protection space to the virtual disk corresponding to the second incremental file, the method further includes:

[0062] After detecting that the synchronization is completed, the data recovery module of the updated operating system sets the to-be-recovered flag of the VOI disk metadata area to 0, and sets the recovery completion flag of the VOI disk metadata area to 1.

[0063] In this embodiment, after detecting that the process of synchronizing the registry key values ​​and system files in the hierarchical protection space to the virtual disk corresponding to the second incremental file is completed, the data recovery module of the updated operating system sets the pending recovery mark of the VOI disk metadata area to 0 and the recovery completion mark of the VOI disk metadata area to 1. The pending recovery mark of the VOI disk metadata area is set to 0 to avoid repeating the step of synchronizing the registry key values ​​and system files in the hierarchical protection space to the virtual disk corresponding to the second incremental file. The recovery completion mark of the VOI disk metadata area is set to 1 so that the VOI underlying client can read the recovery completion mark of the VOI disk metadata area, and then execute the steps of deleting the first incremental file and mounting the second incremental file as the boot disk of the updated operating system.

[0064] In a third aspect, an embodiment of the present invention further provides a data static recovery system.

[0065] In one embodiment, referring to Figure 3 , Figure 3 FIG. 1 is a schematic diagram of the functional modules of an embodiment of a static data recovery system of the present invention. Figure 3 As shown, the data static recovery system includes a data recovery module of an updated operating system and a VOI underlying client, wherein:

[0066] The VOI underlying client 10 is used for, after the operating system is updated, the VOI underlying client creates a first incremental file and a second incremental file based on the system image file of the updated operating system in the qcow2 format, respectively, and mounts the first incremental file as the updated operating system boot disk, and mounts the second incremental file as a static system disk, wherein the first incremental file and the second incremental file are differential image files with the same root;

[0067] The updated operating system data recovery module 20 is used for the updated operating system to start up based on the first incremental file mounted as the updated operating system startup disk. After the updated operating system is started up, the updated operating system data recovery module reads the to-be-restored mark of the VOI disk metadata area;

[0068] The data recovery module 20 of the updated operating system is used to synchronize the registry key values ​​and system files in the hierarchical protection space to the second incremental file mounted as a static system disk if the to-be-recovered mark of the VOI disk metadata area is 1.

[0069] Furthermore, in one embodiment, the VOI underlying client 10 is further used for:

[0070] When the operating system update is completed, the VOI underlying client sets the pending recovery flag of the VOI disk metadata area to 1.

[0071] Furthermore, in one embodiment, if the to-be-restored flag of the VOI disk metadata area is 0, no processing is performed.

[0072] Furthermore, in one embodiment, the VOI underlying client 10 is further used for:

[0073] The VOI bottom-level client reads the recovery completion mark of the VOI disk metadata area;

[0074] If the recovery completion flag of the VOI disk metadata area is 0, no processing is performed;

[0075] If the recovery completion mark of the VOI disk metadata area is 1, the VOI underlying client deletes the first incremental file, mounts the second incremental file as the updated operating system boot disk, and sets the recovery completion mark of the VOI disk metadata area to 0.

[0076] Furthermore, in one embodiment, the data recovery module 20 of the updated operating system is further used to:

[0077] After detecting that the synchronization is completed, the data recovery module of the updated operating system sets the to-be-recovered flag of the VOI disk metadata area to 0, and sets the recovery completion flag of the VOI disk metadata area to 1.

[0078] Among them, the specific embodiment of the above-mentioned data static recovery system corresponds to the steps in the above-mentioned data static recovery method embodiment, and its functions and implementation processes are no longer repeated here.

[0079] In a fourth aspect, an embodiment of the present invention further provides a readable storage medium.

[0080] The readable storage medium of the present invention stores a data static recovery program, wherein when the data static recovery program is executed by a processor, the steps of the data static recovery method described above are implemented.

[0081] Among them, the method implemented when the data static recovery program is executed can refer to the various embodiments of the data static recovery method of the present invention, and will not be repeated here.

[0082] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0083] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0084] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present invention.

[0085] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A static data recovery method, characterized in that: The method is used to synchronize the registry key values ​​and system files in the layered protection space to the updated operating system for data recovery after the operating system update is completed in an operating system with Windows image layering enabled, and the static data recovery method includes: After the operating system update is completed, the VOI underlying client creates a first incremental file and a second incremental file based on the system image file in the qcow2 format of the updated operating system, respectively, and mounts the first incremental file as the updated operating system boot disk, and mounts the second incremental file as a static system disk, wherein the first incremental file and the second incremental file are differential image files with the same root; The updated operating system is started based on the first incremental file mounted as the updated operating system startup disk. After the updated operating system is started, the data recovery module of the updated operating system reads the to-be-recovered mark of the metadata area of ​​the VOI disk; If the to-be-restored flag of the VOI disk metadata area is 1, the data recovery module of the updated operating system synchronizes the registry key values ​​and system files in the layered protection space to the second incremental file mounted as a static system disk; The static data recovery method also includes: When the operating system update is completed, the VOI underlying client sets the pending recovery flag of the VOI disk metadata area to 1; After the step of synchronizing the registry key value and the system file in the hierarchical protection space to the virtual disk corresponding to the second incremental file, the method further includes: The VOI bottom-level client reads the recovery completion mark of the VOI disk metadata area; If the recovery completion flag of the VOI disk metadata area is 0, no processing is performed; If the recovery completion mark of the VOI disk metadata area is 1, the VOI underlying client deletes the first incremental file, mounts the second incremental file as the updated operating system boot disk, and sets the recovery completion mark of the VOI disk metadata area to 0.

2. The static data recovery method according to claim 1, characterized in that: After the step of reading the to-be-restored mark in the metadata area of ​​the VOI disk, the method further includes: If the to-be-restored flag of the VOI disk metadata area is 0, no processing is performed.

3. The static data recovery method according to claim 1, characterized in that: After the step of synchronizing the registry key value and the system file in the hierarchical protection space to the virtual disk corresponding to the second incremental file, the method further includes: After detecting that the synchronization is completed, the data recovery module of the updated operating system sets the to-be-recovered flag of the VOI disk metadata area to 0, and sets the recovery completion flag of the VOI disk metadata area to 1.

4. A data static recovery system, characterized in that: The system is used to synchronize the registry key values ​​and system files in the layered protection space to the updated operating system for data recovery after the operating system update is completed in an operating system with Windows image layering enabled, wherein the static data recovery system includes a data recovery module of the updated operating system and a VOI underlying client, wherein: The VOI underlying client is used to create a first incremental file and a second incremental file based on the system image file of the updated operating system in the qcow2 format after the operating system is updated, and mount the first incremental file as the updated operating system boot disk and the second incremental file as the static system disk, wherein the first incremental file and the second incremental file are differential image files with the same root; A data recovery module for the updated operating system, used for starting the updated operating system based on the first incremental file mounted as the startup disk of the updated operating system, after the updated operating system is started, the data recovery module for the updated operating system reads the to-be-recovered mark of the metadata area of ​​the VOI disk; The data recovery module of the updated operating system is used to synchronize the registry key values ​​and system files in the hierarchical protection space to the second incremental file mounted as a static system disk if the to-be-recovered flag of the VOI disk metadata area is 1; When the operating system update is completed, the VOI underlying client sets the pending recovery flag of the VOI disk metadata area to 1; The VOI underlying client is also used for: The VOI bottom-level client reads the recovery completion mark of the VOI disk metadata area; If the recovery completion flag of the VOI disk metadata area is 0, no processing is performed; If the recovery completion mark of the VOI disk metadata area is 1, the VOI underlying client deletes the first incremental file, mounts the second incremental file as the updated operating system boot disk, and sets the recovery completion mark of the VOI disk metadata area to 0.

5. The data static recovery system according to claim 4, characterized in that: The data recovery module of the updated operating system is further used for: After detecting that the synchronization is completed, the data recovery module of the updated operating system sets the to-be-recovered flag of the VOI disk metadata area to 0, and sets the recovery completion flag of the VOI disk metadata area to 1.

6. A static data recovery device, characterized in that: The data static recovery device includes a processor, a memory, and a data static recovery program stored in the memory and executable by the processor, wherein when the data static recovery program is executed by the processor, the steps of the data static recovery method as described in any one of claims 1 to 3 are implemented.

7. A readable storage medium, characterized in that: The readable storage medium stores a data static recovery program, wherein when the data static recovery program is executed by a processor, the steps of the data static recovery method according to any one of claims 1 to 3 are implemented.

Images