Guardrails for Copy Data Storage Resource Limits

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Copy Data Storage systems, users often configure service level agreements (SLAs) that exceed data resource limits, leading to potential system failures due to insufficient resources, either from too many applications, frequent backups, or prolonged backup retention, without adequate warning or prevention mechanisms.

Innovation Solution

A computerized method and system that calculates the resource requirements for data backups by determining the number of copies, change rate parameters, and data volumes associated with each application, and transmits a resource shortage warning when aggregate resource limits are exceeded, preventing users from configuring SLAs that exceed available data resource limits.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users configure service level agreements with frequent backups and long retention periods, then data protection reliability is improved, but storage resource consumption increases and may exceed system limits

Engineering Contradiction:
Improvedata protection reliabilityVSAvoidstorage resource consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system performs preliminary calculation of resource requirements before the backup schedule is executed. By evaluating the aggregate pool resources and data volume resources needed for the configured SLA upfront, the system can warn users before resource limits are exceeded, preventing system failures and enabling proactive resource planning.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback to users by transmitting resource shortage warnings when the calculated aggregate resources exceed available limits. This feedback mechanism allows users to adjust their SLA configurations to align with available resources, resolving the contradiction between reliable data protection and resource consumption.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If the system allows users to configure unlimited backup schedules, then service flexibility is improved, but system stability deteriorates due to resource exhaustion

Engineering Contradiction:
Improveservice flexibilityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system applies preliminary anti-action by preventing users from configuring SLAs that would lead to resource exhaustion. Through upfront resource calculation and warning mechanisms, the system blocks configurations that would compromise system stability, thereby maintaining both service flexibility and system reliability.

Inventive Principle:
Principle #9Preliminary anti-action

3Measurement precision

If the system performs detailed resource calculations for each application backup, then measurement precision is improved, but computational complexity increases

Engineering Contradiction:
Improveresource measurement precisionVSAvoidcomputational complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The resource calculation process is segmented into distinct components: calculating number of copies, determining change rate parameters, computing data volumes, and aggregating pool resources. This segmentation allows for precise measurement of each resource component while organizing the computational complexity into manageable, modular steps.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10248510B2Guardrails for copy data storage
Publication Date: 2019.04.02 GOOGLE LLC
  • US10248510B2 patent drawing
  • US10248510B2 patent drawing
  • US10248510B2 patent drawing

AI summary

Techniques are disclosed for preventing a user from configuring a service level agreement from creating a data management schedule that creates a set of data backups that exceeds data resource limits available for storing the set of data backups. A first amount of pool resources associated with the backup of each of the at least one application is determined according to a received schedule. A first amount of data volumes associated with the backup of each of the at least one application is determined according to the received schedule. A resource shortage warning is transmitted when the aggregate amount of pool resources exceeds an available amount of pool resources or the aggregate amount of data volume resource exceeds an available amount of data volume resource, thereby preventing a user from configuring a service level agreement that exceeds data resource limits.