A differentiated backup directory construction and deduplication scheduling method and system

Abstract

The application relates to the technical field of power industry control system data protection and backup recovery, and particularly provides a differential backup directory construction and deduplication scheduling method and system. The method comprises the following steps: acquiring a distributed node set in a distributed control system; simultaneously generating object check information to obtain a complete feature data set of a backup object; constructing a backup directory based on the complete feature data set; taking file-level deduplication and only-fingerprint-index deduplication as the default priority of a deduplication strategy to form an initial configuration of a backup scheduling plan; generating and executing the backup scheduling plan according to the initial configuration of the backup scheduling plan; simultaneously setting a deduplication window and a degradation rule for different data types; checking the backup result and writing the check result back to a directory entry to update version information and object check information, so that a traceable trusted backup version and a differential positioning record are obtained. The application realizes differential deduplication and backup scheduling mainly based on file-level deduplication and only-fingerprint-index deduplication.

Description

Technical Field

[0001] This invention relates to the field of data protection, backup and recovery technology for power industry control systems, and in particular to a method and system for constructing and deduplicating a differentiated backup catalog. Background Technology

[0002] Distributed Control Systems (DCS), as the core control and monitoring platform for power generation, typically consist of multiple distributed nodes, including engineer workstations, operator workstations, historical workstations, application / database servers, and bridge / inter-domain communication nodes. These nodes carry various critical objects such as engineering and deployment files, screen and configuration data, permission and responsibility area data, alarm and event data, historical / time-series / relational database data, and inter-domain communication and mapping configurations. Furthermore, they continuously undergo dynamic changes during long-term operation, including configuration modifications, alarm events, and the accumulation of historical time-series data.

[0003] Existing distributed control system backup methods generally suffer from the following problems: First, backup objects are diverse, widely distributed, and change with varying frequencies. Common practices often employ uniform full or simple incremental strategies, resulting in high backup redundancy, large storage consumption, long backup windows, and difficulty in ensuring priority protection and availability recovery of critical objects. Second, distributed control systems are often partitioned according to security domains and network domains such as production control, secure access, and management information. Cross-domain data flow and backup strategies are subject to compliance and security constraints. Existing backup solutions typically lack a directory-based management mechanism that binds security domains / network domains, making them prone to risks such as cross-domain index misuse, cross-domain deduplication, or policy mismatch. Third, the backup process and deduplication calculations consume CPU, disk I / O, and network bandwidth resources. Without scheduling and degradation mechanisms oriented towards real-time business, critical functions such as control operations, alarm handling, and historical data storage may be disrupted, thus affecting system stability. Furthermore, the lack of traceable verification and directory write-back after backup completion can easily lead to situations where the backup appears successful but recovery is unusable.

[0004] Therefore, a technical solution is needed that can be used for distributed nodes and multiple types of objects in a distributed control system, combined with security domain / network domain partition constraints, to implement differentiated backup strategy selection, a deduplication mechanism with file-level deduplication and fingerprint indexing as the core, and has a feasible scheduling and verification closed loop to improve backup efficiency and recovery reliability. Summary of the Invention

[0005] To achieve the above objectives, the present invention adopts the following technical solution: One aspect of the present invention provides a method for constructing and deduplicating a differentiated backup directory, comprising the following steps: The system acquires a set of distributed nodes within the distributed control system, collects node metadata for each node, automatically discovers a set of backup objects on each node, assigns an object identifier and object location to each backup object, performs on-site classification of each backup object to obtain a data type identifier, calculates a quadruple of change frequency index, repeatability index, recovery priority index, and business disturbance sensitivity index, and generates object verification information to obtain a complete feature dataset of the object to be backed up. A backup directory is constructed based on the complete feature dataset. The backup directory contains fingerprint indexes partitioned by security domain identifier and network domain identifier for file-level deduplication and difference location. For each backup object, a differentiated backup strategy and a differentiated deduplication strategy are selected based on the directory indicator quadruple. The deduplication strategy prioritizes file-level deduplication and fingerprint index-only deduplication by default, forming the initial configuration of the backup scheduling plan. The backup scheduling plan is generated and executed based on the initial configuration. Concurrency, rate limit, and execution window are set for different security domain identifiers and different network domain identifiers. Deduplication windows and degradation rules are set for different data types. When the degradation conditions are met, the concurrency is reduced, the rate limit is reduced, the deduplication window is narrowed, and the deduplication strategy is downgraded to fingerprint index deduplication only. The backup results are verified and the verification results are written back to the directory entries to update the version information and object verification information, so as to obtain a traceable and reliable backup version and difference location record.

[0006] Another aspect of the present invention provides a differentiated backup directory construction and deduplication scheduling system, comprising: The backup object processing component is used to obtain the set of distributed nodes in the distributed control system, collect node metadata for each node, automatically discover the set of backup objects on each node, assign an object identifier and object location to each backup object, perform on-site classification of each backup object to obtain a data type identifier, calculate a quadruple of change frequency index, repeatability index, recovery priority index and business disturbance sensitivity index, and generate object verification information to obtain a complete feature dataset of the object to be backed up. The differential deduplication component is used to build a backup directory based on the complete feature dataset. The backup directory contains fingerprint indexes partitioned by security domain identifier and network domain identifier for file-level deduplication and difference location. It also selects a differential backup strategy and a differential deduplication strategy for each backup object based on the directory indicator quadruple. The deduplication strategy prioritizes file-level deduplication and fingerprint index-only deduplication by default, forming the initial configuration of the backup scheduling plan. The backup result verification component is used to generate and execute the backup scheduling plan based on the initial configuration of the backup scheduling plan. It sets the concurrency, rate limit, and execution window for different security domain identifiers and different network domain identifiers, and sets the deduplication window and degradation rules for different data types. When the degradation conditions are met, it reduces the concurrency, lowers the rate limit, narrows the deduplication window, and downgrades the deduplication strategy to fingerprint index-only deduplication. It verifies the backup results and writes the verification results back to the directory entries to update the version information and object verification information, thus obtaining a traceable and reliable backup version and difference location record.

