Distributed Data Backup Consistency via Transaction Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed data structures, generating a backup copy while ensuring data consistency between replicas and interrelated key-value pairs across network nodes is complicated due to inconsistent updates, leading to potential data inconsistencies.
Innovation Solution
A method that uses transaction identifiers to manage data consistency by performing transaction steps, generating backup copies, and ensuring that changes are aligned with specific transaction levels, using timestamps to maintain point-in-time consistency between backup copies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the distributed hash table is constantly updated during backup copy generation, then the data structure remains dynamic and up-to-date, but data consistency between replicas and interrelated key-value pairs deteriorates
Solution Approach 1:
The system performs preliminary actions by recording transaction identifiers at the moment backup generation is requested, before actual updates occur. This allows the system to later filter and select only those updates that occurred before the backup point in time, ensuring consistency without stopping updates during backup generation.
Solution Approach 2:
Transaction identifiers serve as an intermediary mechanism between the continuous update process and the backup generation process. By attaching transaction identifiers to each update operation and comparing them with the backup point in time, the system mediates between ongoing updates and consistency requirements, allowing both to coexist.
2Adaptability or versatility
If updates are performed on interrelated key-value pairs distributed across different network nodes, then the distributed nature of the system is maintained, but ensuring consistency across all nodes becomes more complex
Solution Approach 1:
The system implements feedback by having each network node report its transaction identifiers to a central coordinator or to each other. This feedback mechanism allows the system to determine which nodes have completed which transactions, enabling consistent snapshot generation across the distributed network without complex coordination protocols.
Solution Approach 2:
The system changes the parameter of tracking from direct data value synchronization to transaction identifier comparison. By using transaction identifiers as a parameter to determine consistency state, the system simplifies the complexity of managing distributed updates while maintaining the distributed storage capability.
3Reliability
If a snapshot is generated at a specific point in time, then data consistency is achieved, but the system cannot reflect subsequent updates that occurred before the backup completion
Solution Approach 1:
The system records the backup point in time (transaction identifier) in advance, before the actual backup process completes. This preliminary recording allows the system to continuously monitor incoming updates and selectively include only those that occurred before the recorded point in time, eliminating update lag while maintaining consistency.
Solution Approach 2:
The system maintains continuous monitoring of transaction identifiers during and after backup generation. This continuous action allows the system to immediately incorporate valid updates (those with transaction identifiers before the backup point) while filtering out invalid ones, ensuring both consistency and minimal update lag.
Data Source
Figure 1~2
Figure 3
AI summary
The present invention relates to a method for enhancing the generation of a backup copy of data items of a distributed data structure, wherein the data items are stored on a number of network nodes of a computer network, wherein the number of network nodes include a first and a second network node, wherein the data items include a data item and a further data item, wherein the data item and the further data item are interrelated, wherein the data item is stored on the first network node, wherein the further data item is stored on the second network node, wherein the method comprises the steps of: -- performing, by the computer network, a first transaction step, wherein the data item of the first network node is updated such that a first data item is generated, wherein the further data item of the second network node is updated such that a further first data item is generated, wherein a first transaction identifier is stored on the first and second network node, wherein the first transaction identifier is related to an identification of the first transaction step, -- performing, by the computer network, a second transaction step, wherein the further first data item of the second network node is updated such that a further second data item is generated, wherein a second transaction identifier is stored on the second network node, wherein the second transaction identifier is related to an identification of the second transaction step, -- performing, by the computer network, a backup step, wherein a backup copy of the first data item is generated on the first network node, wherein a further backup copy of the further second data item is generated on the second network node, -- performing, by the computer network, a consistency step such that data consistency is realized between the backup copy and the further backup copy in dependence of the first and second transaction identifier.