Concurrent Database Snapshot Execution via Metadata Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database snapshot processes are inefficient as they require a database to be frozen during snapshot requests, preventing concurrent execution of multiple snapshot requests and impacting processing performance.
Innovation Solution
A computer-implemented method that allows for the concurrent execution of multiple snapshot requests on a selected database by handling requests in parallel, recording snapshot identifiers in metadata, and managing database records to ensure accurate snapshot creation and update handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a database is frozen during snapshot request processing, then data consistency is ensured, but concurrent execution of multiple snapshot requests is prevented and processing efficiency deteriorates
Solution Approach 1:
The patent creates a copy of the database state at a specific point in time through snapshot identifiers and metadata records, rather than freezing the actual database. Multiple snapshot requests can concurrently read from the same database while each maintains its own isolated copy of the data state, ensuring data consistency without blocking other operations.
Solution Approach 2:
The patent introduces snapshot identifiers and metadata as intermediary elements that mediate between multiple snapshot requests and the underlying database. These intermediaries track and manage snapshot state without requiring the database itself to be frozen, allowing concurrent access while maintaining isolation between snapshots.
2Measurement precision
If a database is frozen for snapshot processing, then accurate point-in-time data is captured, but response time increases and system availability decreases
Solution Approach 1:
The patent performs preliminary actions by recording snapshot identifiers in metadata before actually capturing the snapshot data. This allows the system to prepare and track multiple snapshot requests in advance without freezing the database, reducing the time each snapshot operation blocks the system while maintaining accurate point-in-time capture.
Solution Approach 2:
The patent enables continuous database operations by allowing snapshot requests to execute without freezing the database. The database remains accessible and operational throughout the snapshot process, maintaining continuity of useful actions while still capturing accurate point-in-time data through the use of snapshot identifiers and metadata tracking.
3Use of energy by moving object
If single snapshot requests are processed sequentially, then resource consumption is controlled, but productivity and throughput decrease
Solution Approach 1:
The patent segments the snapshot processing into independent, concurrently executable units by assigning unique snapshot identifiers to each request. Each snapshot operation is divided into independent stages (metadata recording, data capture, refresh) that can be executed in parallel without interfering with other snapshot requests, thereby increasing throughput while maintaining controlled resource consumption through individual snapshot management.
Solution Approach 2:
The patent merges multiple snapshot requests into a concurrent execution model where multiple snapshots can be processed simultaneously on the same or different databases. By combining resource management at the metadata level with parallel execution of snapshot operations, the system achieves higher throughput while maintaining efficient resource utilization through shared infrastructure.
Data Source
AI summary
A snapshot request for a selected database is obtained by a computing device of a computing environment. Based on obtaining the snapshot request, a snapshot of the selected database is taken. Based on taking the snapshot, a snapshot identifier is recorded in metadata of the selected database. The snapshot identifier identifies the snapshot request.