[0007] The present invention relates to a differentiated backup catalog construction and deduplication scheduling method and related apparatus for distributed nodes in a distributed control system. This method constructs a backup catalog with dual binding of Security Domain Identifier (SID) and Network Domain Identifier (NID) by classifying backup objects on-site and calculating indicators such as change frequency, redundancy, recovery priority, and sensitivity to business disturbances. Under strict constraints of identical SID and NID, a fingerprint index is established to achieve differentiated deduplication and backup scheduling, primarily using file-level deduplication and fingerprint-based deduplication. Simultaneously, by combining concurrency, rate limits, execution windows, deduplication windows, and degradation mechanisms, backup execution and verification write-back are completed, thereby reducing redundancy, minimizing disturbances to real-time services, and improving the reliability and efficiency of subsequent difference location and recovery. Attached Figure Description

[0008] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used in conjunction with embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings: Figure 1 This is a flowchart of the differentiated backup directory construction and deduplication scheduling method provided in Embodiment 1 of the present invention; Figure 2 This is a schematic diagram of the differentiated backup directory construction and deduplication scheduling method provided in Embodiment 1 of the present invention; Figure 3 This is a flowchart illustrating the process of calculating the four-tuple of change frequency index, repeatability index, recovery priority index, and service disturbance sensitivity index provided in Embodiment 2 of the present invention. Figure 4 This is a flowchart illustrating the process of selecting a differentiated backup strategy and a differentiated deduplication strategy for each backup object based on the directory index quadruple provided in Embodiment 3 of the present invention. Figure 5 This is a block diagram of the differentiated backup directory construction and deduplication scheduling system provided in Embodiment 8 of the present invention; Figure 6 A block diagram of the electronic device provided by the present invention; Figure 7 A block diagram of a computer-readable storage medium provided for this invention.

[0009] Reference numerals: 1. Backup object processing component; 2. Differentiation deduplication component; 3. Backup result verification component; 4. Central processing unit / microprocessor / main control chip; 5. Storage medium; 6. Data bus; 7. Input / output bus / external bus / device bus; 8. Display; 9. Input / output device; 10. Computer-readable instructions; 11. Non-transitory computer-readable storage medium. Detailed Implementation

[0010] The technical solutions of the present invention will now be described with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.

[0011] Hereinafter, the terms "first," "second," etc., are used for descriptive convenience only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0012] In this invention, unless otherwise explicitly specified and limited, the term "connection" should be interpreted broadly. For example, "connection" can be a fixed mechanical connection, a detachable mechanical connection, or an integral part; or, "connection" can be a direct connection or an indirect connection through an intermediate medium. Furthermore, unless otherwise explicitly specified and limited, the term "coupling" should be interpreted broadly. For example, "coupling" can be a direct electrical connection, such as physical contact and electrical conduction between two components; it can also be understood as an electrical connection between different components in a circuit structure through physical lines capable of transmitting electrical signals, such as copper foil or wires on a printed circuit board (PCB), to transmit electrical signals; or, "coupling" can be an indirect electrical connection between two components through an intermediate medium; or, "coupling" can be an electrical connection between two components in a non-contact manner, such as an electrical connection between two components using capacitive coupling to transmit electrical signals.

[0013] In this embodiment of the invention, directional terms such as "up," "down," "left," and "right" may be defined relative to the orientation of the components shown in the accompanying drawings. It should be understood that these directional terms can be relative concepts, used for relative description and clarification, and can change accordingly depending on the orientation of the components in the accompanying drawings.

[0014] The differentiated backup method for distributed systems in this embodiment includes: establishing a backup object feature model: assigning a unique identifier to backup objects automatically discovered by each node, and collecting multi-dimensional feature data including data type identifier, change frequency, redundancy, recovery priority, and business sensitivity; constructing an intelligent backup catalog: establishing a partition fingerprint index based on both security domain and network domain dimensions, and dynamically matching differentiated backup strategies and deduplication strategies according to the multi-dimensional feature data; performing elastic scheduling: setting differentiated concurrency control parameters and transmission strategies according to security domain / network domain division, and adjusting the deduplication granularity and resource quota in real time based on system load status; and implementing closed-loop verification: performing end-to-end verification of backup results, and dynamically updating version traceability information and difference records to the backup catalog. The deduplication strategy includes: first priority using file-level content deduplication; second priority using fingerprint index deduplication; and dynamically switching priorities based on system resource usage. The elastic scheduling includes: reserving minimum guaranteed bandwidth for high business-sensitive data; automatically reducing the deduplication processing depth when the system load reaches a threshold; and implementing differentiated time window control according to data type.

[0015] Example 1: As Figure 1 As shown, this embodiment of the invention provides a method for constructing and deduplicating a differentiated backup directory, comprising the following steps: Step S100: Obtain the set of distributed nodes in the distributed control system, collect node metadata for each node, automatically discover the set of backup objects on each node, assign object identifier and object location to each backup object; perform on-site classification of each backup object to obtain data type identifier, calculate the four-tuple of change frequency index, repeatability index, recovery priority index and business disturbance sensitivity index, and generate object verification information to obtain the complete feature dataset of the object to be backed up. Step S200: Construct a backup directory based on the complete feature dataset. The backup directory contains fingerprint indexes partitioned by security domain identifier and network domain identifier for file-level deduplication and difference location. For each backup object, select a differentiated backup strategy and a differentiated deduplication strategy based on the directory index quadruple. The deduplication strategy prioritizes file-level deduplication and fingerprint index-only deduplication by default, forming the initial configuration of the backup scheduling plan. Step S300: Generate and execute the backup scheduling plan according to the initial configuration of the backup scheduling plan. Set the concurrency, rate limit and execution window for different security domain identifiers and different network domain identifiers respectively. At the same time, set the deduplication window and degradation rules for different data types. When the degradation conditions are met, reduce the concurrency, reduce the rate limit, narrow the deduplication window and degrade the deduplication strategy to fingerprint index deduplication only. Verify the backup results and write the verification results back to the directory entries to update the version information and object verification information, so as to obtain a traceable trusted backup version and difference location record.

