Synchronized Test Master Using Snapshots for Database Cloning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Creating test instances of production databases for debugging and testing purposes is time-consuming and storage-intensive, as it often requires full copies of the production database, leading to excessive storage space usage when multiple test databases are in use.
Innovation Solution
A synchronized test master system that maintains a single copy of the source database, using snapshots to keep it in sync with the production database, allowing for quick synchronization and reducing storage needs by using snap clones for test databases, which are provisioned from stored snapshots without requiring a dedicated full copy of the source database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full copies of the production database are created for test databases, then test database functionality is complete, but storage space consumption increases significantly
Solution Approach 1:
The patent uses snapshots as read-only copies of the production database at specific points in time. These snapshots serve as the basis for test databases, allowing multiple test instances to share the same underlying data without requiring separate full copies. This copying approach maintains complete test functionality while dramatically reducing storage requirements.
Solution Approach 2:
The patent merges multiple test databases into a single storage space by having them all reference the same production database snapshots. Instead of allocating separate storage for each test database, the system combines them into a shared test database space that all test instances can access simultaneously, reducing total storage consumption while maintaining individual test database functionality.
2Reliability
If full copies of the production database are created for test databases, then data completeness is ensured, but time required to create test instances increases
Solution Approach 1:
The system performs preliminary actions by continuously maintaining snapshots of the production database at various points in time. When a test database is needed, the system can immediately provision a test instance from an existing snapshot without waiting for data copying, thus ensuring data completeness while minimizing creation time.
Solution Approach 2:
Instead of copying entire databases when test instances are needed, the system uses pre-existing snapshots as copies. This approach ensures that test databases have complete data from the snapshot point in time while avoiding the time-consuming process of creating full copies on demand.
3Adaptability or versatility
If multiple independent test instances are created, then testing flexibility is improved, but storage space usage becomes excessive
Solution Approach 1:
The patent makes the production database snapshots serve multiple functions: they act as the source for production data, serve as read-only references for testing, and provide the foundation for multiple independent test instances. This multi-functionality allows flexible testing with multiple independent test databases while avoiding excessive storage usage through shared snapshot references.
Solution Approach 2:
The system merges multiple test database instances into a shared storage space where they all reference the same production snapshots. This combining approach maintains the independence and flexibility of multiple test instances while dramatically reducing total storage requirements through shared underlying data.
Data Source
AI summary
Systems, methods, and other embodiments associated with a synchronized test master are described. In one embodiment, a method periodically synchronizing test master data to a source database by, at a synchronization time: modifying the test master data to reflect changes to the source database since a last synchronization time; populating a transaction log with data manipulation operations performed on the source database since a last transaction time; and taking a snapshot of the test master data. Synchronization data is derived from the transaction log that includes a snapshot time for the snapshot and a modification time for each data manipulation operation in the transaction log. The method includes storing the synchronization data and snapshot for use in generating a test database that represents a point-in-time version of the source database.