Database Restoration via Time-Parameter Archival
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods lack an optimal solution for efficiently recovering and restoring database records to a specific time or event occurrence, posing a challenge in maintaining database integrity.
Innovation Solution
A system and method that involve selecting and storing earlier database record revisions in an archival database, allowing for the restoration of database records to a previous state by updating the target database with selected revisions, which can be done in batch or real-time, and supports various database types including relational, NoSQL, and object-oriented databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database records are restored to a previous state using conventional methods, then database integrity is maintained, but the restoration process is inefficient and lacks optimal recovery capabilities
Solution Approach 1:
The system performs preliminary actions by continuously archiving previous versions of database records before they are overwritten or lost. This allows the system to have restoration points already prepared in advance, enabling efficient recovery without complex reconstruction processes when restoration is needed.
Solution Approach 2:
The system creates copies of database records at different time points and stores them in an archival database. These copies serve as restoration points that can be quickly applied to restore the target database to a previous state, significantly improving restoration efficiency while maintaining data integrity.
2Reliability
If all historical database record versions are retained in the target database, then complete restoration capability is achieved, but database storage space is excessively consumed
Solution Approach 1:
The system segments historical record versions by separating them into the target database (current active records) and the archival database (historical versions). This segmentation allows the system to maintain complete restoration capability while managing storage space efficiently by only keeping essential historical versions in the archive.
Solution Approach 2:
The system extracts historical record versions from the target database and stores them in a dedicated archival database. This extraction process removes unnecessary historical data from the main database, reducing storage space consumption while preserving the ability to restore to previous states when needed.
3Loss of information
If real-time updates are implemented for database record revisions, then data currentness is improved, but system complexity increases
Solution Approach 1:
The system implements self-service mechanisms where the archival database automatically captures and stores previous versions of records as they are updated in the target database. This automatic versioning occurs without requiring complex manual intervention or sophisticated coordination between systems, maintaining data currentness while limiting complexity growth.
Data Source
AI summary
A system and method are provided for the recovery and restoration of software records of a database server to record iterations previous to the current state of the selected records. This action may be taken in order to overcome the consequences of database corruption. An event-time maybe designated which is applied to select some or all of the earlier but most recent versions of each selected record. The system and method presented include a local target database for the purpose of recording software records to an archive, and may include a remote source database, from which records may be transmitted to the local target database. A restore command may be detected by the database server as sent from the remote source server, as received in an electronic message, as received via an electronics communications network, or as directly input. The local target database may have access to multiple iterations or versions of a software record including the original record version as stored in an archive, and may, upon instruction or command, revert to a previous iteration of a software record stored in the archive if corruption of later iterations is suspected. Alternatively or additionally, the local target database may not be restored with earlier versions of records but the remote source database may be restored with the selected record versions. The software records may optionally be updated in a batch method, or may alternatively be updated in real time, as the software records are created.