[0016] In the above embodiments, the principle is referenced in the appendix. Figure 2 This embodiment constructs a complete backup object feature dataset through node metadata collection and an automated object discovery mechanism, enabling refined management of backup objects in a distributed environment. The combination of data type identifiers and four-tuple indicators provides a quantitative basis for post-policy formulation. A dual-partition fingerprint index design based on security and network domains balances file-level deduplication efficiency with difference location accuracy. The backup directory, as the core metadata center, dynamically maintains object verification information to ensure the verifiability and integrity of backup content. The combined application of differentiated backup and deduplication strategies achieves a balance between resource consumption and backup efficiency. The hierarchical mechanism for file-level and fingerprint index deduplication strategies can be flexibly adjusted according to system load; the three-level adjustment of degradation rules—concurrency, rate limit, and deduplication window—ensures the system's continuous service capability under abnormal conditions. The dual-dimensional concurrency control model of security domain and network domain, combined with the dynamic rate adjustment mechanism, effectively avoids resource contention issues caused by cross-domain backups; the windowed scheduling method enables precise control over the impact of backup tasks on business operations; the real-time verification result write-back mechanism forms a closed-loop quality control system; the continuous updating of version information and difference location records constructs a complete backup traceability chain, providing accurate version pointing and time reference for data recovery; and the dynamic maintenance of object verification information ensures that the verifiable status of backup content is always known and controllable.

[0017] This embodiment constructs a backup directory that includes object types and multi-dimensional indicators, enabling differentiated backup strategy selection for objects such as engineering, configuration, permissions, alarms, history, and inter-domain mappings. This avoids redundancy and excessively long backup windows caused by a one-size-fits-all full backup, improving backup organization efficiency and critical object protection capabilities. Security domain identifiers and network domain identifiers are bound to backup directory entries, and fingerprint indexes and deduplication references are established only within the strictly identical security domain identifier and network domain identifier range. This effectively reduces the risk of cross-domain index mixing and policy mismatch, better aligning with the partitioned operation and compliance requirements of distributed power generation control systems. File-level deduplication and fingerprint-only deduplication are used as the default priority strategies, reducing block-level deduplication while ensuring availability. The CPU / I / O disturbances introduced by equal-weight calculation enable more real-time service-friendly backup and deduplication. Concurrency, rate limits, execution windows, and deduplication windows are set according to different partitions (security domain identifier, network domain identifier). Degradation is triggered when resources are at high levels (CPU, I / O wait, insufficient bandwidth, etc.), automatically shrinking the window and switching to fingerprint-based deduplication only. This reduces the impact of backup on control services and alarm handling, improving system stability. Backup results are fingerprinted / digested and written back to directory entries, forming traceable version and verification information. This facilitates difference identification, recovery path selection, and fault tracing, reducing the risk of successful backup but failed recovery, and improving recovery reliability and operational efficiency.

[0018] The differentiated backup directory construction and deduplication scheduling method provided in this embodiment specifically includes the following steps: S1. Obtain the set of distributed nodes within the distributed control system. and for each node Collect node metadata The node metadata includes at least: node identifier. Node Roles Node type Security Domain Identifier Network domain identifier and available resource information ; Node Role It includes at least one or more of the following: engineer station, operator station, historical station, bridge / inter-domain communication node, OPC forwarding node, application server node, and database server node; the available resource information It includes at least one or more of the following: CPU utilization, memory utilization, disk I / O wait, and available bandwidth.

[0019] S2, at each node Automatically discover backup object collection The backup objects include file objects and / or database objects, and each backup object is assigned an object identifier. With object position ; Automatic backup object discovery includes: based on node role Node type as well as The matching object rule base generates a candidate list; the candidate list is subjected to existence and access permission checks; candidates that pass the checks are registered as backup objects and their object locations are recorded. The object rule base includes at least one or more of the following: file path rules, file extension rules, database / table / tablespace rules, process-configuration dependency rules, and inter-domain mapping file rules.

[0020] S3, For each backup object Perform on-site classification to obtain data type identifiers. The data type identifier includes at least one of the following or a combination thereof: engineering and deployment class, screen and configuration class, permission and responsibility area class, alarm and event class, history / time series / relational database class, and inter-domain communication and mapping class; Data type identifier The following categories are required: Engineering and Deployment: Project files, deployment files, or startup-related configurations required for project creation, deployment, and site operation; Screen and Configuration: Human-machine interface display, template / graphic element references, screen indexes, or screen-related backup data; Permissions and Responsibility Areas: Responsibility area division, user permissions, permission verification, and permission filtering policy data; Alarms and Events: Alarm group configuration, alarm filtering conditions, alarm sound / light board related configurations, or event-related data; History / Time Series / Relationship Database: History / Time Series storage, relationship database storage, and its indexes, partitions, caches, or archived data; Inter-Domain Communication and Mapping: Bridge / Inter-Domain communication configuration, inter-domain mapping, cross-domain association indexes, or KKS-related mapping configuration data.

[0021] S4, for each backup object Calculate the catalog index quadruple ,in: As a frequency of change index, As a repeatability index, To restore priority indicators, As a business disturbance sensitivity indicator; Frequency of change index In the statistics window Internal based on the number of change events With / or change the number of bytes The calculation yields the result, which satisfies the following conditions:

[0022] in Preset weighting coefficients; when the backup object is a database object, Obtained from database logs, I / O records, or incremental markers; Statistics window The timeframe is from 5 minutes to 24 hours, and the threshold is... and It meets the following applicable scope: The corresponding change intensity is 0–10 times / hour or 0–50 MB / hour; The corresponding change intensity is ≥20 times / hour or ≥200 MB / hour; Object verification information At least include object fingerprints AND / or object summary object fingerprint File-level fingerprinting is used, and the file-level fingerprint is a fingerprint obtained by calculating the hash digest of the entire object, or a fingerprint obtained by generating a segmented digest sequence of the object content according to a preset segmentation rule and then summarizing it. Repeatability index Satisfying the "strictly the same SID and the same NID" constraint: only when the constraint is satisfied and Perform a duplicate comparison between pairs of objects and calculate the duplicate score based on the object fingerprint hit ratio; Recovery priority indicators At least based on data type identifier With node roles Determine and map to a discrete set of priority levels. Among them, the categories of inter-domain communication and mapping, permissions and responsibility areas, and engineering and deployment have higher priority than the categories of history / time series / relational database. Business Disturbance Sensitivity Indicators Based on the node's real-time business attributes and available resource information This is confirmed, and when the node is in a critical process running in the real-time control network or real-time alarm processing, Select the highest sensitivity level.

