Backup Repository Recovery Point Deletion Without Data Relocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data backup methods require inefficient data merging and relocation when deleting a recovery point, leading to increased resource usage and inefficiency.

Innovation Solution

A method and apparatus for deleting recovery points by determining target data to be deleted based on backup indexes of the target, preceding, and subsequent recovery points, without data relocation or merging, thereby optimizing resource usage and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data merging and relocation are performed when deleting a recovery point, then subsequent recovery points can continue to be used, but computing resources and storage space are occupied and efficiency is reduced

Engineering Contradiction:
Improveusability of subsequent recovery pointsVSAvoiddeletion efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts and deletes only the specific data blocks and metadata associated with the target recovery point, rather than performing comprehensive data merging and relocation. By identifying and removing only the necessary components (data blocks referenced exclusively by the target recovery point and its backup index), the system maintains deletion efficiency while ensuring subsequent recovery points remain usable.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If data merging and relocation are performed when deleting a recovery point, then subsequent recovery points can continue to be used, but more metadata is maintained and computer resources are consumed

Engineering Contradiction:
Improveusability of subsequent recovery pointsVSAvoidmetadata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts and removes only the backup index and data blocks specifically associated with the target recovery point. The backup index, which contains metadata mapping recovery points to data blocks, is deleted entirely for the target recovery point, and only the data blocks that are not referenced by any other recovery point are removed. This approach minimizes metadata maintenance complexity while preserving the integrity of subsequent recovery points.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If soft deletion and periodic garbage collection are performed, then recovery points can be deleted without immediate data relocation, but computing resources are still consumed and efficiency is reduced

Engineering Contradiction:
Improvedeletion operation simplicityVSAvoidcomputing resource consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent performs preliminary identification of data blocks and metadata that can be safely deleted immediately when a recovery point is deleted. By analyzing the backup index to determine which data blocks are referenced exclusively by the target recovery point, the system enables immediate deletion without requiring periodic garbage collection or soft deletion mechanisms, thus reducing computing resource consumption while maintaining operational simplicity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260017144A1Data backup method, medium and electronic device
Publication Date: 2026.01.15 BEIJING VOLCANO ENGINE TECH CO LTD
  • US20260017144A1 patent drawing
  • US20260017144A1 patent drawing
  • US20260017144A1 patent drawing

AI summary

A data backup method, a medium and an electronic device are provided. The data backup method includes: generating a recovery point deletion task, where the recovery point deletion task is used to instruct to delete a target recovery point in a backup repository, and the backup repository is used to manage backup data and backup indexes corresponding to respective recovery points; and delivering the recovery point deletion task to a backup work service node, and instructing the backup work service node to determine first target data to be deleted according to a first backup index corresponding to the target recovery point, a second backup index corresponding to a preceding recovery point of the target recovery point, and a third backup index corresponding to a subsequent recovery point of the target recovery point, and delete the first target data and the first backup index from the backup repository.