Database Point-in-Time Restoration Using Changed Entry Reversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database restoration methods require processing entire backups, consuming significant computing resources and network bandwidth, and result in loss of data changes since the last backup, leading to reduced productivity and inefficient recovery.

Innovation Solution

A system that restores a database by processing only the changed data entries since a specified restore time, using database versions and change information to revert these entries to their initial values, thereby reducing the need to process the entire database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire database backup is loaded for restoration, then the database can be restored to a previous state, but the network bandwidth consumption and computing resource usage increase significantly

Engineering Contradiction:
Improvedatabase restoration capabilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the changed data entries from the entire database backup, rather than loading the complete backup. By identifying and extracting only the modified records since the last backup, the system reduces network bandwidth consumption and computing resource usage while still achieving reliable restoration of the database to its previous state.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the database restoration process into two parts: (1) identifying which data entries have changed since the last backup, and (2) restoring only those changed entries. This segmentation allows the system to restore the database efficiently without processing the entire backup, thereby reducing network and computing resource consumption.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the entire database backup is loaded for restoration, then the database can be restored to a previous state, but the computing resource usage increases significantly

Engineering Contradiction:
Improvedatabase restoration capabilityVSAvoidcomputing resource usage
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

The patent extracts only the changed data entries from the entire database backup, rather than loading the complete backup. By identifying and extracting only the modified records since the last backup, the system reduces network bandwidth consumption and computing resource usage while still achieving reliable restoration of the database to its previous state.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by restoring only the necessary changed data entries rather than the entire database. This partial restoration approach is sufficient to achieve the restoration goal while significantly reducing computing resource consumption compared to processing the complete backup.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If the entire database backup is loaded for restoration, then the database can be restored to a previous state, but the restoration time increases

Engineering Contradiction:
Improvedatabase restoration capabilityVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the changed data entries from the entire database backup, rather than loading the complete backup. By identifying and extracting only the modified records since the last backup, the system reduces network bandwidth consumption and computing resource usage while still achieving reliable restoration of the database to its previous state.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the database restoration process into two parts: (1) identifying which data entries have changed since the last backup, and (2) restoring only those changed entries. This segmentation allows the system to restore the database efficiently without processing the entire backup, thereby reducing network and computing resource consumption.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250355769A1Partial database restoration
Publication Date: 2025.11.20 RUBRIK INC
  • US20250355769A1 patent drawing
  • US20250355769A1 patent drawing
  • US20250355769A1 patent drawing

AI summary

Described herein is a system that restores a database by processing a portion of the database. The system restores the database to a previous state at a particular time by reverting data entries that have changed since the time to their initial values before the change. Data entries that have changed after the restore time are identified. For the data entries that have changed after the restore time, their initial values before the change are determined from various sources. The system determines a database version that is created most recently before the restore time. The system additionally identifies changes to the database between the restore time and when the database version is created. The initial values can be determined from either the database version or the changes made to the database between the restore time and when the database version is created.