[0023] S5. Build backup directory The backup directory consists of multiple directory entries. Each directory entry consists of at least:

[0024] in For version information, Verify the information for the object; Backup directory Include by Partition fingerprint index It is used for file-level deduplication and difference location, and the fingerprint index stores at least the mapping relationship between object fingerprints and object identifiers.

[0025] S6, Based on Backup Directory Select a differentiated backup strategy for each backup object. Differentiation Deduplication Strategy Among them, file-level deduplication and fingerprint-only deduplication are preferred by default in the deduplication strategy; Differentiated backup strategy Choose according to at least the following rules: when For high priority and Less than the threshold When necessary, select full backup; when Greater than the threshold When choosing, select incremental backup or fingerprint index backup only; when For historical / time-series / relational databases and For high sensitivity levels, choose a combination strategy of fingerprint index backup only + periodic archive backup; in ; Differentiated deduplication strategy Choose according to at least the following rules: When repeatability Greater than the repetition threshold At the same time, select file-level deduplication, and in the same And the same Establish reference relationships in the fingerprint index; duplicate threshold The value ranges from 0.60 to 0.95; When repeatability Not greater than the repetition threshold When selecting fingerprint index deduplication only; Among different or across different Do not share deduplication indexes, and do not create deduplication references.

[0026] S7. Generate and execute the backup scheduling plan. And identify different security domains. Different network domain identifiers Set the concurrency level, speed limit, and execution window separately, and set deduplication windows for different data types. With the downgrade rules; Deduplication window At least a time window, and with , and Association settings: When For high sensitivity levels, a smaller window is used and fingerprint indexing is prioritized for deduplication; when When the sensitivity level is low, a larger window can be used and file-level deduplication can be performed; Backup scheduling plan Including: based on recovery priority indicators Sort backup objects and assign them to priority queues and background queues; according to different Set the maximum concurrency and rate limit for each queue; and reduce the concurrency, rate limit, and deduplication window when the degradation conditions are met. Furthermore, the deduplication strategy was downgraded from file-level deduplication to fingerprint index-only deduplication; Deduplication window The value ranges from 30 seconds to 30 minutes; the number of concurrent backup tasks per node is 1 to 8. The number of concurrent backup tasks within a partition is 2 to 32; the maximum backup rate per node is 1MB / s to 80MB / s; when the CPU utilization is between 80% and 95%, the disk I / O wait is between 20% and 40%, or the available bandwidth is less than 5% to 20% of the link's rated bandwidth, a degradation is triggered, and the deduplication strategy is downgraded to fingerprint index-only deduplication and the deduplication window is reduced.

[0027] S8. Verify the backup results and write the verification results back to the directory entries. This is to update version information and object verification information for difference location and recovery; Verification includes: recalculating the object fingerprint after backup and comparing it with the object fingerprint before backup; if they match, the directory entry is marked as trusted; if they do not match, it is marked as abnormal and a re-backup or isolation process is triggered. Isolation process includes recording the reason for the abnormality and the corresponding... information.

[0028] Example 2: As Figure 3 As shown, based on Example 1, the process of calculating the quadruple of change frequency index, repeatability index, recovery priority index, and service disturbance sensitivity index in step S100 of this embodiment of the invention includes the following steps: Step S101: Obtain the preset statistical window duration, low threshold, and high threshold from the node metadata of each node, as well as the number of change events and the amount of changed bytes for each backup object automatically discovered at that point. Calculate the change frequency index for each backup object based on a weighted average of the number of change events and the amount of changed bytes. Simultaneously, generate an object fingerprint from the object verification information for each backup object. The object fingerprint is obtained by calculating a hash digest of the entire backup object, or by generating a segmented digest sequence from the backup object content according to preset segmentation rules and then summarizing it. This yields the change frequency index and object fingerprint for each backup object. Step S102: After obtaining the object fingerprint of each backup object, based on the security domain identifier and network domain identifier in the node metadata, limit the backup objects to be between this node and other nodes that have the same security domain identifier and network domain identifier; calculate the hit ratio between the object fingerprint of each backup object of this node and the object fingerprints of other backup objects with the same security domain identifier and network domain identifier, and obtain the duplication index of each backup object based on the hit ratio; no duplication comparison is performed between different security domain identifiers or different network domain identifiers; obtain the duplication index of each backup object; Step S103: Based on the obtained change frequency index, repeatability index, data type identifier of each backup object, node role, and available resource information of its node, determine the recovery priority index and business disturbance sensitivity index respectively: The recovery priority index is mapped to discrete priority levels according to the data type identifier and node role, where inter-domain communication and mapping, permission and responsibility area, and engineering and deployment are given higher priority than historical, time-series, or relational database types; the business disturbance sensitivity index is determined based on the node's real-time business attributes and available resource information such as CPU utilization, memory utilization, disk I / O wait, and available bandwidth. When the node is in the running state of a real-time control network or a real-time alarm processing critical process, the business disturbance sensitivity index takes the higher sensitivity level; finally, the change frequency index, repeatability index, recovery priority index, and business disturbance sensitivity index are combined into a quadruple.

[0029] In the above embodiments, this embodiment uses a dual-factor weighted algorithm based on change events and byte size to objectively reflect the dynamic characteristics of data and avoid bias from a single indicator. A segmented / overall dual-mode fingerprint generation mechanism adapts to different data scale scenarios, ensuring the completeness of feature extraction. A local comparison strategy under dual constraints of security domain and network domain ensures effective repeatability detection while guaranteeing isolation requirements. A matrix mapping model of data types and node roles constructs a recovery priority system that conforms to business logic. Joint analysis of real-time resource monitoring data (CPU / memory / IO / bandwidth) and business process status accurately quantifies business disturbance risks. Four-dimensional indicator coupling analysis provides a quantitative decision-making basis for subsequent strategy selection. Dual access control based on security domain and network domain ensures that cross-domain data does not generate unexpected associations. The fingerprint comparison scope limitation mechanism prevents information leakage, meets the requirements of information security classification protection, and real-time monitoring of sensitive process running states establishes a business-critical protection barrier.

