Storage Rate Limiting for Accidental Data Deletion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large storage systems face management complications due to multiple users creating and deleting data objects, leading to potential accidental deletions and data loss, which existing systems fail to adequately address.

Innovation Solution

Implementing a rate limit system within a data storage space that defines a default limit for operations such as object creation, deletion, migration, and archiving, with remedial actions like stopping or slowing operations that exceed these limits, and allowing users to override temporarily, ensuring data integrity and reducing accidental deletions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple users are allowed to create and delete data objects freely in a large storage system, then user productivity and ease of operation are improved, but the risk of accidental deletions and data loss increases

Engineering Contradiction:
Improveuser productivityVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing rate limits and monitoring mechanisms before data operations occur. The storage management system proactively defines maximum operation rates and implements monitoring to prevent accidental deletions before they happen, rather than reacting after data loss occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements continuous feedback by monitoring data operations in real-time, comparing actual operation rates against predefined rate limits, and triggering remedial actions when limits are exceeded. This closed-loop feedback mechanism allows the system to adapt and respond to unusual deletion patterns that may indicate accidental data loss.

Inventive Principle:
Principle #23Feedback

2Reliability

If rate limiting is implemented to prevent accidental deletions, then data protection is improved, but system complexity and operational restrictions increase

Engineering Contradiction:
Improvedata protectionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The storage system is segmented into multiple independent components: rate limit definition module, operation monitoring module, comparison module, and remedial action module. Each component performs a specific function, making the overall system easier to manage and maintain despite the added complexity of rate limiting.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The storage management system provides self-service by automatically monitoring operations, comparing rates against limits, and implementing remedial actions without requiring constant human intervention. The system serves itself by managing its own data protection needs through automated rate limiting and monitoring.

Inventive Principle:
Principle #25Self-service

3Reliability

If strict rate limits are enforced to reduce accidental data loss, then data integrity is improved, but user flexibility and ease of operation deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoiduser flexibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The rate limiting system is dynamic rather than static. Rate limits can be adjusted based on user roles, storage space characteristics, and operational patterns. The system adapts to different users and scenarios, providing appropriate levels of restriction rather than applying uniform constraints to all operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes parameters such as rate limit values, monitoring thresholds, and remedial action triggers based on storage conditions and user behavior. By dynamically adjusting these parameters, the system maintains data integrity while accommodating legitimate high-volume operations that do not represent accidental deletions.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10152245B1Storage management system and method
Publication Date: 2018.12.11 EMC IP HLDG CO LLC
  • US10152245B1 patent drawing
  • US10152245B1 patent drawing
  • US10152245B1 patent drawing

AI summary

A method, computer program product, and computing system for defining at least a portion of a storage system as a data storage space. A rate limit is assigned to the data storage space, thus defining a default rate limit. Operations performed on objects within the data storage space are compared to determine if the default rate limit is exceeded. If the default rate limit is exceeded, one or more remedial actions are implemented concerning the operations performed on objects within the data storage space.