Cross-Database Recovery Control System Using Common Version Time
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data protection schemes for relational and non-relational databases operate independently, making it difficult to restore associated data across both types of databases due to differences in structure and versioning consistency.
Innovation Solution
A recovery control system identifies data versions from relational and non-relational databases based on a common version time, coordinating the restoration of data versions between the two systems to ensure consistent recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data protection schemes operate independently for relational and non-relational databases, then each database type can be protected using its own versioning system, but it becomes difficult to restore associated data across both database types due to structural differences and versioning inconsistency
Solution Approach 1:
The patent merges independent protection schemes for relational and non-relational databases into a unified cross-database protection system. The system combines versioning data from both database types into a single protection framework that uses a common timestamp mechanism, allowing coordinated restoration of associated data across different database types through a single operation.
Solution Approach 2:
The patent creates a universal protection system that handles both relational and non-relational databases through a single cross-database protection scheme. The system uses a common timestamp-based version identification mechanism that works across different database types, enabling the same restoration process to be applied universally to both relational and non-relational data.
2Adaptability or versatility
If separate versioning systems are used for relational and non-relational databases, then each system can be optimized for its specific database type, but versioning consistency between the two systems becomes difficult to maintain
Solution Approach 1:
The patent introduces a homogeneous timestamp-based version identification mechanism that is applied uniformly across both relational and non-relational databases. This common versioning approach uses identical timestamp formats and comparison logic for both database types, ensuring versioning consistency while maintaining adaptability to different database structures through the abstract timestamp interface.
3Adaptability or versatility
If data is stored in both relational and non-relational databases with different structures, then the system can leverage the strengths of both database types, but restoring data to a consistent state across both types becomes complex
Solution Approach 1:
The patent extracts the version identification logic from database-specific operations and isolates it into a separate timestamp comparison mechanism. By separating the version identification function from the database restoration process, the system simplifies restoration complexity while maintaining the ability to handle different database structures, as the timestamp comparison operates independently of database-specific details.
Data Source
AI summary
Embodiments disclosed herein provide systems, methods, and computer readable media for recovering data across relational and non-relational databases. In a particular embodiment, a method includes identifying first data having a first version time in a first version store storing data versions from a relational database. Based on the first version time, the method provides identifying second data, associated with the first data, in a second version store storing data versions from a non-relational database. The method further provides recovering the first data to the relational database and the second data to the non-relational database.