Backup Management System Automating Service Level Agreements

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup systems face challenges in managing diverse user data backup demands, particularly when migrating to new systems with service level agreements, as manual adjustments are complex and time-consuming, leading to difficulties in accommodating changing user requirements and resource management.

Innovation Solution

A method and system that determine backup attributes from historical records to automatically generate and manage backup demands, using statistical data to set threshold ranges and candidate values for start time, end time, backup speed, and other attributes, allowing for efficient resource allocation and reducing manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual adjustments are used to manage backup demands during system migration, then service level agreements can be customized for different users, but the process becomes complex and time-consuming

Engineering Contradiction:
Improvecustomization of service level agreementsVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system automatically generates service level agreements by analyzing historical backup operation records and determining data distribution patterns. The backup management system performs self-service by autonomously creating customized SLAs based on historical data without requiring manual intervention for each user, thus maintaining adaptability while reducing management complexity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary analysis of historical backup records to determine data distribution characteristics before system migration. By pre-calculating backup attributes and establishing baseline patterns from past operations, the system prepares customized service level agreements in advance, enabling smooth migration while maintaining user-specific requirements

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If manual adjustments are used to manage backup demands during system migration, then service level agreements can be customized for different users, but the process becomes time-consuming

Engineering Contradiction:
Improvecustomization of service level agreementsVSAvoidtime for managing backup demands
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system automatically generates service level agreements by analyzing historical backup operation records and determining data distribution patterns. The backup management system performs self-service by autonomously creating customized SLAs based on historical data without requiring manual intervention for each user, thus maintaining adaptability while reducing management complexity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual mechanical processes of analyzing historical data and creating service level agreements with automated computational mechanisms. By using algorithms to analyze backup records and generate SLAs automatically, the system eliminates time-consuming manual work while preserving customized service level agreement capabilities

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If backup operations are performed for multiple users with different demands, then user-specific requirements are met, but the amount of data in the backup system continually increases

Engineering Contradiction:
Improveaccommodation of user demandsVSAvoiddata volume in backup system
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system determines data distribution characteristics by analyzing historical backup records and uses these parameters to optimize backup operations. By changing backup parameters such as retention periods, backup frequencies, and storage allocation based on determined data distribution patterns, the system accommodates user-specific requirements while controlling overall data volume growth

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system applies different backup strategies to different users based on their specific demands and historical patterns. By customizing backup attributes for each user according to their local requirements rather than applying a uniform approach, the system efficiently manages data volume while meeting individual user needs

Inventive Principle:
Principle #3Local quality

4Volume of stationary object

If data is migrated to a new backup system with larger capacity, then storage requirements are met, but management of backup demands becomes difficult

Engineering Contradiction:
Improvebackup system capacityVSAvoidmanagement difficulty
Core Design Contradiction:
Volume of stationary objectVSDevice complexity

Solution Approach 1:

The system performs preliminary analysis of historical backup records to determine data distribution characteristics before system migration. By pre-calculating backup attributes and establishing baseline patterns from past operations, the system prepares customized service level agreements in advance, enabling smooth migration while maintaining user-specific requirements and simplifying management of the new larger-capacity system

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11301337B2Method, device, and computer program product for managing backup system
Publication Date: 2022.04.12 EMC IP HLDG CO LLC
  • US11301337B2 patent drawing
  • US11301337B2 patent drawing
  • US11301337B2 patent drawing

AI summary

The present disclosure relates to a method, device and computer program product for managing a backup system. In a method for managing a backup system, at least one backup attribute of a backup demand on the backup system is determined, the at least one backup attribute describing at least one aspect of a demand on the backup system from a user of the backup system. A plurality of backup records of a plurality of historical backup operations performed on the backup system are obtained, respectively. Data distribution associated with the at least one backup attribute is determined based on the plurality of backup records.