S3 Migration Index Objects for Seamless Cloud Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data migration methods for cloud storage are inefficient, particularly when migrating from public clouds to private clouds, as they often copy deleted data and take a long time, and lack suitable solutions for private cloud migrations, leading to disruptions and data integrity issues.

Innovation Solution

The method employs index objects and an S3 migration management module to create and migrate Access Control Lists (ACLs) during an index stage, followed by object data migration in a data stage, using migration agents to ensure seamless and efficient data transfer without altering the original data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data migration copies all data first including deleted data, then data completeness is improved, but migration time increases significantly and data integrity deteriorates

Engineering Contradiction:
Improvedata completenessVSAvoidmigration time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent applies preliminary action by creating index objects that represent all data objects before actual data migration begins. This index stage allows the system to identify and track all objects (including deleted ones) in advance, so that during the subsequent data stage, only necessary data needs to be transferred. This resolves the contradiction by preparing the migration framework beforehand, enabling efficient selective data transfer rather than blind copying of all data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the migration process into two distinct stages: an index stage for creating representative index objects and metadata, and a data stage for actual data transfer. This segmentation allows the system to separate the overhead of tracking all objects from the actual data copying, thereby reducing overall migration time while maintaining data completeness. The index objects act as placeholders that enable efficient data stage execution.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If data migration copies all data first, then data completeness is improved, but data integrity deteriorates due to copying deleted data

Engineering Contradiction:
Improvedata completenessVSAvoiddata integrity
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent implements feedback mechanisms through ACL migration and index object tracking. The system continuously monitors the state of source objects and uses this feedback to determine which data objects should be migrated. By migrating ACLs (Access Control Lists) along with index objects, the system maintains accurate information about object states and permissions, enabling it to identify and exclude deleted objects from the data migration phase, thus preserving data integrity while maintaining completeness.

Inventive Principle:
Principle #23Feedback

3Productivity

If endpoint switching is performed after data copying, then migration completion is achieved, but service disruption occurs during the switching process

Engineering Contradiction:
Improvemigration completionVSAvoidservice continuity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent applies preliminary action by creating index objects and migrating ACLs during the index stage, before the data stage begins. This preparation ensures that when data migration completes, the destination is already configured with proper metadata and access controls, enabling seamless endpoint switching without service disruption. The preliminary setup of the migration framework allows for smooth transition.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The index objects serve as intermediaries between the source and destination systems during migration. These index objects maintain the relationship between source objects and their representations at the destination, enabling continuous access during the transition. The intermediary index objects allow the system to switch endpoints seamlessly because they preserve the logical structure and access paths even as physical data locations change.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If traditional data migration methods are used for private clouds, then migration capability is achieved, but migration efficiency deteriorates due to lack of optimized solutions

Engineering Contradiction:
Improvemigration capabilityVSAvoidmigration efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the migration process into distinct index and data stages, with each stage performing specific optimized functions. The index stage focuses on metadata and ACL migration, while the data stage focuses on efficient data transfer. This segmentation enables the system to adapt to private cloud environments by optimizing each stage for the specific requirements of the target cloud infrastructure, thereby improving overall migration efficiency while maintaining versatility.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11516287B2Method and apparatus for performing simple storage service seamless migration using index objects
Publication Date: 2022.11.29 SILICON MOTION TECH HONG KONG LTD
  • US11516287B2 patent drawing
  • US11516287B2 patent drawing
  • US11516287B2 patent drawing

AI summary

A method for performing Simple Storage Service (S3) seamless migration using index objects and associated apparatus are provided. The method includes: in response to a request of migrating user data of a user of the storage server from a remote S3-compatible server into the storage server, during an index stage, utilizing an index-object-based S3 migration management module among multiple program modules running on a host device within the storage server to create and store multiple index objects into a storage device layer of the storage server to be respective representatives of multiple normal objects of the user data at the storage server, and migrate respective Access Control Lists (ACLs) of the multiple normal objects to the storage server to be respective ACLs of the multiple index objects; and during a data stage, utilizing the index-object-based S3 migration management module to trigger one or more migration agents to migrate object data.