Backup Session Orchestration via Proxy Resource Reservation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup systems inefficiently utilize computing resources, leading to wasted resources and failed backup sessions due to insufficient processing capacity on proxy infrastructure.

Innovation Solution

Implementing a reservation mechanism for backup sessions on proxy infrastructure, where backup sessions are created based on available resources, and slices are processed in parallel within containers to optimize resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If backup sessions are created without reservation mechanism, then backup operations can be initiated freely, but computing resources are wasted and backup sessions fail due to insufficient processing capacity

Engineering Contradiction:
Improvebackup session success rateVSAvoidcomputing resource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary resource assessment before creating backup sessions. The reservation mechanism evaluates available computing resources on proxy infrastructure in advance and only creates backup sessions when sufficient resources are confirmed available, preventing resource waste and ensuring backup success.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The reservation mechanism implements feedback loops where the system continuously monitors computing resource availability on proxy infrastructure and adjusts backup session creation accordingly. This feedback ensures that backup sessions are only created when resources are sufficient, improving success rates while minimizing resource waste.

Inventive Principle:
Principle #23Feedback

2Productivity

If multiple backup sessions are created simultaneously, then backup processing throughput increases, but proxy infrastructure processing capacity is exceeded leading to failures

Engineering Contradiction:
Improvebackup processing throughputVSAvoidbackup session completion
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The reservation mechanism dynamically adjusts the number of concurrent backup sessions based on real-time proxy infrastructure capacity. The system can create multiple backup sessions when capacity allows but reduces or pauses creation when capacity is exceeded, maintaining both throughput and reliability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses feedback from proxy infrastructure resource monitoring to control backup session creation. When resource usage approaches capacity limits, the feedback mechanism prevents new backup sessions from being created or suspends existing ones, ensuring completion of all initiated sessions while maintaining high throughput during capacity-available periods.

Inventive Principle:
Principle #23Feedback

3Loss of energy

If backup sessions wait for resource availability, then resource utilization is optimized, but backup processing time increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidbackup processing time
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The reservation mechanism performs preliminary resource assessment continuously and proactively creates backup sessions when resources become available, rather than waiting passively. This preliminary action reduces the waiting time while ensuring resources are allocated efficiently, optimizing both time and resource utilization.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12271268B1Orchestrating backup sessions for efficient resource usage
Publication Date: 2025.04.08 DELL PROD LP
  • US12271268B1 patent drawing
  • US12271268B1 patent drawing
  • US12271268B1 patent drawing

AI summary

A method for performing a backup operation, the method comprising receiving a backup operation request for an asset, partitioning a plurality of slices of the asset into a plurality of backup sessions, wherein each backup session comprises a separate portion of the plurality of slices, sending a first backup request to a proxy manager to initiate a backup session of the plurality of backup sessions, wherein initiating the backup session comprises: instantiating a container on the one compute node, wherein the backup session operates within the container, receiving a notification that one of the plurality of slices in the backup session has been processed, and sending, based on the notification, a second backup request to the proxy manager to add a new slice to the backup session, wherein the new slice is associated with a second asset.