Service Device Backup Generation via Block-Level Transaction Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data protection systems for service devices that provide computer-implemented services face challenges in ensuring a predetermined level of data protection, as scheduled backups may be insufficient to handle sudden increases in data changes, leading to potential data loss exceeding acceptable limits.
Innovation Solution
A backup management system that filters storage system transactions using a block-level filter to identify impacting transactions, generates service-device initiated backups when data protection metrics indicate insufficient protection, and remediates the backup schedule to ensure data protection requirements are met.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If scheduled backups are used for data protection, then data protection services can be provided with predictable resource usage, but data loss may exceed acceptable limits when sudden increases in data changes occur
Solution Approach 1:
The backup system dynamically adjusts backup frequency based on real-time data change rates. When the rate of data changes exceeds a threshold, the system automatically initiates unscheduled backups, transforming the static scheduled backup approach into a dynamic responsive system that adapts to actual data protection needs.
Solution Approach 2:
The system continuously monitors data change rates and uses this feedback to determine when unscheduled backups should be triggered. By measuring the rate of data changes and comparing it against thresholds, the system receives feedback about data protection adequacy and adjusts backup behavior accordingly, ensuring reliable data protection while avoiding excessive backups.
2Reliability
If unscheduled backups are generated based on data change rates, then data protection reliability is improved, but system complexity increases
Solution Approach 1:
The service device autonomously monitors its own data change rates and automatically triggers unscheduled backups when thresholds are exceeded, without requiring external intervention or complex centralized management. This self-service approach simplifies overall system architecture by distributing the intelligence to the individual service devices.
Solution Approach 2:
The system pre-establishes threshold criteria for triggering unscheduled backups based on acceptable data loss limits. By defining these thresholds in advance, the system avoids complex real-time decision-making about whether backups are needed, simplifying the backup management logic while maintaining reliable data protection.
3Reliability
If backup frequency is increased to handle sudden data changes, then data protection level improves, but computing resource consumption increases
Solution Approach 1:
Instead of continuously increasing backup frequency across all services, the system applies partial action by triggering unscheduled backups only for specific service devices where data change rates exceed thresholds. This targeted approach provides enhanced data protection exactly where needed while avoiding unnecessary resource consumption in other areas.
Solution Approach 2:
The system changes the parameter of backup frequency dynamically based on measured data change rates. Rather than using a fixed high backup frequency that would consume excessive resources, the system adjusts the frequency parameter in response to actual conditions, increasing it only when data protection requirements demand and maintaining lower frequencies when sufficient protection already exists.
Data Source
AI summary
A backup management system includes storage and a processor. The processor filters copies of storage system transactions of a service device using a block level filter to identify a portion of the storage system transactions impacting a protected data asset; obtains at least one data protection metric based on the portion of the storage system transactions; makes a determination that the at least one data protection metric indicates that the backup schedule will not provide the protected data asset with a predetermined level of data protection; in response to the determination: generates a service-device initiated backup for the protected data asset; stores the service-device initiated backup in backup storage; and remediates a backup schedule for the service device based on the service-device initiated backup.