CN117349086B - Permanent incremental backup method for Windows complete machine - Google Patents
Permanent incremental backup method for Windows complete machine Download PDFInfo
- Publication number
- CN117349086B CN117349086B CN202311644041.XA CN202311644041A CN117349086B CN 117349086 B CN117349086 B CN 117349086B CN 202311644041 A CN202311644041 A CN 202311644041A CN 117349086 B CN117349086 B CN 117349086B
- Authority
- CN
- China
- Prior art keywords
- disk
- partition
- data
- backup
- snapshot
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000005192 partition Methods 0.000 claims abstract description 145
- 238000012937 correction Methods 0.000 claims abstract description 16
- 230000007717 exclusion Effects 0.000 claims abstract description 14
- 230000005540 biological transmission Effects 0.000 claims abstract description 13
- 238000013507 mapping Methods 0.000 claims abstract description 13
- 230000026676 system process Effects 0.000 claims abstract description 4
- 238000011084 recovery Methods 0.000 claims description 6
- 230000008602 contraction Effects 0.000 claims description 4
- 238000013075 data extraction Methods 0.000 claims description 4
- 238000012546 transfer Methods 0.000 claims description 4
- 101000648827 Homo sapiens TPR and ankyrin repeat-containing protein 1 Proteins 0.000 claims description 3
- 102100028173 TPR and ankyrin repeat-containing protein 1 Human genes 0.000 claims description 3
- 230000001681 protective effect Effects 0.000 claims description 3
- 238000000638 solvent extraction Methods 0.000 claims description 3
- 230000000694 effects Effects 0.000 abstract description 5
- 230000000875 corresponding effect Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000007792 addition Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 206010033799 Paralysis Diseases 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000035515 penetration Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1453—Management of the data involved in backup or backup restore using de-duplication of the data
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application discloses a method for permanently and incrementally backing up a whole Windows machine, which comprises the following steps: s1: the target Windows system issues a backup instruction; s2: after receiving the backup instruction, distributing a system process-level mutual exclusion lock; s3: initializing a snapshot directory after initializing the mutual exclusion lock; s4: collecting physical disk group data; s5: the backup all-in-one machine traverses the effective partition data in the physical disk group data and executes data correction and backup mode marking operation; s6: creating file resources and mapping resources of the virtual disk according to the physical disk group data and the backup mode mark; s7: the target Windows system executes data stream transmission logic; s8: after the backup is completed, releasing the resource handle to form a whole machine snapshot; s9: S1-S8 are repeated, correction and merging are carried out on the whole machine snapshot chain, and the implementation effect of the permanent incremental backup is not only limited to the disk environment in the first backup, and the subsequent backup disk changes do not need to recreate the configuration backup plan.
Description
Technical Field
The invention belongs to the technical field of computer data backup, and particularly relates to a method for permanent incremental backup of a Windows complete machine.
Background
Today, where enterprise data grows exponentially, an operating system carrying the enterprise data faces the risk of data loss caused by paralysis due to network penetration, lux attacks, software and hardware faults and the like, and pre-backup becomes one of the best means for passively defending the foregoing problems.
However, under the existing most Windows backup schemes, only full-volume backup of the system is performed, any full-volume backup point is selected for restoration during restoration, which is easy to cause problems of storage resource waste, increase in enterprise storage cost and the like, or under the condition of supporting permanent incremental backup, the backup strategy or the schedule cannot be compatible with incremental backup in the scenes of new addition, reduction, modification and the like of the disk and the partition during the effective period.
Disclosure of Invention
In order to solve the problems in the background art, the invention provides a method for permanent incremental backup of a Windows complete machine, which aims to solve the problems in the prior art that storage resource waste is easily caused, the storage cost of enterprises is increased, and the incremental backup cannot be well carried out under the scenes of new addition, reduction, modification and the like of a disk and a partition.
In order to achieve the above purpose, the present invention provides the following technical solutions:
a permanent incremental backup method of a Windows complete machine comprises the following steps:
s1: the integrated backup machine initializes a storage directory of the backup snapshot point and remotely issues a backup instruction to the target Windows system;
s2: after receiving a backup instruction, the target Windows system initializes a backup task session, distributes a system process-level mutual exclusion lock, initializes the mutual exclusion lock, and the backup task session is in the context of the mutual exclusion lock, wherein the mutual exclusion lock is used for ensuring the singleness of the backup task execution;
s3: initializing a snapshot directory after the initialization of the mutual exclusion lock is completed;
s4: the target Windows system collects physical disk group data and sends the physical disk group data to the backup integrated machine, and for each piece of disk data subordinate to the disk group data, the target Windows system contains three key data, namely disk metadata, disk general data and disk effective partition data;
s5: the backup all-in-one machine traverses the effective partition data in the collected physical disk group data, executes data correction and backup mode marking operation, and sends the physical disk group data after the data correction and backup mode marking operation to a target Windows system, wherein the backup mode marking comprises a full quantity marking and an increment marking, and the full quantity marking comprises the following steps:
the disk total mark judgment at least meets the following conditions:
the unique identifier of the disk application layer is not hit from the disk group information of the last historical backup under the strategy; the capacity of the magnetic disk is expanded or contracted; any of the disk partition table type changes;
the incremental mark judgment conditions of the disk are as follows: all the disk total mark judging conditions are not satisfied;
the full flag determination of the partition satisfies at least the condition:
the unique identification of the partition is not hit from the disk group data which is backed up last time in the history under the strategy; partitioning expansion or contraction; partition unique identification change; any of the partition file system changes;
the incremental mark judgment conditions of the partition are: all partition total judgment conditions are not satisfied;
s6: the target Windows system creates virtual disk file resources and mapping resources for the physical disk group according to the physical disk group data and the backup mode mark;
s7: the target Windows system executes data stream transmission logic; transmitting disk metadata to virtual disk equipment according to LBA offset, transmitting all effective partition data under a disk after the disk metadata is transmitted, releasing a locally held block handle resource of the partition after each effective partition is transmitted, archiving a local partition file according to the snapshot catalog after the transmission is finished, releasing mapping resources of a backup integrated machine after each disk is processed, and archiving corresponding virtual disk file resources;
s8: after all the disks of the target Windows system are backed up, the target Windows system releases all local and remote resource handles associated with the task to form a whole machine snapshot;
s9: S1-S8 are repeated to gradually form a whole machine snapshot chain, when the number of nodes on the chain exceeds the number N of reserved snapshot points in the strategy, the current snapshot number is recorded as CN, when CN > N, correction and combination are executed on the whole machine snapshot chain, and the permanent increment of the whole Windows machine is realized along with the periodical execution of backup tasks.
Preferably, the three key data in S4 are specifically expressed as:
disk metadata: if the data is a GPT disk, the disk metadata is primary GPT data and secondary GPT data, wherein the primary GPT data comprises a protective MBR of LBA0, a GPT head of LBA1 and partition entries of LBA2 to LBA33, the secondary GPT data comprises a secondary GPT head of LBA-1 and secondary partition entries of LBA-33 to LBA-2, and if the data is an MBR disk, the disk metadata is MBR data of LBA0 and EBR data of a logical partition chain under an extended partition;
disk general data: disk generic data includes, but is not limited to, disk application layer unique fingerprint, disk partition table type, disk size, disk partition table CRC;
disk valid partition data: including but not limited to partition unique fingerprint, partition starting LBA, partition LBA number, partition file system, partition application layer driver number, the valid partition satisfies the following conditions:
one of file system FAT, FAT32, NTFS exists;
partition properties belong to system partitions, reserved partitions, boot partitions, recovery partitions, EFI system partitions, and data partitions.
Preferably, the data correction mode in S5 is to filter out the disk and partition with data errors, correct and back up the mode mark, and obtain new disk group data.
Preferably, the specific implementation method of the S6 is as follows: iterating the disk group, performing backup on the disk by disk, and applying for a virtual disk file according to the size of the disk when the disk is marked as a full quantity; when the disk is marked as an increment, the virtual disk file of the last backup task of the disk history is inquired, the virtual disk file is used as a mirror image to create a post-writing copy virtual disk file, after the virtual disk file is created, the virtual disk file is mapped into a device node under the backup integrated machine udev, the device node is used for receiving writing of backup data from a client disk, and after the virtual disk file and mapping resource application are completed, virtual disk file resources and mapping resources thereof are returned to a target Windows system.
Preferably, the effective partition transmission method in S7 is as follows: before backup, using Windows volume-level IO driver to create COW or ROW snapshot for effective partition and exposing snapshot virtual device to application layer, executing effective data extraction for partition according to logic cluster for partition snapshot virtual device, under this process, fingerprint, offset byte and distribution mark of each partition are recorded and stored in client local fingerprint file and bitmap file, and partition data are transferred to mapped virtual disk file according to offset byte of partition, if partition mark is incremental backup, in addition to the above-mentioned process, the partition fingerprint file of last snapshot point of the whole machine is additionally pulled to local, when transferring partition data, the historical fingerprint value of the partition is read from the historical fingerprint file, then the current fingerprint value of the partition is calculated, finally the historical fingerprint value is compared with the current fingerprint value, and if the same, transparent transfer is ignored, otherwise transparent transfer is performed.
Preferably, in S8, the complete machine snapshot includes three key data, where the three key data are respectively: bitmap files of all effective partitions of the original client disk set, block fingerprint files of all effective partitions of the original client disk set, and data files of all disks of the original client disk set.
Preferably, the correction and combining logic in S9 is as follows:
in the backup integrated machine, if the whole machine snapshot chain has a connection pipe requirement, the original whole machine snapshot chain is deformed into a whole machine snapshot multi-path tree and is marked as a side chain, and if sub side chains exist in the whole machine snapshot points to be combined, the side chains are required to be removed firstly; if the complete machine snapshot point s3 is a complete machine snapshot point exceeding the reserved snapshot number N, one of the complete machine snapshots needs to be deleted, and the validity of the complete machine snapshot chain is still maintained, and the merging logic thereof is divided into three steps:
s9.1: the incremental data of all disk groups of the forward whole machine snapshot point s2 of the whole machine snapshot point s3 are shifted according to the incremental data and submitted to the corresponding disk groups of the whole machine snapshot point s1 block by block;
s9.2: changing the forward direction complete machine snapshot dependency pointer of the complete machine snapshot point s3 from pointing to the complete machine snapshot point s2 to the complete machine snapshot point s1, so that the forward direction snapshot of the complete machine snapshot point s3 points to the complete machine snapshot point s1;
s9.3: and deleting redundant complete machine snapshot point s2.
Compared with the prior art, the invention has the beneficial effects that:
the method and the device use the marking technology of the metadata of the disk equipment, particularly sense the new addition, modification, deletion and the like of the metadata of the disk equipment, store and manage the marking set of the disk environment before each backup, thereby determining that the data synchronization mode of the disk environment is full backup or incremental when the disk environment is scheduled for a certain time, and realize the effect of permanent incremental backup only by creating a backup plan in the whole machine backup scene of Windows through automatic management of the whole machine disk snapshot chain at the snapshot storage side without reconfiguring the backup plan when the disk environment is changed. The method solves the problems that in the prior art, the implementation effect of permanent incremental backup of the whole Windows machine is limited to the disk environment in the first backup, and the limitation of creating a configuration backup plan again is needed under the condition that a new disk or a reduced disk appears in the subsequent backup.
Drawings
FIG. 1 is a schematic diagram of a main logic flow of a Windows backup task according to the present application;
FIG. 2 is a schematic diagram illustrating critical data of a disk according to the present application;
FIG. 3 is a schematic illustration of a storage form of a complete machine snapshot;
FIG. 4 is a schematic diagram illustrating the logical relationship of a complete machine snapshot chain;
FIG. 5 is a schematic illustration of side chain determination and recovery at the instant of overall machine snapshot chain recovery;
fig. 6 is a logic flow diagram of data recovery of a whole machine snapshot under a whole machine snapshot chain.
Detailed Description
The present invention will be further described in detail below with reference to the accompanying drawings and specific examples in order to facilitate understanding of the technical content of the present invention by those skilled in the art. It should be understood that the specific examples described herein are intended to illustrate the invention and are not intended to limit the invention.
Example 1:
a permanent incremental backup method of a Windows complete machine comprises the following steps:
entering a terminal control interface of the backup integrated machine, creating a whole machine backup strategy for a target Windows system, configuring a backup snapshot point reserved by the strategy as N, namely, N time points for restoring, and after the backup strategy is started, the backup integrated machine schedules backup operation according to a planned preset period, wherein the main service logic flow of each generated backup operation can be summarized as the following steps:
s1: the backup integrated machine initializes the snapshot point storage directory of the current backup and remotely issues a backup instruction to the target Windows system;
s2: after receiving the backup instruction, the data synchronization management module of the target Windows system immediately initializes the backup task session and distributes a system process-level mutual exclusion lock, and the backup operation is in the context of the lock, thereby ensuring the singleness of task execution;
s3: after the process mutual exclusion lock is initially completed, a snapshot point storage catalog pre-initialization instruction is sent to a snapshot point storage module, and the snapshot point storage module initializes the snapshot catalog of the time;
s4: the disk information collection module immediately collects the direct-connection physical disk group data of the own system, and for each disk data subordinate to the disk group data, as shown in fig. 2, the direct-connection physical disk group data comprises three key data:
one is disk metadata, which is primary GPT data (protective MBR of LBA0, GPT header of LBA1, partition entries of LBA2 to LBA 33) and secondary GPT data (secondary GPT header of LBA-1, secondary partition entries of LBA-33 to LBA-2) if it is GPT disk, and MBR data of LBA0 and EBR data of logical partition chains under extended partitions if it is MBR disk;
and the second is disk general data, including but not limited to a disk application layer unique fingerprint, a disk partition table type, a disk size and a disk partition table CRC. It should be noted that the UNIQUE fingerprint of the disk application layer must be strongly correlated with the system application layer, and the invention uses the combination of the storage_query_attribute kernel structure to obtain the disk hardware serial number and the storage_device_identifier kernel structure to obtain the DUID (DEVICE UNIQUE IDENTIFIER) as the UNIQUE fingerprint, so that the UNIQUE fingerprint can be realized in the scenarios of restarting the operating system, moving from one computer to another computer, multipath system, etc.;
third, the data of the effective partition of the disk includes, but is not limited to, unique fingerprints of the partition, partition starting LBA, partition LBA number, partition file system, partition application layer driver number, etc., and the judging conditions of the effective partition are as follows:
one of file system FAT, FAT32, NTFS exists;
with the continuous update of the Windows version, NTFS is now becoming a partition standard file system, so the determination condition of an effective partition is that there is a file system NTFS;
for the partition of the loaded file system, the volume serial number is used as the unique fingerprint, and for the partition of the unloaded file system, the fixed value of 0000-0000 is used as the unique fingerprint;
partition properties belong to system partitions, reserved partitions, boot partitions, recovery partitions, EFI system partitions, and data partitions;
s5: after the target Windows system disk information collection module successfully collects the information in the S4, the collected disk group data is transmitted to the backup mode judgment module;
s6: the backup mode judging module traverses the disk group data, traverses the effective partition data in the disk group data, and executes data correction and backup mode marking, particularly, the data correction mode is a disk and partition for filtering data errors, and the full/increment marking mode is as follows:
the total judgment conditions of the disk are as follows:
the unique identifier of the disk application layer is not hit from the disk group information of the last historical backup under the strategy;
capacity expansion/contraction of the magnetic disk;
disk partition table type changes, such as MBR to GPT or GPT to MBR;
the increment judgment conditions of the disk are as follows:
all the disk total judgment conditions are not satisfied;
the total judgment conditions of the partitions are as follows:
the unique identification of the partition is not hit from the disk group data which is backed up last time in the history under the strategy;
partitioning expansion/contraction;
partition unique identification change;
partition file system changes;
the increment judgment conditions of the partition are as follows:
all partition total judgment conditions are not satisfied;
and the backup mode judging module transmits the disk group data back to the data synchronous management module of the target Windows system.
S7: and the data synchronization management module of the target Windows system receives the corrected and marked disk group data, executes subsequent backup operation according to the disk data and the backup mode mark in the corrected and marked disk group data, and executes the backup operation as iterative disk groups and executes the backup one by one. When the disk is marked as full, applying a virtual disk file with copy-on-write property in the snapshot point storage module according to the size of the disk; when the disk is marked as an increment, the virtual disk file of the last backup task of the history of the disk is queried, and the virtual disk file is used as a mirror image to create a post-write copy virtual disk file. After the virtual disk file is created, the virtual disk file is mapped into a device node under the backup integrated machine udev and is used for receiving writing of backup data from a client disk. And after the application of the virtual disk file and the mapping resource is completed, returning the virtual disk file resource and the mapping resource to a data synchronization management module of the target Windows system.
S8: the data synchronization management module executes data stream transmission logic. Firstly, disk metadata are transmitted to virtual disk equipment according to LBA offset, and metadata are transmitted thoroughly. And secondly, all the effective partition data under the transmission disk are backed up by one of the effective partitions. Before backup, a COW or ROW snapshot is created for an effective partition by utilizing a Windows volume-level IO driver, snapshot virtual equipment is exposed to an application layer, a data synchronization management module immediately performs effective data extraction for the partition according to a logic cluster, the logic cluster belongs to the upper layer of a physical cluster of a file system, the block transmission speed can be greatly improved, the effective data extraction is performed for the snapshot virtual equipment of the partition, for a RAW partition, a fixed logic cluster is used, and according to the fact that all the logic clusters are effective data, in this process, the records of fingerprints, offset byte bits, allocation marks and the like of each block of the partition are stored into a client local fingerprint file and a bitmap file according to bits by a block fingerprint management module, and the block data is transmitted into the mapped virtual disk file according to the offset byte bits of the block. It should be noted that, if the partition is marked as full-scale backup, the block fingerprint management module does not perform other processes except the foregoing processes; if the partition is marked as incremental backup, the partition fingerprint file of the last time of the snapshot point of the whole machine in the history of the policy is additionally pulled to the local area, when the partitioned data is transmitted through, the history fingerprint value of the partitioned block is preferentially read from the history fingerprint file, then the current fingerprint value of the partitioned block is calculated, finally the history fingerprint value is compared with the current fingerprint value, if the history fingerprint value is the same, the transparent transmission is ignored, and if the history fingerprint value is different, the transparent transmission is performed through. In order to improve data transmission efficiency, the system multithreading concurrent processing can be utilized for the calculation of the block fingerprint, the filling of the block bitmap and the uploading of the block data. After the release is finished, the block fingerprint file and the bitmap file of the local partition are transmitted to the snapshot point storage module, the snapshot point storage module files the snapshot directory, and when one disk is processed, mapping resources of the backup integrated machine are released through the snapshot point storage module, and virtual disk file resources corresponding to the mapping resources are filed.
S9: after all the disks of the target Windows system are backed up, the data synchronization management module sends a complete machine snapshot archiving instruction to the snapshot point storage module and releases all the resource handles associated with the local and remote tasks, so that the snapshot resource directory of the tasks on the storage side of the backup integrated machine can form a complete machine snapshot, and as shown in FIG. 3, the complete machine snapshot comprises three key data, namely bitmap files of all the effective partitions of the disk group of the original client, block fingerprint files of all the effective partitions of the disk group of the original client, and data files of all the disks of the disk group of the original client.
S10: with the increase of backup tasks, as shown in fig. 4, a complete machine snapshot chain is gradually formed, and eventually, the number of nodes on the chain exceeds the number N of reserved snapshot points in the policy, and the current snapshot number is recorded as CN, so when CN > N, correction and merging are required to be performed on the complete machine snapshot chain, and specific correction and merging logic is as follows:
as shown in fig. 5, in the backup integrated machine, if the complete machine snapshot chain has a connection requirement, the original complete machine snapshot chain is changed into a complete machine snapshot multi-path tree and marked as a side chain, and if the sub side chain exists in the complete machine snapshot point to be combined, the side chain is required to be removed first;
then, as shown in fig. 6, if the complete machine snapshot point s3 is a complete machine snapshot point exceeding the reserved snapshot number N, one of the complete machine snapshots needs to be deleted, and the validity of the complete machine snapshot chain is still maintained, and the merging logic thereof is divided into three steps:
the incremental data of all disk groups of the forward whole machine snapshot point s2 of the whole machine snapshot point s3 are shifted according to the incremental data and submitted to the corresponding disk groups of the whole machine snapshot point s1 block by block;
changing the forward direction complete machine snapshot dependency pointer of the complete machine snapshot point s3 from pointing to the complete machine snapshot point s2 to the complete machine snapshot point s1, so that the forward direction snapshot of the complete machine snapshot point s3 points to the complete machine snapshot point s1;
deleting redundant complete machine snapshot point s2;
thus, the merging of one snapshot point is completed, and the concept of permanent increment is realized by correctly recovering resources and correctly correcting a snapshot chain along with the periodical execution of backup tasks.
In this embodiment, the present application uses a marking technology of metadata of a disk device, particularly senses new addition, modification, deletion, and the like of the metadata of the disk device, and stores and manages a marking set of a disk environment before each backup, so as to determine that a data synchronization mode of the disk environment is full backup or incremental when the disk environment is scheduled for a certain time, and the snapshot storage side realizes an effect of permanent incremental backup by only creating a backup plan once in a complete machine backup scene of Windows through automatic management of a complete machine disk snapshot chain, without reconfiguring the backup plan when the disk environment changes. The method solves the problems that in the prior art, the implementation effect of permanent incremental backup of the whole Windows machine is limited to the disk environment in the first backup, and the limitation of creating a configuration backup plan again is needed under the condition that a new disk or a reduced disk appears in the subsequent backup.
Claims (7)
1. The method for permanently and incrementally backing up the whole Windows machine is characterized by comprising the following steps:
s1: the integrated backup machine initializes a storage directory of the backup snapshot point and remotely issues a backup instruction to the target Windows system;
s2: after receiving a backup instruction, the target Windows system initializes a backup task session, distributes a system process-level mutual exclusion lock, initializes the mutual exclusion lock, and the backup task session is in the context of the mutual exclusion lock, wherein the mutual exclusion lock is used for ensuring the singleness of the backup task execution;
s3: initializing a snapshot directory after the initialization of the mutual exclusion lock is completed;
s4: the target Windows system collects physical disk group data and sends the physical disk group data to the backup integrated machine, and for each piece of disk data subordinate to the disk group data, the target Windows system contains three key data, namely disk metadata, disk general data and disk effective partition data;
s5: the backup all-in-one machine traverses the effective partition data in the collected physical disk group data, executes data correction and backup mode marking operation, and sends the physical disk group data after the data correction and backup mode marking operation to a target Windows system, wherein the backup mode marking comprises a full quantity marking and an increment marking, and the full quantity marking comprises the following steps:
the disk total mark judgment at least meets the following conditions:
the unique identifier of the disk application layer is not hit from the disk group information of the last historical backup under the strategy; the capacity of the magnetic disk is expanded or contracted; any of the disk partition table type changes;
the incremental mark judgment conditions of the disk are as follows: all the disk total mark judging conditions are not satisfied;
the full flag determination of the partition satisfies at least the condition:
the unique identification of the partition is not hit from the disk group data which is backed up last time in the history under the strategy; partitioning expansion or contraction; partition unique identification change; any of the partition file system changes;
the incremental mark judgment conditions of the partition are: all partition total judgment conditions are not satisfied;
s6: the target Windows system creates virtual disk file resources and mapping resources for the physical disk group according to the physical disk group data and the backup mode mark;
s7: the target Windows system executes data stream transmission logic; transmitting disk metadata to virtual disk equipment according to LBA offset, transmitting all effective partition data under a disk after the disk metadata is transmitted, releasing a locally held block handle resource of the partition after each effective partition is transmitted, archiving a local partition file according to the snapshot catalog after the transmission is finished, releasing mapping resources of a backup integrated machine after each disk is processed, and archiving corresponding virtual disk file resources;
s8: after all the disks of the target Windows system are backed up, the target Windows system releases all local and remote resource handles associated with the task to form a whole machine snapshot;
s9: S1-S8 are repeated to gradually form a whole machine snapshot chain, when the number of nodes on the chain exceeds the number N of reserved snapshot points in the strategy, the current snapshot number is recorded as CN, when CN > N, correction and combination are executed on the whole machine snapshot chain, and the permanent increment of the whole Windows machine is realized along with the periodical execution of backup tasks.
2. The method for permanent incremental backup of a whole Windows machine according to claim 1, wherein three key data in S4 are specifically expressed as:
disk metadata: if the data is a GPT disk, the disk metadata is primary GPT data and secondary GPT data, wherein the primary GPT data comprises a protective MBR of LBA0, a GPT head of LBA1 and partition entries of LBA2 to LBA33, the secondary GPT data comprises a secondary GPT head of LBA-1 and secondary partition entries of LBA-33 to LBA-2, and if the data is an MBR disk, the disk metadata is MBR data of LBA0 and EBR data of a logical partition chain under an extended partition;
disk general data: disk generic data includes, but is not limited to, disk application layer unique fingerprint, disk partition table type, disk size, disk partition table CRC;
disk valid partition data: including but not limited to partition unique fingerprint, partition starting LBA, partition LBA number, partition file system, partition application layer driver number, the valid partition satisfies the following conditions:
one of file system FAT, FAT32, NTFS exists;
partition properties belong to system partitions, reserved partitions, boot partitions, recovery partitions, EFI system partitions, and data partitions.
3. The method of claim 2, wherein the data correction in S5 is to filter out the data error of the disk and partition, and correct and back up the mode mark to obtain new disk group data.
4. The method for permanently and incrementally backing up a whole Windows machine according to claim 3, wherein the specific implementation method of S6 is as follows: iterating the disk group, performing backup on the disk by disk, and applying for a virtual disk file according to the size of the disk when the disk is marked as a full quantity; when the disk is marked as an increment, the virtual disk file of the last backup task of the disk history is inquired, the virtual disk file is used as a mirror image to create a post-writing copy virtual disk file, after the virtual disk file is created, the virtual disk file is mapped into a device node under the backup integrated machine udev, the device node is used for receiving writing of backup data from a client disk, and after the virtual disk file and mapping resource application are completed, virtual disk file resources and mapping resources thereof are returned to a target Windows system.
5. The method for permanent incremental backup of a whole Windows machine according to claim 4, wherein the effective partition transmission method in S7 is as follows: before backup, using Windows volume-level IO driver to create COW or ROW snapshot for effective partition and exposing snapshot virtual device to application layer, executing effective data extraction for partition according to logic cluster for partition snapshot virtual device, under this process, fingerprint, offset byte and distribution mark of each partition are recorded and stored in client local fingerprint file and bitmap file, and partition data are transferred to mapped virtual disk file according to offset byte of partition, if partition mark is incremental backup, in addition to the above-mentioned process, the partition fingerprint file of last snapshot point of the whole machine is additionally pulled to local, when transferring partition data, the historical fingerprint value of the partition is read from the historical fingerprint file, then the current fingerprint value of the partition is calculated, finally the historical fingerprint value is compared with the current fingerprint value, and if the same, transparent transfer is ignored, otherwise transparent transfer is performed.
6. The method for permanent incremental backup of a whole machine of Windows according to claim 1, wherein the whole machine snapshot in S8 comprises three key data, wherein the three key data are respectively: bitmap files of all effective partitions of the original client disk set, block fingerprint files of all effective partitions of the original client disk set, and data files of all disks of the original client disk set.
7. The method of claim 1, wherein the correction and merge logic in S9 is as follows:
in the backup integrated machine, if the whole machine snapshot chain has a connection pipe requirement, the original whole machine snapshot chain is deformed into a whole machine snapshot multi-path tree and is marked as a side chain, and if sub side chains exist in the whole machine snapshot points to be combined, the side chains are required to be removed firstly; if the complete machine snapshot point s3 is a complete machine snapshot point exceeding the reserved snapshot number N, one of the complete machine snapshots needs to be deleted, and the validity of the complete machine snapshot chain is still maintained, and the merging logic thereof is divided into three steps:
s9.1: the incremental data of all disk groups of the forward whole machine snapshot point s2 of the whole machine snapshot point s3 are shifted according to the incremental data and submitted to the corresponding disk groups of the whole machine snapshot point s1 block by block;
s9.2: changing the forward direction complete machine snapshot dependency pointer of the complete machine snapshot point s3 from pointing to the complete machine snapshot point s2 to the complete machine snapshot point s1, so that the forward direction snapshot of the complete machine snapshot point s3 points to the complete machine snapshot point s1;
s9.3: and deleting redundant complete machine snapshot point s2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311644041.XA CN117349086B (en) | 2023-12-04 | 2023-12-04 | Permanent incremental backup method for Windows complete machine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311644041.XA CN117349086B (en) | 2023-12-04 | 2023-12-04 | Permanent incremental backup method for Windows complete machine |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117349086A CN117349086A (en) | 2024-01-05 |
| CN117349086B true CN117349086B (en) | 2024-02-23 |
Family
ID=89356074
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311644041.XA Active CN117349086B (en) | 2023-12-04 | 2023-12-04 | Permanent incremental backup method for Windows complete machine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117349086B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1873622A (en) * | 2006-04-20 | 2006-12-06 | 北京艾德斯科技有限公司 | Method and equipment for backing up, replicating and recovering data under environment |
| CN101295276A (en) * | 2008-06-20 | 2008-10-29 | 中国科学院计算技术研究所 | Magnetic disk data backup system and method |
| US7606868B1 (en) * | 2006-03-30 | 2009-10-20 | Wmware, Inc. | Universal file access architecture for a heterogeneous computing environment |
| US9612914B1 (en) * | 2012-07-23 | 2017-04-04 | Veritas Technologies Llc | Techniques for virtualization of file based content |
| CN106919477A (en) * | 2017-03-03 | 2017-07-04 | 上海爱数信息技术股份有限公司 | The analytic method and system of a kind of virtual disk |
| US10114705B1 (en) * | 2015-04-14 | 2018-10-30 | EMC IP Holding Company LLC | Presenting virtual machine backup files for block and file level restore |
| CN110998537A (en) * | 2017-12-26 | 2020-04-10 | 华为技术有限公司 | Expired backup processing method and backup server |
| CN111124620A (en) * | 2019-12-26 | 2020-05-08 | 航天壹进制(南京)数据科技有限公司 | Continuous data protection method for application programming interface for IO filtering |
| CN112965856A (en) * | 2021-02-24 | 2021-06-15 | 上海英方软件股份有限公司 | Backup data-based fast fine-grained recovery method and device |
| CN113238891A (en) * | 2021-03-19 | 2021-08-10 | 浪潮云信息技术股份公司 | Backup deletion method and system based on backup chain |
| CN114637633A (en) * | 2022-04-01 | 2022-06-17 | 南京壹进制信息科技有限公司 | Backup recovery method based on domestic dream database |
| CN115509824A (en) * | 2022-11-23 | 2022-12-23 | 深圳市科力锐科技有限公司 | Data backup method, device, equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10055300B2 (en) * | 2015-01-12 | 2018-08-21 | Actifio, Inc. | Disk group based backup |
| US11886226B2 (en) * | 2021-11-29 | 2024-01-30 | Rubrik, Inc. | Consolidating snapshots using partitioned patch files |
-
2023
- 2023-12-04 CN CN202311644041.XA patent/CN117349086B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7606868B1 (en) * | 2006-03-30 | 2009-10-20 | Wmware, Inc. | Universal file access architecture for a heterogeneous computing environment |
| CN1873622A (en) * | 2006-04-20 | 2006-12-06 | 北京艾德斯科技有限公司 | Method and equipment for backing up, replicating and recovering data under environment |
| CN101295276A (en) * | 2008-06-20 | 2008-10-29 | 中国科学院计算技术研究所 | Magnetic disk data backup system and method |
| US9612914B1 (en) * | 2012-07-23 | 2017-04-04 | Veritas Technologies Llc | Techniques for virtualization of file based content |
| US10114705B1 (en) * | 2015-04-14 | 2018-10-30 | EMC IP Holding Company LLC | Presenting virtual machine backup files for block and file level restore |
| CN106919477A (en) * | 2017-03-03 | 2017-07-04 | 上海爱数信息技术股份有限公司 | The analytic method and system of a kind of virtual disk |
| CN110998537A (en) * | 2017-12-26 | 2020-04-10 | 华为技术有限公司 | Expired backup processing method and backup server |
| CN111124620A (en) * | 2019-12-26 | 2020-05-08 | 航天壹进制(南京)数据科技有限公司 | Continuous data protection method for application programming interface for IO filtering |
| CN112965856A (en) * | 2021-02-24 | 2021-06-15 | 上海英方软件股份有限公司 | Backup data-based fast fine-grained recovery method and device |
| CN113238891A (en) * | 2021-03-19 | 2021-08-10 | 浪潮云信息技术股份公司 | Backup deletion method and system based on backup chain |
| CN114637633A (en) * | 2022-04-01 | 2022-06-17 | 南京壹进制信息科技有限公司 | Backup recovery method based on domestic dream database |
| CN115509824A (en) * | 2022-11-23 | 2022-12-23 | 深圳市科力锐科技有限公司 | Data backup method, device, equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| Instant recovery for data center savings;Goetz Graefe 等;《ACM SIGMOD Record》;第44卷(第2期);29-34 * |
| 构建基于SAN的图书馆存储区域网;王建平 等;《江西图书馆学刊》;第38卷(第3期);104-105，108 * |
| 虚拟机可靠性备份机制的研究与实现;褚福勇;《中国优秀硕士学位论文全文数据库 信息科技辑》(第S1期);I138-91 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117349086A (en) | 2024-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11086545B1 (en) | Optimizing a storage system snapshot restore by efficiently finding duplicate data | |
| US11741048B2 (en) | Distributed write journals that support fast snapshotting for a distributed file system | |
| US11762817B2 (en) | Time sequence data management | |
| US9323624B2 (en) | File management system and file management method | |
| US10866869B2 (en) | Method to perform crash and failure recovery for a virtualized checkpoint protected storage system | |
| EP3646195B1 (en) | Systems and methods of restoring a dataset of a database for a point in time | |
| US9389800B1 (en) | Synthesizing virtual machine disk backups | |
| US9588847B1 (en) | Recovering corrupt virtual machine disks | |
| EP2329377B1 (en) | Using a snapshot as a data source | |
| US8521694B1 (en) | Leveraging array snapshots for immediate continuous data protection | |
| US8433683B2 (en) | Systems and methods of data replication of a file system | |
| US7257690B1 (en) | Log-structured temporal shadow store | |
| TWI222562B (en) | Dynamic links to file system snapshots | |
| EP1349089A2 (en) | System and method for managing a plurality of snapshots of a file system | |
| CN106021016A (en) | Virtual point in time access between snapshots | |
| US20080027998A1 (en) | Method and apparatus of continuous data protection for NAS | |
| US20070276878A1 (en) | System and method for providing continuous data protection | |
| WO2015034827A1 (en) | Replication of snapshots and clones | |
| TW200303468A (en) | Deferred copy-on-write of a snapshot | |
| US20130159257A1 (en) | Systems, Method, and Computer Program Products Providing Sparse Snapshots | |
| US10977143B2 (en) | Mirrored write ahead logs for data storage system | |
| WO2015088735A1 (en) | Replication of volumes on demand using absent allocation | |
| US10776211B1 (en) | Methods, systems, and apparatuses to update point in time journal using map reduce to create a highly parallel update | |
| CN108255638A (en) | A kind of snapshot rollback method and device | |
| US20230237024A1 (en) | Data Storage System and Method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |