Logical Log Database Updates for Low-Bandwidth Disaster Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud service systems waste significant network bandwidth and storage resources on synchronizing data between primary and disaster recovery sites due to the need to transmit entire rows of modified data, especially when the sites are geographically distant.
Innovation Solution
Generate a logical log file containing minimal information to update data at the disaster recovery site, including row identifiers, hash values, or bitmaps to reduce data amount, and utilize a protection site with low latency for quick data transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If entire rows of modified data are synchronized between primary and disaster recovery sites, then data reliability and completeness are improved, but network bandwidth consumption and storage resource waste increase significantly
Solution Approach 1:
The patent segments the data synchronization process by identifying and transmitting only the modified columns (first data) rather than entire rows. The logical log file structure separates row identification information from the actual modified data, enabling selective transmission of only necessary data portions to the disaster recovery database.
Solution Approach 2:
The patent extracts only the essential modified data elements from the complete row structure. By using the logical log file to store only the first data (modified columns) along with row identifier information, the system extracts and transmits only the necessary data for disaster recovery while eliminating redundant data transmission.
2Reliability
If entire rows of modified data are transmitted to the disaster recovery site, then data completeness is ensured, but storage resources are wasted
Solution Approach 1:
The logical log file is segmented into distinct components: row identifier information (first information) and modified data (second data). This segmentation allows the disaster recovery database to store only the necessary modified data portions rather than complete row duplicates, reducing storage resource consumption while maintaining data completeness for recovery operations.
Solution Approach 2:
The patent extracts only the modified data portions from complete rows and stores them in the logical log file. The disaster recovery database uses this extracted data to update only the necessary columns, eliminating the need to store complete row data and thereby reducing storage resource waste.
3Loss of energy
If minimal information is transmitted in the logical log file, then network bandwidth and storage requirements are reduced, but data synchronization complexity increases
Solution Approach 1:
The patent introduces a logical log file as an intermediary structure between the primary database and disaster recovery database. This log file serves as a mediator that organizes the transmission of minimal necessary information, handling the complexity of selective data transmission and ensuring proper data synchronization without requiring complex direct communication protocols.
Solution Approach 2:
The logical log file structure incorporates feedback mechanisms through row identifier information and modified data markers. This feedback structure enables the receiving system to accurately identify which rows and columns need updating, simplifying the synchronization process despite the minimal data transmission by providing clear identification and context information.
Data Source
Figure 1~3
Figure 4~6
Figure 7~8
AI summary
This application discloses a data update method, apparatus, and system, and a storage medium, and pertains to the database field. The method is applied to a cloud service system, the cloud service system includes a primary site and a disaster recovery site, a primary database in the primary site includes a first primary data set, and a disaster recovery database in the disaster recovery site includes a first disaster recovery data set that is the same as the first primary data set. The method includes: modifying at least one piece of first data in the first primary data set into at least one piece of second data; generating a logical log file, where the logical log file includes first information, second information, and the at least one piece of second data, the first information indicates the first primary data set, and the second information indicates the at least one piece of first data; and sending the logical log file to the disaster recovery site, where the logical log file is used to indicate the disaster recovery site to update the at least one piece of first data in the first disaster recovery data set to the at least one piece of second data. In this application, network bandwidth resources can be saved.