Database File Backup Using Subfile Segmentation and Fingerprint Sync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud backup methods fail to optimize backup performance for database (DB) files due to their frequent changes, resulting in prolonged backup times as the entire DB file is repeatedly uploaded, despite only specific portions needing updates.
Innovation Solution
The method segments DB files into local subfiles based on file blocks, distinguishing between subfiles with and without corresponding server-side subfiles or content inconsistencies, and uploads only these subfiles, using file IDs and fingerprints for efficient comparison and updating.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire DB file is uploaded during each backup, then complete data synchronization is achieved, but backup time is excessively long and backup efficiency deteriorates
Solution Approach 1:
The patent segments the DB file into multiple subfiles based on file blocks. Each subfile corresponds to one or more file blocks, allowing the system to identify and upload only the specific subfiles that have changed or are missing, rather than uploading the entire DB file. This segmentation enables precise control over backup data transmission.
Solution Approach 2:
The patent extracts only the necessary subfiles from the DB file for upload. By comparing local subfiles with server-side subfiles using file fingerprints, the system identifies and extracts only those subfiles that need to be uploaded (either because they don't exist on the server or their content has changed), eliminating unnecessary data transmission.
2Reliability
If the entire DB file is uploaded during each backup, then data completeness is ensured, but the amount of data transmitted is excessive
Solution Approach 1:
The DB file is divided into multiple subfiles based on file blocks, enabling the system to transmit only the specific subfiles that have changed or are missing. This segmentation reduces the volume of transmitted data while ensuring that all necessary changes are captured and uploaded to maintain data completeness.
Solution Approach 2:
The patent implements partial action by uploading only the necessary subfiles rather than the entire DB file. Through fingerprint comparison, the system determines exactly which subfiles need to be uploaded and transmits only those, avoiding excessive data transmission while ensuring complete synchronization of changed data.
3Ease of manufacture
If conventional cloud backup methods are used for DB files, then simplicity of implementation is maintained, but backup performance fails to improve
Solution Approach 1:
The patent segments the DB file into subfiles based on file blocks and implements a comparison mechanism using file fingerprints. This approach maintains implementation simplicity by building upon conventional backup frameworks while adding segmentation and fingerprint comparison capabilities, resulting in significantly improved backup performance through selective upload of only changed subfiles.
Data Source
AI summary
A database (DB) file backup method and apparatus, and an electronic device are provided. The method includes: an electronic device segments a DB file, to obtain local subfiles of the DB file, obtains a first local subfile from the local subfiles, and uploads the first local subfile to a server, where the first local subfile is a local subfile that does not have a corresponding server side subfile in the server; and/or obtains a second local subfile from the local subfiles, and uploads the second local subfile to the server, where the second local subfile is a local subfile that has a corresponding server side subfile in the server and that corresponds to a content comparison result indicating that the second local subfile and the corresponding server side subfile are inconsistent. In this case, a local subfile whose content does not change is not uploaded each time.