Dynamic Computing Pod Provisioning for Backup Workloads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup and restoration solutions often lack sufficient computing resources, leading to prolonged backup and restoration times, which impact recovery time objectives (RTO) and recovery point objectives (RPO), especially when dealing with large volumes of data and numerous computing devices.

Innovation Solution

An information management system utilizing a flexible computing resource cluster that dynamically provisions computing pods using pre-configured backup images, allowing for on-demand allocation and deallocation of resources based on resource requests from a storage manager, ensuring efficient management of backup and restoration operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a backup solution is deployed to protect computing devices, then data protection capability is improved, but computing resource sufficiency deteriorates

Engineering Contradiction:
Improvedata protection capabilityVSAvoidcomputing resource sufficiency
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system dynamically provisions computing pods based on real-time backup workload demands. The resource administrator monitors computing resource usage and automatically instantiates or terminates pods to match the current backup throughput requirements, transforming the static resource allocation into a dynamic adaptive system that scales resources up during backup operations and releases them when not needed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The computing resource cluster serves multiple functions: it provides data protection through backup operations, enables data restoration when needed, and offers flexible resource allocation for various workloads. The same infrastructure supports both backup and restoration operations, as well as potential other computing tasks, maximizing resource utilization efficiency.

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

2Reliability

If backup operations are performed on large volumes of data, then data protection coverage is improved, but backup time deteriorates

Engineering Contradiction:
Improvedata protection coverageVSAvoidbackup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The backup workload is segmented across multiple computing pods that operate in parallel. Each pod handles a portion of the backup throughput requirements, allowing the system to divide and conquer large data volumes by processing them concurrently through multiple independent computing units rather than a single sequential process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system pre-configures computing pods with necessary software and resources before backup operations begin. The resource administrator can instantiate pods in advance and prepare the computing resource cluster, so when backup operations are initiated, the infrastructure is already ready to immediately process data without setup delays.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If computing resources are allocated for backup operations, then backup throughput is improved, but resource flexibility deteriorates

Engineering Contradiction:
Improvebackup throughputVSAvoidresource flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system maintains resource flexibility through dynamic pod provisioning. Computing resources are allocated on-demand based on backup throughput requirements, and the same resources can be released and reallocated for different workloads. The computing resource cluster can adapt to varying backup demands while maintaining the ability to reconfigure for other tasks, achieving both high throughput and resource versatility.

Inventive Principle:
Principle #15Dynamics

4Reliability

If a full on-premise backup solution is deployed, then backup capability is improved, but system complexity deteriorates

Engineering Contradiction:
Improvebackup capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces a resource administrator as an intermediary layer between the backup solution and the computing resource cluster. This intermediary manages pod instantiation, monitors resource usage, and coordinates backup operations, simplifying the overall system architecture by providing a centralized control mechanism rather than requiring direct complex interactions between all components.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240411615A1Dynamically provisioning computing PODS in a computing resource cluster
Publication Date: 2024.12.12 COMMVAULT SYSTEMS INC
  • US20240411615A1 patent drawing
  • US20240411615A1 patent drawing
  • US20240411615A1 patent drawing

AI summary

An information management system includes a storage manager for managing backup and/or restore operations for one or more client computing devices. The storage manager may be in communication with a resource administrator of a computing resource cluster, wherein the resource administrator instantiates one or more computing pods using the computing resource cluster. The resource administrator may receive a request for computing resources from the storage manager and provision the computing pods based on the request. The resource administrator may then select a pre-configured container image from one or more pre-configured container images based on the computing resource request, wherein the pre-configured container image configures a computing pod to create secondary copies of primary data from a particular primary data source of the information management system. The resource administrator may then communicate a message to the storage manager informing the storage of the availability of the provisioned computing pods.