Database Backup Timeline Visualization for Point-in-Time Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database restore methods fail to restore databases to their latest state before an error occurred, resulting in lost changes and are resource-intensive, with backups consuming significant network bandwidth and processing resources, and making the database inaccessible during recovery.
Innovation Solution
A system that stitches together database backups and log backups to provide a visual timeline view, allowing users to select recoverable time ranges for automated or manual restore, using a graphical user interface to validate Recovery Point Objectives (RPO) and Service Level Agreements (SLAs), and generates scripts for automated recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If periodic database backups are created to protect information, then data protection is improved, but the database cannot be restored to its latest state before an error occurred
Solution Approach 1:
The patent segments the backup process into two components: full database backups (capturing complete data at specific time points) and transaction log backups (capturing incremental changes between backups). This segmentation allows the system to restore to any point in time between full backups by applying transaction logs, thereby resolving the contradiction between periodic backup protection and the ability to restore to the latest state.
Solution Approach 2:
The patent performs preliminary actions by continuously capturing transaction logs during normal database operation, so that when an error occurs, the most recent changes are already recorded in the logs. This preliminary capture of changes enables restoration to the latest state without requiring continuous full backups, thus maintaining both protection and recoverability.
2Reliability
If full database backups are loaded to restore the database, then data recovery is achieved, but significant network bandwidth and processing resources are consumed
Solution Approach 1:
The patent extracts only the necessary change information (transaction logs) rather than transferring the entire database backup. By taking out only the incremental changes that occurred since the last full backup, the system dramatically reduces network bandwidth consumption and processing resources required for restoration, while still achieving complete data recovery.
Solution Approach 2:
Instead of performing a complete full backup restoration (excessive action), the patent applies only the minimal necessary transaction log records (partial action) that contain the changes since the last full backup. This partial restoration approach achieves the same recovery goal with significantly reduced resource consumption.
3Reliability
If database restoration is performed, then data is recovered to a previous state, but the database becomes inaccessible during recovery reducing productivity
Solution Approach 1:
The patent performs preliminary backup actions during normal database operation, capturing transaction logs in the background without blocking user access. This allows the restoration process to occur using minimal resources and potentially in a way that maintains database accessibility, thereby reducing the impact on productivity while ensuring data recovery capability.
Data Source
AI summary
A computer-implemented method at a data management system comprises; retrieving start and end times of a backup of a database; retrieving time stamps of log backups of the database; retrieving sequence numbers of the log backups; generating a graphical user interface illustrating a timeline of availability of database restoration and unavailability; making a second backup of the database; illustrating, on the graphical user interface during the making, pending availability of the second database backup; receiving a command to restore the database at an available time as illustrated by the graphical user interface; and restoring the database.