[0030] Example 3: As Figure 3 As shown, based on Example 1, the process of selecting a differentiated backup strategy and a differentiated deduplication strategy for each backup object according to the directory index quadruple provided in this embodiment of the invention includes the following steps: S201: Based on the recovery priority index and change frequency index in the catalog index quadruple of each backup object, the backup objects with high recovery priority and change frequency index below the low threshold are selected as full backup objects; the backup objects with change frequency index above the high threshold are selected as incremental backup or fingerprint index only backup objects, thus obtaining the basic backup type in the differentiated backup strategy of each backup object. S202: Based on the data type identifier and the business disturbance sensitivity index in the directory index quadruple of each backup object, for backup objects whose data type identifier is historical, time-series, or relational database and whose business disturbance sensitivity index is of high sensitivity level, periodic archive backups are added to the obtained basic backup types to form a combination strategy of fingerprint index backup only plus periodic archive backup, resulting in a complete differentiated backup strategy for each backup object. S203: Based on the duplication index in the directory index quadruple of each backup object and the preset duplication threshold, backup objects with duplication index greater than the duplication threshold are selected for file-level deduplication strategy and a reference relationship is established in the fingerprint index with the same security domain identifier and the same network domain identifier; backup objects with duplication index not greater than the duplication threshold are selected for fingerprint index-only deduplication strategy; thus obtaining the differentiated deduplication strategy for each backup object.

[0031] In the above embodiments, this embodiment forms a dynamic evaluation framework oriented towards backup objects, achieving precise matching between backup strategies and deduplication strategies; establishes a multi-dimensional backup strategy decision tree, covering key parameters such as recovery priority, business sensitivity, and data characteristics; provides quantifiable deduplication decision criteria, achieving optimal allocation of storage resources through threshold comparison; ensures that backup strategies maintain a strict positive correlation with data value and business needs; and guarantees the security of deduplication operations through a dual verification mechanism of security domain and network domain.

[0032] Example 4: Based on Example 3, the process of obtaining the complete differentiated backup strategy for each backup object in step S202 of this embodiment of the invention includes the following steps: Step S2021: Obtain the basic backup type for each backup object. Based on the data type identifier and business disturbance sensitivity index of the backup object, filter out backup objects whose data type identifier is historical, time-series, or relational database and whose business disturbance sensitivity index is high sensitivity level. Associate the basic backup type of the backup object with the periodic archived backup to obtain the intermediate strategy object. Step S2022: The periodic archive backups that have been associated and marked in the obtained intermediate policy object are merged with the original fingerprint index-only backup type of the object to form a combined policy of fingerprint index-only backup plus periodic archive backup; at the same time, the original basic backup type of unmarked objects is retained to obtain the merged policy for each backup object; Step S2023: The merged strategy of each backup object is output as the complete differentiated backup strategy of the backup object; the combined strategy is output for the marked objects, and the original basic backup type is output for the unmarked objects, thus obtaining the complete differentiated backup strategy set of the full backup objects.

[0033] In the above embodiments, this embodiment achieves policy isolation between highly sensitive data and non-highly sensitive data. While maintaining the original backup performance of the system, it implements enhanced protection schemes for critical data, forming a hierarchical backup policy system. At the same time, it ensures that the policy adjustment process does not affect the backup processing flow of unmarked data.

[0034] Example 5: Based on Example 4, the process of forming a combined strategy of fingerprint index backup and periodic archive backup in step S2022 of this embodiment of the invention includes the following steps: Step S20221: Extract the fingerprint index backup portion of the basic backup type obtained after association tagging for each backup object, and at the same time extract the periodic archived backups attached to the backup object to obtain two policy constituent elements to be combined. Step S20222: Merge the fingerprint index backup part and the periodic archive backup part into a single policy description, making the periodic archive backup a supplementary action in the fingerprint index backup process, thus obtaining the intermediate form of the combined policy. Step S20223: Determine the combined intermediate form of the strategy as the combined strategy part in the final complete differentiated backup strategy of the backup object, and output it as a combined strategy of fingerprint index backup only plus periodic archive backup.

[0035] In the above embodiments, this embodiment establishes a multi-layered nested system of backup strategies, simultaneously meeting basic deduplication requirements and long-term archiving compliance requirements. It adopts a non-intrusive strategy overlay approach, maintaining the stability of the original backup process while expanding advanced functionality. This forms a strategy combination model that combines standardization and flexibility, adapting to the protection strength requirements of different types of data.

[0036] Example 6: Based on Example 5, the process of merging the fingerprint index backup portion and the periodic archive backup portion into a single policy description in step S20222 of this embodiment includes the following steps: Step S202221: Obtain the fingerprint-only backup portion of the basic backup type obtained after associating the tag for each backup object, and define it as the main policy unit; when the main policy unit is executed, it only calculates and records the object fingerprint for the backup object, and does not perform a complete data copy; at the same time, obtain the periodic archived backup portion attached to the backup object, and define this portion as the auxiliary policy unit; the auxiliary policy unit performs complete data storage on the backup object according to the preset archived period; the main policy unit and the auxiliary policy unit are encapsulated into independent policy description objects, resulting in two independent policy description objects; Step S202222: The execution result of the main policy unit serves as the starting condition for the auxiliary policy unit. The auxiliary policy unit is set to start calculating the archiving cycle timer only after the main policy unit completes fingerprint recording and generates the corresponding fingerprint index entry. At the same time, the archiving storage target location of the auxiliary policy unit is set to be bound to the fingerprint index storage location of the main policy unit within the same security domain identifier and the partition defined by the same network domain identifier. The execution order association rule and the storage location binding rule are written into the policy description to obtain a combined policy intermediate description containing time-series dependencies and location constraints. Step S202223: The main strategy unit and auxiliary strategy unit in the intermediate description of the combined strategy are merged into a composite strategy entry. The complete execution method of the composite strategy entry is defined as follows: First, perform fingerprint-only index backup, generate or update object fingerprints and store them in the fingerprint index of the corresponding partition; then, according to the preset archiving period, perform complete data archiving storage on the backup object based on the generated fingerprint information. During the archiving process, fingerprints are not recalculated, and the fingerprint results recorded by the main strategy unit are directly referenced; the composite strategy entry is output as a combined strategy description of fingerprint-only index backup plus periodic archiving backup.

