Database Snapshot Selection via Log Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database backup systems face inefficiencies due to exponential storage space requirements as databases grow, with differential-based systems becoming costly and computationally inefficient over time, especially when restoring point-in-time data and managing change logs.
Innovation Solution
A system that determines the type of snapshot (full or log-based) based on log size and operation type statistics, storing snapshots efficiently as metadata or complete data, and managing change logs by calculating cumulative sizes and removing redundant entries to reduce storage usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If differential-based backup systems are used to reduce storage requirements, then storage space is reduced, but restoration cost and computational efficiency deteriorate over time
Solution Approach 1:
The patent segments the backup approach into two distinct types: full snapshots and log-based snapshots. Full snapshots provide complete database states for quick restoration, while log-based snapshots capture only changes for space efficiency. The system dynamically selects between these segments based on partition characteristics and restoration requirements, resolving the contradiction between storage efficiency and restoration speed.
Solution Approach 2:
The patent implements dynamic snapshot type selection based on real-time evaluation of partition properties, change log sizes, and restoration priorities. The system adapts its backup strategy by transitioning between full and log-based snapshots as conditions change, optimizing both storage utilization and restoration performance according to current system state.
2Reliability
If full backups are taken in response to small changes, then data protection is ensured, but storage space is wasted
Solution Approach 1:
The patent changes the parameter of backup granularity by introducing log-based snapshots that capture only the minimal necessary changes (INSERT, UPDATE, DELETE operations) rather than performing full database backups. This parameter change allows the system to maintain data protection while dramatically reducing storage space consumption when only small changes occur.
Solution Approach 2:
The patent applies local quality by treating different partitions differently based on their individual characteristics. High-priority partitions with frequent changes receive log-based snapshot treatment for efficiency, while low-priority partitions may receive full snapshots for completeness. This localized approach optimizes storage usage while maintaining appropriate data protection levels.
3Adaptability or versatility
If change logs are stored extensively for point-in-time restoration, then restoration flexibility is improved, but storage cost increases
Solution Approach 1:
The patent extracts only the essential change information needed for restoration by capturing specific database operations (INSERT, UPDATE, DELETE) in log-based snapshots. Rather than storing complete transaction logs or full backup histories, the system extracts and stores only the minimal change data required to reconstruct database states, reducing storage costs while maintaining restoration flexibility.
Solution Approach 2:
The patent applies partial action by storing change logs selectively based on partition priority and restoration requirements. Instead of maintaining comprehensive logs for all partitions indefinitely, the system retains logs only where and when needed, balancing restoration flexibility with storage cost efficiency through targeted log retention strategies.
Data Source
AI summary
Various systems and methods to efficiently store backups of partitions of a database are disclosed. An indication to take a current snapshot of a partition of the database is received. A log size and operation type statistics are determined for a portion of the change log for the partition. A snapshot type is determined for the partition based at least in part on the log size and the operation type statistics, where the snapshot type specifies a log-based snapshot or a full snapshot. The snapshot is stored as metadata indicating a point in the change log if the determined snapshot type is log-based snapshot or stored as complete data of the partition if the determined snapshot type is full snapshot.