Retroactive Database Snapshots via Periodic Journaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data backup methods, such as periodic snapshots, do not efficiently allow for accessing the state of data at specific times between snapshots, making it difficult to generate custom retroactive backup snapshots.
Innovation Solution
A method that involves generating a first copy of a database, periodically querying for updates, storing these updates in a journal, and then using these updates to create a custom snapshot of the database at a specified time by updating the initial copy with updates prior to that time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If periodic snapshots are used for data backup, then data protection and disaster recovery are improved, but the ability to access data state at specific times between snapshots is lost
Solution Approach 1:
The patent segments the continuous data stream into discrete periodic snapshots (e.g., hourly) and maintains a journal of changes between snapshots. This allows the system to provide both the periodic backup capability and the ability to query custom time points by combining snapshot data with journal records, resolving the contradiction between simple periodic backup and flexible custom access.
Solution Approach 2:
The system performs preliminary actions by continuously logging all data changes in a journal between periodic snapshots. This preliminary recording of change data enables the system to later reconstruct custom snapshots at any requested time without requiring continuous full backups, thus maintaining reliability while enabling adaptability.
2Reliability
If full database backup is performed frequently, then data recovery capability is improved, but processing time and storage resources are consumed
Solution Approach 1:
The patent extracts only the necessary change information from the full database and stores it in a journal format. Instead of backing up the entire database continuously, the system extracts and logs only the delta changes (inserts, updates, deletes) between periodic snapshots. This extraction approach significantly reduces processing time and storage requirements while maintaining the ability to reconstruct complete database states.
Solution Approach 2:
The system applies partial action by performing backups at periodic intervals rather than continuously, and by storing only the essential change data in the journal rather than all data. This partial approach provides sufficient data recovery capability without the excessive processing time and storage consumption of continuous full backups.
3Measurement precision
If continuous monitoring of data changes is implemented, then custom snapshot accuracy is improved, but system complexity and API usage increase
Solution Approach 1:
The patent implements periodic action by querying the database at regular intervals (e.g., hourly) to capture snapshots and log changes. Rather than requiring continuous real-time monitoring, the system uses periodic sampling combined with journal records to achieve accurate custom snapshots. This periodic approach simplifies the monitoring mechanism while maintaining measurement precision for custom time point reconstruction.
Data Source
AI summary
Embodiments of the present invention include generating, at a first time, a first copy of a database including multiple tables, the first copy including a set of first structured text files. During a time period subsequent to the first time, queries that request updates to the tables during the time period are periodically generated and conveyed to a system managing the database. Responsively to the periodic queries, any updates to the tables and their respective update times are received and stored to a journal including one or more second structured text files. At a subsequent time, a request to generate a second copy of the database is received, the second copy including a state of the database at a specified time during the time period. The first copy of the database is updated with the updates whose update times are prior to the specified time, thereby generating the second copy.