Object Storage Metadata Retention Across Cloud Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Metadata stored in object storage is susceptible to deletion and/or modification during data migration from one cloud provider's container to another, particularly when migrating for ingestion by artificial intelligence applications, leading to loss of metadata integrity.

Innovation Solution

A supplemental data structure is generated and stored with the object, linked to the source location using an object identifier, which is changed to the target location during migration, ensuring metadata preservation and integrity through the use of a hash value to validate its unmodified state.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is migrated from one cloud provider's container to another using conventional methods, then the migration process can be completed, but the metadata is lost or modified during the migration

Engineering Contradiction:
Improvemigration speedVSAvoidmetadata integrity
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by capturing and storing metadata in a supplemental data structure before the actual data migration occurs. This metadata is extracted from the source container and preserved in a format that can be reapplied to the target container, ensuring metadata integrity is maintained throughout the migration process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The supplemental data structure acts as an intermediary between the source and target containers. It captures metadata from the source container, transports it through the migration process, and applies it to the target container, thereby preserving metadata that would otherwise be lost during conventional migration.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If cloud providers implement conventional data migration standards, then users can migrate data between containers, but cloud providers can lock-in users to their ecosystem

Engineering Contradiction:
Improvecloud provider interoperabilityVSAvoiduser retention
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The supplemental data structure is designed with universal applicability across different cloud providers and container formats. It can capture, store, and transport metadata in a standardized format that works with various cloud ecosystems, enabling users to migrate data between different providers without being locked into a single ecosystem.

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

3Ease of manufacture

If metadata is not preserved during migration, then the migration process is simpler and faster, but the metadata cannot be searched natively or used for AI models

Engineering Contradiction:
Improvemigration process simplicityVSAvoidmetadata usability
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The system creates a copy of the metadata in the supplemental data structure during the migration process. This copy preserves the original metadata values and attributes, allowing the metadata to be reapplied to the target container in its native form, thereby maintaining searchability and usability for AI models without complicating the migration process.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12536193B2Systems and methods for data retention while migrating objects and object metadata stored in object storage environments migrated across cloud ecosystems
Publication Date: 2026.01.27 CITIBANK N A
  • US12536193B2 patent drawing
  • US12536193B2 patent drawing
  • US12536193B2 patent drawing

AI summary

Systems and methods for novel uses and/or improvements to data migration. In particular, systems and methods for data migration of metadata stored in object storage from one container to another, especially in instances when the metadata is destined for ingestion by an artificial intelligence application. The systems and methods ensure that all metadata (e.g., metadata stored in object storage) is preserved during data migration, including metadata such as content type, object lock mode, object lock retain until date, and/or custom metadata.