Tiered Backup Metadata and Payload Storage for Faster Restore

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud storage solutions face challenges in balancing cost-effectiveness and accessibility, with long-term storage tiers causing delays due to high latency, while immediate access tiers incur high costs, complicating data management for organizations.

Innovation Solution

An information management system that separates backup payload data from metadata, storing metadata in a high-accessibility, high-cost tier and payload data in a lower-accessibility, lower-cost tier, optimizing storage characteristics based on organizational needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If backup data is stored in long-term cloud storage tier, then storage cost is reduced, but data access latency increases

Engineering Contradiction:
Improvestorage costVSAvoiddata access latency
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent segments backup data into two distinct components: metadata (stored in high-accessibility tier) and payload data (stored in low-accessibility tier). This segmentation allows the system to optimize for both cost and accessibility by placing different data types in appropriate storage tiers based on their access patterns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different storage characteristics to different parts of the backup data. Metadata, which requires frequent access for browsing and management, is stored in high-accessibility tier, while payload data, which is accessed less frequently, is stored in low-accessibility tier for cost optimization.

Inventive Principle:
Principle #3Local quality

2Speed

If backup data is stored in immediate access cloud storage tier, then data accessibility is improved, but storage cost increases

Engineering Contradiction:
Improvedata access speedVSAvoidstorage cost
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The patent segments backup data into metadata and payload data, storing each in the most appropriate storage tier. This segmentation enables the system to achieve fast access for metadata operations while avoiding the high cost of storing entire backup sets in immediate access tier.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by storing only the metadata portion of backup data in the high-accessibility tier, giving that specific part high speed characteristics, while the payload data resides in low-accessibility tier with cost-effective characteristics.

Inventive Principle:
Principle #3Local quality

3Ease of operation

If all backup data is stored in a single cloud storage tier, then management is simplified, but access efficiency and cost optimization are compromised

Engineering Contradiction:
Improvedata management simplicityVSAvoidbrowsing and restoring efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent segments backup data into metadata and payload data stored in different tiers, which initially appears to increase complexity. However, the system provides a unified interface that abstracts this complexity, maintaining ease of operation while enabling optimized access efficiency and cost management through intelligent data placement.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250278339A1Back up and restore related data on different cloud storage tiers
Publication Date: 2025.09.04 COMMVAULT SYSTEMS INC
  • US20250278339A1 patent drawing
  • US20250278339A1 patent drawing
  • US20250278339A1 patent drawing

AI summary

Presented herein are systems and methods for backing up and restoring related backup data stored in different cloud storage tiers in a cloud storage environment. Backup data generated during a backup job is stored to different cloud storage tiers based on the type of data and a storage policy comprising designations of a first cloud storage tier and a second cloud storage tier. Backup metadata and index data is stored in the designated first cloud storage tier and backup payload data is stored in the designated second cloud storage tier. Designations of the storage tiers are based on the attributes associated with each tier of cloud storage. During restore, the backup payload data is recalled from the second storage tier into the first storage tier where it is used to restore to the destination client or customer.