Backup Data Segmentation by File Size for Selective Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional backup processes store data in a single location without consideration for ease of access, requiring users to restore entire backups to access specific files, which is inefficient and time-consuming, especially for large files.

Innovation Solution

Implementing a system that categorizes and stores backup data by file size, allowing large files to be stored separately, enabling users to locate and access them directly without full restore, and using multiple savestreams for simultaneous backup to increase process speed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the entire backup is stored in a single location, then the backup process is simple and access to the backup is straightforward, but the user cannot easily access specific files without restoring the entire backup

Engineering Contradiction:
Improveease of access to specific filesVSAvoidbackup storage structure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The backup is segmented into multiple savestreams, each containing files of similar size. This allows users to access specific files from specific savestreams without restoring the entire backup, resolving the contradiction between ease of access and storage simplicity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of organization by categorizing files based on their size and storing them in separate savestreams. This dimensional approach to file organization enables selective access while maintaining backup integrity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Loss of time

If the backup is stored without categorization by file size, then the backup process is efficient, but large files cannot be accessed without restoring the entire backup

Engineering Contradiction:
Improvetime to access specific filesVSAvoidbackup process speed
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The backup process is segmented into multiple parallel savestreams that simultaneously backup files of different sizes. This segmentation enables selective access to large files without time loss while maintaining efficient backup throughput through parallel processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Files are pre-categorized by size during the backup process and organized into separate savestreams. This preliminary organization allows users to quickly locate and access specific files without time loss while the backup process continues efficiently in parallel.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If multiple savestreams are used for simultaneous backup, then the backup process speed increases, but the system complexity increases

Engineering Contradiction:
Improvebackup process speedVSAvoidbackup system structure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The backup system is segmented into multiple independent savestreams that can operate simultaneously. This segmentation increases backup productivity through parallel processing while maintaining manageable complexity through standardized stream management protocols.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The savestream mechanism serves multiple functions: it categorizes files by size, enables selective access, and facilitates parallel backup processing. This multi-functionality increases productivity without proportionally increasing system complexity.

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

Data Source

PatentUS11256573B1Method of categorizing data and its backup destination
Publication Date: 2022.02.22 EMC IP HLDG CO LLC
  • US11256573B1 patent drawing
  • US11256573B1 patent drawing
  • US11256573B1 patent drawing

AI summary

In one example, a method can be performed that involves receiving a backup request specifying: one or more files to be backed up; a group of one or more categories, each of which corresponds to a respective range of file sizes; and, one or more storage destinations, categorizing each of the files by assigning a respective category to each file, initiating a respective backup datastream corresponding to each category that has been assigned, and requesting that each backup datastream be backed up at the respective storage destination that corresponds to the assigned category associated with that backup datastream.