Block-Level Data Migration for Large Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems face challenges in efficiently migrating and restoring large data files, which can be costly and time-consuming, often requiring knowledge of the application that created the data and involving resource-intensive processes.

Innovation Solution

The system migrates data objects by transferring segments, portions, or increments based on criteria such as time or age, using block-based or chunk-based methods, allowing for transparent data migration and restoration without requiring user input, and maintaining data in primary storage while moving less frequently accessed blocks or chunks to secondary storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional file-based data migration is used, then data structure and application format are maintained, but migration cost and time increase significantly for large files

Engineering Contradiction:
Improvedata structure maintenanceVSAvoidmigration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent divides data objects into blocks or chunks that can be independently migrated. Instead of migrating entire files, the system transfers only specific blocks or chunks based on access patterns and usage criteria, significantly reducing migration time and cost while maintaining the ability to reconstruct complete data objects with their original structures.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and migrates only the necessary portions of data objects rather than moving complete files. By identifying and transferring specific blocks or chunks based on access patterns, the system reduces the overall migration volume and time while preserving the ability to restore complete data objects when needed.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If entire large files are restored, then complete data availability is achieved, but restoration cost and time become excessive

Engineering Contradiction:
Improvedata availabilityVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments data objects into manageable blocks or chunks that can be selectively restored. When data recovery is needed, the system can restore only the specific blocks or chunks that are required, rather than recovering entire large files, thereby reducing restoration time and resource consumption while maintaining complete data availability when needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by restoring only the necessary portions of data objects rather than complete files. The system identifies and restores only the specific blocks or chunks that are needed, avoiding the excessive action of restoring entire large files, thus reducing time and resource consumption while achieving sufficient data recovery.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If block-based or chunk-based migration is implemented, then migration efficiency improves, but system complexity increases

Engineering Contradiction:
Improvemigration efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal data migration system that handles multiple data object types and access patterns through a unified block or chunk-based approach. The system provides multi-functional capabilities including migration, restoration, and data management operations that work across different data types, reducing the need for separate specialized systems and thereby managing complexity while improving efficiency.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Loss of time

If selective block or chunk migration is performed, then cost and time are reduced, but knowledge of application structure is required

Engineering Contradiction:
Improvemigration timeVSAvoidapplication knowledge requirement
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent enables the data migration system to operate autonomously by using metadata and access patterns to automatically identify which blocks or chunks should be migrated. The system serves itself by making intelligent decisions about data selection and migration based on stored information about data access patterns and usage criteria, eliminating the need for manual intervention or deep application knowledge while maintaining efficient selective migration.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10572445B2Transferring or migrating portions of data objects, such as block-level data migration or chunk-based data migration
Publication Date: 2020.02.25 COMMVAULT SYSTEMS INC
  • US10572445B2 patent drawing
  • US10572445B2 patent drawing
  • US10572445B2 patent drawing

AI summary

A system and method for migrating data objects based on portions of the data objects is described. The system may transfer portions of files, folders, and other data objects from primary storage to secondary storage based on certain criteria, such as time-based criteria, age-based criteria, and so on. An increment may be one or more blocks of a data object, or one or more chunks of a data object, or other segments that combine to form or store a data object. For example, the system identifies one or more blocks of a data object that satisfy a certain criteria, and migrates the identified blocks. The system may determine that a certain number of blocks of a file have not been modified or called by a file system in a certain time period, and migrate these blocks to secondary storage.