Client-Managed Backup Metadata Caching for Scalable Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Information management systems experience communication bottlenecks due to increased client devices, leading to reduced hardware and storage availability, particularly during backup and restore processes, which limits the scalability of the system.

Innovation Solution

Clients obtain job metadata from a storage manager and store it locally, reducing the frequency of communication with the storage manager, and distribute backup management, enabling direct communication with cloud or network storage systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If clients communicate frequently with the storage manager during backup operations, then backup management and control are improved, but communication bottlenecks worsen and system scalability deteriorates

Engineering Contradiction:
Improvebackup management controlVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the backup management functionality by introducing local agents on client devices that can independently manage backup operations. These agents obtain job metadata from the storage manager but then operate autonomously to execute backups, reducing the need for continuous communication with the central storage manager and thereby resolving the contradiction between centralized control and system scalability.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If the number of client devices is increased, then system capacity is improved, but communication overhead increases and resource availability decreases

Engineering Contradiction:
Improvenumber of client devicesVSAvoidcommunication overhead
Core Design Contradiction:
Quantity of substanceVSUse of energy by moving object

Solution Approach 1:

The patent implements self-service mechanisms where local agents on client devices autonomously manage their own backup operations. Agents obtain initial job metadata from the storage manager but then independently execute backups, monitor their own status, and manage local resources without requiring continuous communication with the storage manager, thereby reducing communication overhead as the system scales.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If centralized backup management is maintained, then coordination and control are improved, but communication bottlenecks increase and backup speed decreases

Engineering Contradiction:
Improvebackup coordinationVSAvoidbackup speed
Core Design Contradiction:
Ease of operationVSSpeed

Solution Approach 1:

The patent divides backup management into centralized coordination (storage manager providing job metadata) and decentralized execution (local agents performing actual backups). This segmentation allows the storage manager to maintain coordination control while local agents execute backups independently at full speed without communication bottlenecks, resolving the contradiction between centralized control and backup speed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces local agents as intermediaries between the storage manager and the actual backup processes. These agents receive job metadata from the storage manager and then mediate the execution of backups locally, reducing direct communication requirements between the storage manager and backup operations, thereby improving backup speed while maintaining coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250219887A1Client managed data backup process within an enterprise information management system
Publication Date: 2025.07.03 COMMVAULT SYSTEMS INC
  • US20250219887A1 patent drawing
  • US20250219887A1 patent drawing
  • US20250219887A1 patent drawing

AI summary

Certain embodiments disclosed herein reduce or eliminate a communication bottleneck at the storage manager by reducing communication with the storage manager while maintaining functionality of an information management system. In some implementations, a client obtains information for enabling a secondary storage job (e.g., a backup or restore) from a storage manager and stores the information (which may be referred to as job metadata) in a local cache. The client may then reuse the job metadata for multiple storage jobs reducing the frequency of communication with the storage manager. When a configuration of the information management system changes, or the availability of resources changes, the storage manager can push updates to the job metadata to the clients. Further, a client can periodically request updated job metadata from the storage manager ensuring that the client does not rely on out-of-date job metadata.