Database Restore Using Sorted Backup Objects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data protection systems face inefficiencies in performing simultaneous full and incremental backups, leading to delays and challenges in data recovery, as well as confusion during restore operations due to potential deadlocks and incorrect application of incremental changes.

Innovation Solution

A system and method that allow simultaneous full and incremental backups, with a process to efficiently locate and restore backup data by sorting backup objects based on timestamps and identifying the correct full and incremental backups to ensure accurate restoration to a point-in-time, using a server and storage device architecture that facilitates efficient data retrieval and reconstruction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full backups are performed completely before incremental backups, then data protection completeness is improved, but backup time and resource consumption increase

Engineering Contradiction:
Improvedata protection completenessVSAvoidbackup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by capturing incremental changes before the full backup completes. The backup system records incremental backup data during the ongoing full backup process, so that when restoration is needed, the incremental changes are already captured and can be applied to restore data to a point-in-time during the full backup operation.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If simultaneous full and incremental backups are performed, then backup efficiency is improved, but restore complexity and potential deadlocks increase

Engineering Contradiction:
Improvebackup efficiencyVSAvoidrestore complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary mechanism - a backup system that acts as a mediator between the primary storage device and the backup storage device. This intermediary manages the complexity of simultaneous operations by coordinating full and incremental backup processes, tracking which incremental changes correspond to which full backup, and providing a structured approach for restoration that resolves the complexity of simultaneous operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If incremental backups are applied to full backup copies during restoration, then data recovery speed is improved, but correctness of restoration decreases due to potential deadlock and confusion

Engineering Contradiction:
Improvedata recovery speedVSAvoidrestoration correctness
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system implements feedback mechanisms where the backup system continuously tracks and records which incremental backup data corresponds to which full backup. This feedback loop ensures that during restoration, the system can accurately match incremental changes to their corresponding full backup, preventing deadlocks and ensuring correctness while maintaining fast recovery speeds.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9483485B1Restore database from backup system where full and incremental backups are performed simultaneously
Publication Date: 2016.11.01 EMC IP HLDG CO LLC
  • US9483485B1 patent drawing
  • US9483485B1 patent drawing
  • US9483485B1 patent drawing

AI summary

This disclosure relates to a method, article of manufacture, and apparatus of restoring a database allowing simultaneous full and incremental backups. In some embodiments, this includes receiving, by a server, a request for restoring as of a restore point-in-time, in response to the request, retrieving by the server a set of backup objects, sorting the set of backup objects in descending order, locating a first incremental backup in the set of backup objects based on the restore point-in-time and a first incremental backup start time associated with the first incremental backup, locating a full backup in the set of backup objects based on the first incremental backup start time, a full backup start time and a full backup end time associated with the full backup, storing the full backup and the first incremental backup in a list of restoring objects, and sending, by the server, the list of restoring objects.