[0037] In the above embodiments, while maintaining the lightweight advantage of fingerprint indexing, the periodic archiving mechanism provides physical backup protection for critical data. The two form a complementary data protection scheme through strict execution order and storage location rules. The combined strategy description can be unambiguously parsed and executed by the backup system, and a verifiable balance is achieved between data security and storage efficiency.

[0038] Example 7: Based on Example 6, the process of obtaining the intermediate description of the combined strategy including temporal dependencies and positional constraints in step S202222 of this embodiment of the invention includes the following steps: Step S2022221: Extract the execution completion flag of the main strategy unit as the start trigger condition of the auxiliary strategy unit, and define the archiving cycle timing start point of the auxiliary strategy unit as the time when the fingerprint record is completed and the corresponding fingerprint index entry is generated, so as to obtain the temporal dependency relationship between the main and auxiliary strategies. Step S2022222: Extract the security domain identifier and network domain identifier associated with the fingerprint index storage location of the main policy unit, and limit the archive storage target location of the auxiliary policy unit to the storage partition corresponding to the same security domain identifier and the same network domain identifier, so as to obtain the storage location binding relationship between the main and auxiliary policies. Step S2022223: Convert the temporal dependency relationship and storage location binding relationship into rule entries in the policy description language, and write them into the policy description structure currently being built to form a combined policy intermediate description containing temporal dependency and location constraint.

[0039] In the above embodiments, this embodiment forms a backup strategy description structure that combines determinism and security. The timing and location constraint rules contained therein can ensure that backup operations are executed in a predetermined order within a specified resource range, while meeting the operational requirements of data security and system efficiency. The intermediate description of the strategy can directly participate in the subsequent strategy deployment process and serve as the benchmark for strategy execution monitoring.

[0040] Example 8: As Figure 5 As shown, based on Examples 1-7, the differentiated backup directory construction and deduplication scheduling system provided in this embodiment of the invention includes: Backup object processing component 1 is used to obtain the set of distributed nodes in the distributed control system, collect node metadata for each node, automatically discover the set of backup objects on each node, assign an object identifier and object location to each backup object, perform on-site classification of each backup object to obtain a data type identifier, calculate a quadruple of change frequency index, repeatability index, recovery priority index and business disturbance sensitivity index, and generate object verification information to obtain a complete feature dataset of the object to be backed up. Differentiated deduplication component 2 is used to build a backup directory based on the complete feature dataset. The backup directory contains fingerprint indexes partitioned by security domain identifier and network domain identifier for file-level deduplication and difference location. It also selects a differentiated backup strategy and a differentiated deduplication strategy for each backup object based on the directory indicator quadruple. The deduplication strategy prioritizes file-level deduplication and fingerprint index-only deduplication by default, forming the initial configuration of the backup scheduling plan. Backup result verification component 3 is used to generate and execute the backup scheduling plan based on the initial configuration of the backup scheduling plan. It sets the concurrency, rate limit and execution window for different security domain identifiers and different network domain identifiers, and sets the deduplication window and degradation rules for different data types. When the degradation conditions are met, it reduces the concurrency, reduces the rate limit, narrows the deduplication window and deduplication strategy to fingerprint index deduplication only. It verifies the backup results and writes the verification results back to the directory entries to update the version information and object verification information, so as to obtain a traceable and reliable backup version and difference location record.

[0041] In the above embodiments, this embodiment achieves an intelligent backup management system through the integration of multi-dimensional technical features; the dynamic object discovery mechanism automatically establishes a node topology map, and achieves fine-grained resource perception through metadata collection, eliminating manual maintenance costs; the four-dimensional index quantification model constructs a dynamic weight system based on change frequency / repetition / recovery priority / business disturbance sensitivity to achieve adaptive allocation of storage resources; the multi-dimensional verification mechanism ensures the integrity of backup objects; and the feature dataset provides a decision-making basis for intelligent scheduling. A dual-index architecture, with security domain + network domain, enables cross-regional data fingerprint positioning, reducing redundant storage by more than 90%; the policy cascading mechanism dynamically switches between file-level deduplication and fingerprint deduplication modes, balancing processing overhead and storage efficiency; the sliding window technology intelligently adjusts the deduplication range according to data type, obtaining the optimal solution between IO throughput and storage compression ratio. The hierarchical scheduling engine ensures that the backup process does not exceed the business SLA threshold through three-dimensional control of concurrency / rate / time window; the elastic degradation strategy automatically shrinks resource usage when the system load exceeds the standard, maintaining the core business data backup channel; and the version traceability system records the complete difference evolution path, supporting fast and accurate recovery at any point in time.

[0042] The differentiated backup directory construction and deduplication scheduling system provided in this embodiment of the invention may further include: The node information acquisition module is used to obtain the node set. And collect node metadata The node metadata includes at least the following: , , , , and ; The object discovery module is used to automatically discover the set of backup objects on each node based on node metadata and the object rule base. and generate object identifiers. With object position ; The object classification module is used to generate data type identifiers for backup objects. ; The indicator calculation module is used to calculate the catalog indicator quadruple. ; The directory building module is used to build backup directories. And generate directory entries , and will and Write directory entries to form a SID+NID dual-binding directory; The fingerprint indexing module is used to generate file-level object fingerprints for backup objects. and build according to Partition fingerprint index and restricts cross-border or across different Shared deduplication index; The strategy selection module is used to select a backup strategy based on the backup directory. Deduplication strategy The default priority is to use file-level deduplication and fingerprint-based deduplication. The scheduling execution module is used to generate backup scheduling plans. , and according to Configure concurrency level, speed limit, execution window, and deduplication window. And perform downgrade when the downgrade conditions are triggered; The verification and write-back module is used to verify the backup results and write the verification results back to the directory entries. .

