Client-Side Job Metadata Caching for Backup Bottlenecks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Information management systems face bottlenecks in data processing due to communication overhead, particularly during backup and restore operations, which limits the scalability and availability of computing resources as the number of client devices increases.

Innovation Solution

Implementing distributed backup management by allowing clients to store job metadata locally and communicate directly with cloud or network storage systems, reducing the burden on media agents and enabling clients to manage backup operations independently, thus minimizing communication with the storage manager.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If clients communicate with the storage manager during each backup operation, then backup operations can be properly managed and coordinated, but communication overhead increases and creates bottlenecks that reduce system scalability

Engineering Contradiction:
Improvebackup operation efficiencyVSAvoidcommunication overhead
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The storage manager pushes configuration metadata to clients in advance before backup operations begin. Clients store this metadata locally and reuse it for multiple backup operations, eliminating the need for repeated communication with the storage manager during each backup cycle. This preliminary action resolves the contradiction by preparing communication data beforehand, reducing real-time communication overhead while maintaining proper backup management.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the number of client devices is increased to support more users, then system coverage and utility improve, but communication bottlenecks worsen and reduce resource availability

Engineering Contradiction:
Improvenumber of supported clientsVSAvoidresource availability
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

Clients are empowered to perform backup operations independently using locally stored configuration metadata. They can initiate and complete backup operations without requiring real-time communication with the storage manager, effectively serving themselves. This self-service capability allows the system to scale to numerous clients without proportionally increasing communication overhead, resolving the contradiction between system coverage and resource availability.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If real-time communication with the storage manager is maintained for backup coordination, then backup operations can adapt to changing resource availability, but communication frequency increases and creates system bottlenecks

Engineering Contradiction:
Improvebackup operation flexibilityVSAvoidcommunication time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The storage manager pushes configuration metadata to clients in advance, including information about available resources and backup policies. Clients store this metadata locally and use it to perform backup operations without repeated real-time communication. This preliminary action provides clients with the flexibility to adapt to resource conditions while minimizing communication time, resolving the contradiction between operational flexibility and communication overhead.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11249863B2Backup-based media agent configuration
Publication Date: 2022.02.15 COMMVAULT SYSTEMS INC
  • US11249863B2 patent drawing
  • US11249863B2 patent drawing
  • US11249863B2 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.