Database Recovery Using Change Markers and Transaction Logs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for managing and operating domain name registries, particularly with the introduction of new generic top-level domains, lack efficient systems for database recovery and transaction logging, leading to inefficiencies in managing business rules and ensuring data integrity.
Innovation Solution
A method and system for database recovery and transaction logging that involves extracting a last change marker from a backup database, copying and sorting transaction logs, and replaying identified transactions to generate a recovered database, while also implementing a business logic framework with Inversion of Control, Dependency Injection, and Aspect-Oriented Programming to manage business rules and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional database recovery methods are used, then the recovery process is simple, but data integrity and reliability are compromised
Solution Approach 1:
The system performs preliminary actions by continuously logging transactions and maintaining change markers before database failures occur. Transaction logs are recorded with change markers that track database state changes, enabling reliable recovery without complex real-time monitoring during failure events.
Solution Approach 2:
The patent creates a copy of the database recovery process by using transaction logs and change markers to reconstruct database state. Instead of complex real-time replication, the system copies transaction information and applies it during recovery, simplifying the overall system architecture while maintaining data integrity.
2Reliability
If comprehensive transaction logging is implemented, then data integrity is improved, but system complexity and storage requirements increase
Solution Approach 1:
The system extracts only the essential information needed for recovery by using change markers that point to specific database records. Instead of logging complete transactions, the system extracts change marker references that indicate what changed and where, significantly reducing log volume while maintaining full recovery capability.
Solution Approach 2:
The patent changes the parameter of transaction logging from complete transaction records to change marker references. This parameter transformation reduces the quantity of data stored in transaction logs while maintaining the ability to reconstruct database state for recovery operations.
3Productivity
If efficient database recovery is implemented, then productivity is improved, but device complexity increases
Solution Approach 1:
The database recovery system performs self-service by automatically using change markers and transaction logs to reconstruct database state without external intervention. The system self-manages recovery operations through predefined mechanisms, improving productivity while avoiding the complexity of manual recovery procedures and external monitoring systems.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A method of recovering a database includes providing a computer having a processor and providing a backup database including a last change marker. The method also includes extracting, using the processor, the last change marker from the backup database and providing transaction logs. Each transaction of the transaction logs includes input data, processed data, and a change marker. The method further includes sorting, using the processor, the transactions of the transaction logs using the change markers, replaying, using the processor, one or more of the transactions of the transaction logs, and generating a recovered database.