[0043] Figure 6 A block diagram of an exemplary electronic device suitable for implementing embodiments of the present invention is shown.

[0044] The electronic device may include a central processing unit / microprocessor / main control chip 4; and a storage medium 5 coupled to the central processing unit / microprocessor / main control chip 4 and storing computer-executable instructions therein for performing the steps of various methods of embodiments of the present invention when executed by the processor.

[0045] The central processing unit / microprocessor / main control chip 4 may include, but is not limited to, one or more processors or microprocessors.

[0046] Storage medium 5 may include, but is not limited to, random access memory (RAM), read-only memory (ROM), flash memory, EPROM memory, EEPROM memory, registers, computer storage media (e.g., hard disk, floppy disk, solid-state drive, removable disk, CD-ROM, DVD-ROM, Blu-ray disc, etc.).

[0047] In addition, the electronic device may include (but is not limited to) a data bus 6, an input / output bus / external bus / device bus 7, a display 8, and input / output devices 9 (e.g., keyboard, mouse, speaker, etc.).

[0048] The central processing unit / microprocessor / main control chip 4 can communicate with external devices (8, 9, etc.) via wired or wireless networks (not shown) through the input / output bus / external bus / device bus 7.

[0049] The storage medium 5 may also store at least one computer-executable instruction for performing the steps of various functions and / or methods in the embodiments described herein when the central processing unit / microprocessor / main control chip 4 is running.

[0050] In one embodiment, the at least one computer-executable instruction may also be compiled into or comprise a software product, wherein one or more computer-executable instructions are executed by a processor to perform the steps of the various functions and / or methods in the embodiments described herein.

[0051] Figure 7 A schematic diagram of a computer-readable storage medium according to an embodiment of the present invention is shown.

[0052] like Figure 7 As shown, the non-transitory computer-readable storage medium 11 stores instructions, such as computer-readable instructions 10. When the computer-readable instructions 10 are executed by a processor, the various methods described above can be performed. The non-transitory computer-readable storage medium includes, but is not limited to, volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-transitory non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. For example, the non-transitory computer-readable storage medium 11 can be connected to a computing device such as a computer, and then, when the computing device executes the computer-readable instructions 10 stored on the non-transitory computer-readable storage medium 11, the various methods described above can be performed.

[0053] In the embodiments provided by this invention, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between systems or units may be electrical, mechanical, or other forms.

[0054] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0055] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0056] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for executing all or part of the steps of the methods of the various embodiments of this invention through a computer device (which may be a personal computer, server, or network device, etc.). The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0057] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for constructing and deduplicating a differentiated backup directory, characterized in that, Includes the following steps: Each node in the distributed node set within the distributed control system automatically discovers backup objects, assigns a unique identifier, and collects multi-dimensional feature data including data type identifier, change frequency, redundancy, recovery priority, and business sensitivity. A partition fingerprint index is established based on both security domain and network domain dimensions, and differentiated backup and deduplication strategies are dynamically matched according to the multidimensional feature data. Differentiated concurrency control parameters and transmission strategies are set according to security domain or network domain, and the deduplication granularity and resource quota are adjusted in real time based on the system load status. End-to-end verification of backup results is performed, and version traceability information and difference records are dynamically updated to the backup directory.

2. The differentiated backup directory construction and deduplication scheduling method as described in claim 1, characterized in that, The system acquires a set of distributed nodes within the distributed control system, collects node metadata for each node, automatically discovers a set of backup objects on each node, assigns an object identifier and object location to each backup object, performs on-site classification of each backup object to obtain a data type identifier, calculates a quadruple of change frequency index, repeatability index, recovery priority index, and business disturbance sensitivity index, and generates object verification information to obtain a complete feature dataset of the object to be backed up.

3. The differentiated backup directory construction and deduplication scheduling method as described in claim 1, characterized in that, A backup directory is constructed based on the complete feature dataset. The backup directory contains fingerprint indexes partitioned by security domain identifier and network domain identifier for file-level deduplication and difference location. For each backup object, a differentiated backup strategy and a differentiated deduplication strategy are selected based on the directory indicator quadruple. The deduplication strategy prioritizes file-level deduplication and fingerprint index-only deduplication by default, forming the initial configuration of the backup scheduling plan.

4. The differentiated backup directory construction and deduplication scheduling method as described in claim 3, characterized in that, The process of selecting a differentiated backup strategy and a differentiated deduplication strategy for each backup object based on the directory metric quadruple includes the following steps: Based on the recovery priority index and change frequency index in the catalog index quadruple of each backup object, backup objects with high recovery priority and change frequency index below the low threshold are selected as full backup objects; backup objects with change frequency index above the high threshold are selected as incremental backup or fingerprint index only backup objects, thus obtaining the basic backup type in the differentiated backup strategy of each backup object. Based on the data type identifier and the business disturbance sensitivity index in the directory index quadruple of each backup object, backup objects with data type identifiers of historical, time series, or relational database and business disturbance sensitivity index of high sensitivity level are identified. By adding periodic archive backups to the obtained basic backup types, a combined strategy of fingerprint index backups and periodic archive backups is formed, resulting in a complete differentiated backup strategy for each backup object. Based on the duplication index in the directory index quadruple of each backup object and the preset duplication threshold, backup objects with duplication index greater than the duplication threshold are selected for file-level deduplication strategy and a reference relationship is established in the fingerprint index with the same security domain identifier and the same network domain identifier; backup objects with duplication index not greater than the duplication threshold are selected for fingerprint index-only deduplication strategy. Obtain the differentiated deduplication strategy for each backup object.

