Hybrid Backup Orchestrator for Computational Resource Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup systems are inefficient in managing computational resources, as they often generate and store backups using methods that do not account for the capabilities of available content managers, leading to higher computational costs and potential resource shortages.

Innovation Solution

A backup manager that identifies the types of content managers available and schedules hybrid backups, combining full and incremental backups to reduce computational costs while meeting data protection requirements, by using the backup orchestrator to determine when and how to invoke native backup generation functionalities of content managers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If backup systems generate and store backups using traditional methods, then backup services are provided, but computational resources are consumed inefficiently leading to higher computational costs and potential resource shortages

Engineering Contradiction:
Improvecomputational resource consumptionVSAvoidbackup service reliability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The backup system is segmented into different backup types (full backup and incremental backup) that can be selectively applied to different content managers based on their capabilities. This segmentation allows the system to optimize resource consumption by using incremental backups for content managers that support them, while using full backups for those that don't, thereby reducing overall computational resource consumption while maintaining backup reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The backup system dynamically determines the backup type to generate based on the capabilities of available content managers. The backup manager identifies which content managers support incremental backups and adjusts the backup strategy accordingly, making the system adaptive and flexible rather than static. This dynamic approach optimizes computational resource usage while ensuring reliable backup services.

Inventive Principle:
Principle #15Dynamics

2Loss of energy

If hybrid backup is implemented by identifying content manager types and combining full and incremental backups, then computational resource consumption is reduced, but system complexity increases

Engineering Contradiction:
Improvecomputational resource consumptionVSAvoidbackup management system complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

A backup manager acts as an intermediary between the backup orchestrator and content managers. The backup manager handles the complexity of identifying content manager types, determining appropriate backup types, and coordinating backup operations. By introducing this intermediary layer, the system manages the complexity of hybrid backup implementation while achieving reduced computational resource consumption, as the backup manager centralizes the decision-making logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the parameter of backup type selection based on content manager capabilities. Instead of using a fixed backup strategy, the system dynamically changes the backup type parameter (full or incremental) according to the identified content manager types. This parameter change approach allows the system to reduce computational resource consumption while managing complexity through structured decision-making based on content manager characteristics.

Inventive Principle:
Principle #35Parameter changes

3Ease of manufacture

If traditional backup methods are used without considering content manager capabilities, then implementation is simpler, but resource shortages occur leading to system failures

Engineering Contradiction:
Improvebackup system implementation simplicityVSAvoidsystem failure likelihood
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The backup system performs preliminary identification of content manager types and their capabilities before generating backups. The backup manager proactively determines which content managers support incremental backups and plans the backup strategy in advance. This preliminary action prevents resource shortages and system failures by ensuring that the backup strategy is optimized based on actual content manager capabilities, rather than reacting to resource issues after they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from content manager capability identification to adjust the backup strategy. The backup manager receives information about which content managers support incremental backups and uses this feedback to determine the appropriate backup type for each content manager. This feedback mechanism ensures that the backup system adapts to the actual capabilities of the system components, preventing resource shortages and improving reliability while maintaining reasonable implementation complexity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11281542B2System and method for backup generation for deployments
Publication Date: 2022.03.22 EMC IP HLDG CO LLC
  • US11281542B2 patent drawing
  • US11281542B2 patent drawing
  • US11281542B2 patent drawing

AI summary

A backup manager for providing backup services includes storage and a backup orchestrator. The storage stores manager associations. The backup orchestrator obtains a request to provide the backup services for a deployment; in response to the request: identifies types of managers of the deployment; makes a determination, based on the types of the managers of the deployment, that the managers of the deployment require a hybrid backup using the manager associations; and schedules a hybrid backup for the deployment based on the determination.