Backup System Orchestrating Direct Cloud Storage Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup systems face challenges in maintaining awareness and efficient data migration between different cloud storage providers, leading to difficulties in recalling data when needed, especially due to decoupling issues and the need for cost-effective long-term retention solutions.

Innovation Solution

A backup system that acts as a central control plane for orchestrating direct data migration between multiple cloud providers, allowing for prioritization and validation of data movement without recalling data to the active tier, using a data management engine to manage policies and metadata for seamless data transfer and retention across heterogeneous cloud services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is migrated directly between cloud storages without backup system intervention, then migration efficiency is improved, but the backup system loses awareness of data location making recall difficult

Engineering Contradiction:
Improvemigration efficiencyVSAvoidbackup system awareness
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The backup system implements feedback mechanisms by receiving notifications from cloud storage providers about data migrations. The system maintains metadata records that track data locations across different cloud storages, and updates these records when migrations occur. This feedback loop ensures the backup system remains aware of data locations even when migrations happen autonomously between cloud providers.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The backup system acts as an intermediary that orchestrates data migrations between cloud storages. Rather than allowing direct autonomous migrations, the backup system mediates the process by coordinating with cloud storage providers, maintaining control over data movement, and ensuring awareness is preserved through its intermediary role in the migration ecosystem.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If backup copies are maintained on traditional backup systems, then data recall capability is ensured, but storage costs continue to grow with organization growth

Engineering Contradiction:
Improvedata recall capabilityVSAvoidstorage costs
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system segments backup storage across multiple cloud storage providers rather than concentrating all backup copies on a single traditional backup system. This segmentation allows the organization to leverage the economies of scale from multiple cloud providers while maintaining data recall capability through the backup system's orchestration and metadata tracking.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The backup system implements a universal architecture that can manage data across different cloud storage providers simultaneously. This multi-functionality allows the same backup system to interact with various cloud storage services, enabling cost-effective storage distribution while maintaining unified data recall capabilities through a single management interface.

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

3Quantity of substance

If data is stored in multiple cloud storages, then storage costs are reduced through economies of scale, but data migration and management complexity increases

Engineering Contradiction:
Improvestorage costsVSAvoiddata migration complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The backup system provides a universal management interface that can operate across multiple cloud storage providers with different protocols and APIs. This multi-functionality simplifies data migration by presenting a unified view to users while handling the complexity of interacting with diverse cloud storage systems behind the scenes.

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

Solution Approach 2:

The backup system serves as an intermediary layer between users and multiple cloud storage providers. It abstracts the complexity of multi-cloud management by handling authentication, data format conversion, and migration coordination, thereby reducing the perceived complexity for users while enabling cost-effective multi-cloud storage strategies.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Device complexity

If direct data migration is implemented between cloud providers, then third-party tools are eliminated, but backup system awareness of data location is lost

Engineering Contradiction:
Improvesystem integrationVSAvoiddata location tracking
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The system implements feedback mechanisms where the backup system receives notifications from cloud storage providers about data migrations. This feedback ensures the backup system maintains awareness of data locations even when migrations occur directly between cloud providers without traditional intermediary tools.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The backup system acts as an intermediary that orchestrates data migrations between cloud storages. Rather than allowing direct autonomous migrations, the backup system mediates the process by coordinating with cloud storage providers, maintaining control over data movement, and ensuring awareness is preserved through its intermediary role in the migration ecosystem.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11520669B2System and method for efficient backup system aware direct data migration between cloud storages
Publication Date: 2022.12.06 EMC IP HLDG CO LLC
  • US11520669B2 patent drawing
  • US11520669B2 patent drawing
  • US11520669B2 patent drawing

AI summary

A first cloud vendor is registered by a backup application. A file is moved from backup storage of the backup application to the first cloud vendor. A reference is maintained at the backup storage to the first file residing at the first cloud vendor. A second cloud vendor is registered by the backup application. The backup application directs a migration of the file from the first cloud vendor to the second cloud vendor without recalling the file to the backup storage. A reference maintained at the backup storage is updated to refer to the file now residing at the second cloud vendor. The updated reference is maintained at the backup storage.