5. The differentiated backup directory construction and deduplication scheduling method as described in claim 4, characterized in that, The process of obtaining a complete differential backup strategy for each backup object includes the following steps: Obtain the basic backup type for each backup object. Based on the data type identifier and business disturbance sensitivity index of the backup object, filter out backup objects whose data type identifier is historical, time-series, or relational database and whose business disturbance sensitivity index is high sensitivity level. Associate the basic backup type of the backup object with the periodic archived backup to obtain the intermediate strategy object. The periodic archive backups that have been associated with and marked in the intermediate policy object are merged with the original fingerprint index-only backup type of the object to form a combined policy of fingerprint index-only backup plus periodic archive backup; at the same time, the original basic backup type of unmarked objects is retained to obtain the merged policy for each backup object; The merged strategy for each backup object is output as the complete differential backup strategy for the backup object; The marked objects output the combined strategy, while the unmarked objects output the original basic backup type, resulting in a complete set of differentiated backup strategies for all backup objects.

6. The differentiated backup directory construction and deduplication scheduling method as described in claim 5, characterized in that, The process of formulating a combined strategy of fingerprint index backup and periodic archive backup includes the following steps: Extract the fingerprint index backup portion of the basic backup type obtained after association tagging for each backup object, and extract the periodic archived backups attached to the backup object to obtain two policy components to be combined. The fingerprint index backup portion and the periodic archive backup portion are merged into a single policy description, making the periodic archive backup a supplementary action in the fingerprint index backup process, resulting in an intermediate form of the combined policy. The combined intermediate form of the strategy is determined as the combined strategy part in the final complete differentiated backup strategy of the backup object, and the output is a combined strategy of fingerprint index backup only plus periodic archive backup.

7. The differentiated backup directory construction and deduplication scheduling method as described in claim 6, characterized in that, The process of merging the fingerprint index backup portion and the periodic archive backup portion into a single policy description includes the following steps: The fingerprint index backup portion of the basic backup type obtained after associating the tag for each backup object is obtained and defined as the main policy unit. When the main policy unit is executed, it only calculates and records the object fingerprint for the backup object and does not perform a full data copy. At the same time, the periodic archived backup portion attached to the backup object is obtained and the portion is defined as the auxiliary policy unit. The auxiliary policy unit performs complete data storage on the backup object according to the preset archiving cycle; the main policy unit and the auxiliary policy unit are encapsulated into independent policy description objects, resulting in two independent policy description objects; The execution result of the main policy unit serves as the starting condition for the auxiliary policy unit. The auxiliary policy unit is set to start calculating the archiving cycle timer only after the main policy unit completes fingerprint recording and generates the corresponding fingerprint index entry. At the same time, the archiving storage target location of the auxiliary policy unit is set to be bound to the fingerprint index storage location of the main policy unit within the same security domain identifier and the partition defined by the same network domain identifier. The execution order association rule and the storage location binding rule are written into the policy description to obtain a combined policy intermediate description containing time-series dependencies and location constraints. The main strategy unit and auxiliary strategy unit in the intermediate description of the combined strategy are merged into a composite strategy entry, which clarifies the complete execution method of the composite strategy entry.

8. The differentiated backup directory construction and deduplication scheduling method as described in claim 7, characterized in that, The process of obtaining an intermediate description of a combinatorial strategy that includes temporal dependencies and positional constraints includes the following steps: Extract the execution completion flag of the main strategy unit as the start trigger condition of the auxiliary strategy unit, and define the archiving cycle timing start point of the auxiliary strategy unit as the time when the fingerprint record is completed and the corresponding fingerprint index entry is generated, so as to obtain the temporal dependency relationship between the main and auxiliary strategies. Extract the security domain identifier and network domain identifier associated with the fingerprint index storage location of the main policy unit, and limit the archive storage target location of the auxiliary policy unit to the storage partition corresponding to the same security domain identifier and the same network domain identifier, thereby obtaining the storage location binding relationship between the main and auxiliary policies; The temporal dependencies and storage location bindings are converted into rule entries in the policy description language and written into the policy description structure currently being built, forming a combined policy intermediate description that includes temporal dependencies and location constraints.

9. The differentiated backup directory construction and deduplication scheduling method as described in claim 1, characterized in that, The backup scheduling plan is generated and executed based on the initial configuration of the backup scheduling plan. Concurrency, rate limit and execution window are set for different security domain identifiers and different network domain identifiers. At the same time, deduplication window and degradation rules are set for different data types. When the degradation conditions are met, the concurrency is reduced, the rate limit is reduced, the deduplication window is narrowed and the deduplication strategy is downgraded to fingerprint index deduplication only. The backup results are verified and the verification results are written back to the directory entries to update the version information and object verification information, so as to obtain a traceable and reliable backup version and difference location record.

10. A differentiated backup directory construction and deduplication scheduling system, used to implement the differentiated backup directory construction and deduplication scheduling method as described in any one of claims 1 to 9, characterized in that, include: The backup object processing component is used to obtain the set of distributed nodes in the distributed control system, collect node metadata for each node, automatically discover the set of backup objects on each node, assign an object identifier and object location to each backup object, perform on-site classification of each backup object to obtain a data type identifier, calculate a quadruple of change frequency index, repeatability index, recovery priority index and business disturbance sensitivity index, and generate object verification information to obtain a complete feature dataset of the object to be backed up. The differential deduplication component is used to build a backup directory based on the complete feature dataset. The backup directory contains fingerprint indexes partitioned by security domain identifier and network domain identifier for file-level deduplication and difference location. It also selects a differential backup strategy and a differential deduplication strategy for each backup object based on the directory indicator quadruple. The deduplication strategy prioritizes file-level deduplication and fingerprint index-only deduplication by default, forming the initial configuration of the backup scheduling plan. The backup result verification component is used to generate and execute the backup scheduling plan based on the initial configuration of the backup scheduling plan. It sets the concurrency, rate limit and execution window for different security domain identifiers and different network domain identifiers, and sets the deduplication window and degradation rules for different data types. When the degradation conditions are met, it reduces the concurrency, reduces the rate limit, narrows the deduplication window and degrades the deduplication strategy to fingerprint index deduplication only. The backup results are verified and the verification results are written back to the directory entries to update the version information and object verification information, so as to obtain a traceable and reliable backup version and difference location record.

Images