Database Cloning via Snapshot and Transactional Log Merging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtual computing systems face challenges in efficiently creating and managing databases, including lengthy database provisioning processes, reliance on multiple entities, and limitations in capturing database snapshots, which result in loss of changes between snapshot captures.
Innovation Solution
A database system within a virtual computing system that allows users to quickly create and manage databases through a user-friendly interface, automatically captures snapshots and transactional logs, and recreates database states to any point in time using these logs, enabling efficient database cloning and protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional database provisioning processes are used, then databases can be created with established methods, but the process is lengthy and requires multiple entities
Solution Approach 1:
The system performs preliminary actions by automatically capturing snapshots and transactional logs at predefined frequencies before cloning is requested. This preparation enables rapid database cloning by having the necessary data ready in advance, eliminating lengthy provisioning processes.
Solution Approach 2:
The invention creates cloned databases by copying data from source databases using captured snapshots and transactional logs. This copying mechanism enables rapid database provisioning without requiring traditional lengthy setup processes, directly improving productivity while reducing time loss.
2Reliability
If snapshots are captured at fixed intervals, then database states can be recorded periodically, but changes between snapshot captures are lost
Solution Approach 1:
The system ensures continuity by capturing both snapshots at predefined frequencies and transactional logs continuously or at high frequency. This continuous capture of transactional logs bridges the gaps between snapshots, preventing loss of data changes while maintaining reliable periodic state records.
Solution Approach 2:
The invention merges snapshot capture with transactional log capture to create a comprehensive data protection mechanism. Snapshots provide periodic state records while transactional logs capture all changes, and combining both approaches eliminates information loss between snapshots while maintaining reliability.
3Loss of information
If frequent snapshots are captured, then data loss between captures is minimized, but system resource consumption increases
Solution Approach 1:
The system applies partial action by capturing snapshots at moderate frequencies and using transactional logs to capture remaining changes. This approach avoids the excessive resource consumption of very frequent snapshots while still minimizing information loss through the complementary transactional log capture.
Solution Approach 2:
The invention changes the parameter of snapshot frequency to a moderate level and compensates by adjusting the transactional log capture frequency. This parameter adjustment optimizes the balance between minimizing data loss and reducing system resource consumption.
4Ease of operation
If manual database management is used, then users have control over database operations, but operational efficiency is reduced
Solution Approach 1:
The system implements self-service by automatically capturing snapshots and transactional logs, managing storage locations, and enabling database cloning without requiring manual intervention for these routine operations. This automation maintains user control through configurable parameters while dramatically improving operational efficiency.
Solution Approach 2:
The invention incorporates feedback mechanisms that allow users to configure snapshot frequencies, transactional log capture settings, and cloning parameters. This feedback loop maintains ease of operation by letting users control key aspects while the system handles execution, thereby improving productivity through automation.
Data Source
AI summary
A system and method include associating, by a database system of a virtual computing system, a protection schedule with each source database provisioned in the database system, the protection schedule defining a frequency of capturing snapshots and a frequency of capturing transactional logs, capturing, by the database system for each of the source databases, snapshots and transactional logs based upon the frequency of capturing snapshots and the frequency of capturing transactional logs, respectively, and receiving, by the database system, a request identifying a point in time for creating a cloned database from a first source database. The system and method also include retrieving, by the database system, the snapshots and the transactional logs corresponding to the point in time and creating, by the database system, the cloned database by combining data in storage locations identified in the transactional logs and the data in remaining storage locations identified in the snapshots.