Cloud Storage Data Migration Using Segment Flags

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integrating cloud services with conventional storage devices is challenging due to differences in operations, with existing systems often inefficient and unreliable in accessing and archiving data across both platforms.

Innovation Solution

A system that allows data migration between cloud services and storage devices by initiating data recalls, modifying metadata, prioritizing object transfers, and maintaining data integrity using flags, enabling seamless access and archiving while optimizing data transfer and storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is migrated entirely to cloud service, then storage capacity and scalability are improved, but data access speed and reliability deteriorate

Engineering Contradiction:
Improvestorage capacityVSAvoiddata access speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The patent segments data into multiple portions and distributes them across different storage locations (cloud service and storage device). This allows the system to maintain large storage capacity in the cloud while enabling faster access by retrieving only specific portions from local storage when needed, rather than accessing the entire dataset from the cloud.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by pre-transferring frequently accessed data portions from cloud to storage device before they are actually needed. The system monitors access patterns and proactively caches data in local storage, so when access is required, the data is already available locally rather than needing to be retrieved from cloud during the access operation.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If data is transferred completely before access, then data integrity is improved, but access time and productivity deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoidaccess time
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by transferring and validating only the necessary portions of data rather than requiring complete data transfer before any access can occur. The system can access already-transferred portions immediately while continuing to transfer remaining portions in the background, achieving both faster access and maintained integrity through selective validation.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent introduces an intermediary mechanism (storage device acting as buffer/cache between cloud and host) that decouples the integrity validation process from the access process. Data can be accessed from the intermediary storage device while integrity checks continue in the background or have been previously performed, allowing access without waiting for complete validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If all data portions are transferred simultaneously, then simplicity of operation is improved, but transfer efficiency and resource utilization deteriorate

Engineering Contradiction:
Improvesimplicity of operationVSAvoidtransfer efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent implements dynamic transfer strategies where the system continuously monitors access patterns, data priority levels, and system resource availability to adjust transfer rates and priorities in real-time. Frequently accessed data receives higher transfer priority and may be pre-transferred, while less critical data transfers at lower priority, optimizing overall system efficiency without requiring complex manual configuration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent incorporates feedback mechanisms that monitor data access patterns, transfer status, and system performance metrics. This feedback information is used to dynamically adjust transfer priorities and strategies - for example, if certain data portions are accessed frequently, the system automatically increases their transfer priority or pre-transfers them, while reducing priority for seldom-accessed data, thereby optimizing transfer efficiency based on actual usage.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10579481B1Restoring data from a storage device to a cloud
Publication Date: 2020.03.03 EMC IP HLDG CO LLC
  • US10579481B1 patent drawing
  • US10579481B1 patent drawing
  • US10579481B1 patent drawing

AI summary

Restoring data from a storage device to a cloud service includes initializing each of a plurality of flags for each of portions of the data when the data is initially recalled from the cloud service to the storage device, the flags indicating whether a corresponding portion of the data has been modified while being stored on the storage device, modifying a particular one of the flags in response to a corresponding one of the portions being modified, transferring only portions of the data having corresponding flags that have been modified to migrate, and merging the portions of the data with remaining data at the cloud service. Data that is recalled from the cloud service to the storage device may be maintained on the cloud service. The portions of data that are transferred from the storage device to the cloud service may overwrite data maintained at the cloud service.