Data Backup Block Size Optimization via Dynamic Sizing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data backup systems face challenges in selecting an optimal block size for full and incremental backups, balancing granularity, deduplication, and cost effectiveness, which affects efficiency and cost in data recovery processes.

Innovation Solution

A system that dynamically selects block sizes for full and incremental backups based on the type of backup, using a first block size for full backups and a substantially smaller second block size for incremental backups, with the ability to upload data to backup media and update block maps to track changed blocks, facilitating efficient deduplication and cost reduction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a smaller block size is selected for backup, then tracking modifications at high granularity is improved and incremental backup size is reduced, but data write request cost and data storage cost increase

Engineering Contradiction:
Improvegranularity of modification trackingVSAvoiddata storage cost
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system dynamically adjusts block size based on backup type: using a first block size for full backups and a second (smaller) block size for incremental backups. This dynamic adaptation resolves the contradiction by selecting appropriate granularity levels contextually, achieving high modification tracking precision for incremental backups while managing storage costs through selective application.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the block size parameter according to backup operation type. By switching between different block size values (first block size vs. second block size) based on whether performing full or incremental backup, the system optimizes both modification tracking granularity and storage cost efficiency.

Inventive Principle:
Principle #35Parameter changes

2Quantity of substance

If a large block size is selected for backup, then data write request cost and data storage cost are reduced, but tracking modifications at high granularity deteriorates and incremental backup effectiveness decreases

Engineering Contradiction:
Improvedata storage costVSAvoidincremental backup effectiveness
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system dynamically selects block size based on backup type requirements. For incremental backups, it uses a smaller second block size to maintain high effectiveness in tracking modifications, while for full backups it uses a larger first block size to reduce storage costs, thus resolving the contradiction dynamically.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the block size parameter according to the backup operation being performed. By switching between first block size (for full backups) and second block size (for incremental backups), it achieves cost efficiency when needed while maintaining backup effectiveness when required.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If full data backups are performed frequently, then data recovery reliability is improved, but backup time and costs increase significantly

Engineering Contradiction:
Improvedata recovery reliabilityVSAvoidbackup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system segments backup operations into two distinct types: full backups and incremental backups. By dividing the backup strategy into these segments, it achieves reliable data recovery through periodic full backups while reducing overall backup time and costs through more frequent, faster incremental backups that only capture changes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements periodic full backups combined with interlaced incremental backups. This periodic action pattern ensures data recovery reliability through regular complete backups while minimizing time loss by using faster incremental backups in between, resolving the contradiction between reliability and time consumption.

Inventive Principle:
Principle #19Periodic action

4Loss of time

If incremental backups are performed between full backups, then backup time and costs are reduced, but selecting appropriate block size becomes more challenging to achieve efficient data deduplication

Engineering Contradiction:
Improvebackup timeVSAvoidblock size selection complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system dynamically determines block size based on backup type, automatically selecting the appropriate block size (first or second) based on whether performing a full or incremental backup. This dynamic selection simplifies the complexity by removing the need for manual or complex automated block size optimization, as the system adapts block size automatically according to backup operation requirements.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11449392B2Data backup system with block size optimization
Publication Date: 2022.09.20 DRUVA INC
  • US11449392B2 patent drawing
  • US11449392B2 patent drawing
  • US11449392B2 patent drawing

AI summary

A system for data backup is provided. The system includes a memory having computer-readable instructions stored therein and a processor configured to execute the computer-readable instructions to receive a request for full data and/or incremental backup for a volume and to perform a full backup of the volume based on a first block size in response to a full data backup request. The processor is configured to generate a digital fingerprint of the full backup and determine if the full backup exists on a backup media based on the generated digital fingerprint and to upload the full backup to the backup media if it is determined that the first backup is unavailable on the backup media and perform an incremental backup of the volume based on a second block size in response to an incremental backup request. The second block size is substantially smaller than the first block size.