Database Provisioning Dashboard With Snapshot and Log Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual computing systems face inefficiencies in database provisioning and protection due to complex configuration processes that require user interaction with multiple entities, leading to time-consuming and inconvenient database creation and protection, with limited snapshot capabilities resulting in lost data between captures.
Innovation Solution
A user-friendly interface for database provisioning and protection system that allows users to quickly create and register databases through a dashboard, utilizing standardized configurations and capturing transactional logs alongside snapshots to recreate any desired database state, with customizable protection schedules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users interact with multiple entities for database provisioning, then database protection can be achieved, but the process becomes time-consuming and complex
Solution Approach 1:
The patent combines multiple separate functions (database provisioning, protection system creation, and snapshot management) into a single integrated database protection system. This consolidation eliminates the need for users to interact with multiple separate entities, reducing process complexity while maintaining comprehensive database protection capabilities through unified management.
Solution Approach 2:
The database protection system is designed to perform multiple functions simultaneously: it provisions databases, creates protection instances, manages snapshots, and restores data. This multi-functional approach allows a single system to replace multiple specialized tools, simplifying the user experience while ensuring robust database protection.
2Loss of substance
If traditional snapshot capabilities are used, then storage space is reduced, but data between captures is lost
Solution Approach 1:
The system creates incremental snapshots that capture only the changes made since the previous snapshot, rather than storing complete database states. This preliminary capture of change data allows efficient storage while ensuring no data is lost, as each incremental snapshot preserves the delta information needed for complete data reconstruction.
Solution Approach 2:
The patent transforms the snapshot approach from storing complete database states to storing only incremental changes. By changing the parameter from full-state snapshots to incremental-difference snapshots, the system dramatically reduces storage requirements while maintaining complete data protection capabilities through the ability to reconstruct any past state by applying increments sequentially.
Data Source
AI summary
A system and method include receiving, by a database engine of a database system associated with a virtual computing system, a user request via a dashboard for provisioning a source database with the database system, receiving, by the database engine via the dashboard, selection of a database engine type, and receiving, by the database engine via the dashboard, selection of a Service Level Agreement (“SLA”) and a protection schedule. The system and method also include provisioning, by the database engine, the source database based upon the database engine type, creating, by the database engine, an instance of a database protection system based upon the SLA and the protection schedule, including associating the instance of the database protection system with the source database, and displaying, by the database engine, the source database within the dashboard.