Database Replication Copy for Clean Shutdown Snapshots
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database replication methods, such as snapshot techniques, often result in data being in a 'dirty shutdown' state, making it inaccessible without shutting down the native database application, which is impractical and costly.
Innovation Solution
A system and method for performing substantially continuous replication of a database, allowing for the generation of snapshots in a clean shutdown state without shutting down the native database application, enabling direct access and manipulation of replicated data using standard APIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If snapshot techniques are used to preserve read-only copy of database data, then data protection and point-in-time imaging are improved, but the data is in a dirty shutdown state and inaccessible without shutting down the native database application
Solution Approach 1:
The patent introduces a replication copy as an intermediary between the source database and the snapshot. The replication copy receives updates from the source database through transaction log replay, allowing snapshots to be taken from the replication copy instead of the source. This intermediary enables snapshots to be in a clean shutdown state while the source database remains online and accessible.
Solution Approach 2:
The system separates the database into source database and replication copy, allowing independent operation. The replication copy can be snapshot without affecting the source database, enabling data protection while maintaining accessibility of the original system.
2Manufacturing precision
If the native database application is shut down to perform snapshot, then clean shutdown state is achieved, but system availability and productivity are reduced
Solution Approach 1:
The system performs preliminary replication of data to a replication copy before taking snapshots. This preliminary action ensures that the replication copy contains up-to-date data that can be snapshotted without shutting down the source database, maintaining both data integrity and system availability.
Solution Approach 2:
The replication process operates continuously in the background, maintaining an up-to-date copy of the database. This continuous replication allows snapshots to be taken at any time without interrupting the source database operations, ensuring uninterrupted productivity.
3Reliability
If data shadowing and mirroring are used to create copies, then data protection is improved, but processing power consumption and storage space requirements increase significantly
Solution Approach 1:
The patent uses a replication copy that is updated through transaction log replay rather than continuous data shadowing or mirroring. This copying approach reduces processing overhead compared to real-time shadowing, as updates are applied in batches through log replay rather than continuously synchronizing every data change.
Data Source
AI summary
Systems and methods for replicating database data and generating read-only copies of the replicated data in a clean shutdown state. For example, systems can include a tracking module (e.g., a filter driver) that monitors transactions from a database application to a source storage device to generate log entries having at least one marker indicating a known good state of the application. The systems further include a computer coupled to a target storage device comprising a database and log files. The computer processes the transactions, based on the log entries, to replicate data to the target storage device; performs a first snapshot on data stored in the database and log files; replays into the database data stored in the log files; performs another snapshot on the database; and reverts the database back to a state in which the database existed at the time of the first snapshot.