Parallel Database Backup via Byte-Range Asset Locks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database backup processes are inefficient due to sequential execution of backup operations, which prolongs the database backup execution time and reduces protection efficiency.

Innovation Solution

A method and system that enable concurrent execution of backup operations by using an asset lock file to manage byte-range locks, allowing multiple backup operations to be performed in parallel, thereby increasing efficiency and reducing execution time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If sequential backup operations are performed, then data protection reliability is maintained, but backup execution time increases and protection efficiency decreases

Engineering Contradiction:
Improvebackup protection efficiencyVSAvoidbackup execution time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the backup process into distinct byte-range operations, allowing different portions of the database to be backed up concurrently. By dividing the backup task into smaller byte-range segments that can be independently locked and processed in parallel, the system achieves faster overall backup execution while maintaining data integrity through proper lock management on the asset lock file.

Inventive Principle:
Principle #1Segmentation

2Loss of time

If concurrent backup operations are enabled, then backup execution time decreases and efficiency increases, but risk of data inconsistency increases without proper locking

Engineering Contradiction:
Improvebackup execution timeVSAvoiddata consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent introduces an asset lock file as an intermediary mechanism that mediates between concurrent backup operations and data consistency requirements. The byte-range locks on the asset lock file act as intermediaries that coordinate access to the database during parallel backup operations, ensuring that data reads are consistent while allowing multiple backup processes to execute simultaneously without corrupting the source data.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If byte-range locks are acquired for backup operations, then concurrent execution is enabled and efficiency improves, but system complexity increases due to lock management

Engineering Contradiction:
Improveparallel backup efficiencyVSAvoidlock management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the locking complexity from the main backup operation logic and centralizes it in dedicated lock acquisition and release routines that operate on the asset lock file. By separating the lock management functionality from the backup data processing, the system enables concurrent backup operations with reduced complexity in the core backup logic, as the lock handling is encapsulated in standardized routines that manage byte-range locks systematically.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11455213B2Method and system for parallel data transmission and cooperating backups
Publication Date: 2022.09.27 EMC IP HLDG CO LLC
  • US11455213B2 patent drawing
  • US11455213B2 patent drawing
  • US11455213B2 patent drawing

AI summary

In general, the invention relates to a method for performing operations. The method includes protecting a database includes detecting a first trigger event for a first backup operation targeting an user asset of a client device of client devices, wherein the first trigger event specifies first metadata associated with the first backup operation, acquiring a first byte-range lock associated with a backup type specified in the first metadata in an asset lock file associated with the user asset, acquiring a second byte-range lock of the asset lock file that is associated with a storage mounting operation, after acquiring the first byte-range lock and the second byte-range lock, mounting a backup storage to the client device using the first metadata, unlocking the second byte-range lock, and performing, after unlocking the second byte-range lock, the first backup operation on the user asset.