Granular Backup Lifecycle Management via Distinct Periodicities
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data protection methods like mirroring and replication fail to differentiate between correct and corrupted data, and backups are optimized for point-in-time recovery rather than granular data management, making it difficult to restore specific files or data states post-disaster.
Innovation Solution
A system that creates primary and secondary backup copies with distinct periodicities, allowing for granular application data lifecycle management, enabling the capture of data states at different points in time and facilitating restoration of specific files or data states post-disaster.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If mirroring and replication technology is used to protect data, then data protection against hardware failures is improved, but the system cannot differentiate between correct and corrupted data, allowing software or human errors to be propagated
Solution Approach 1:
The backup system segments data protection into multiple independent backup copies created at different time points, rather than using continuous replication. Each backup copy is an independent snapshot that can be individually validated, preventing propagation of corrupted data while maintaining protection against hardware failures.
Solution Approach 2:
The system performs preliminary validation and verification of data integrity during the backup creation process itself, before data can be corrupted. By creating discrete backup copies at scheduled intervals with built-in validation, the system prevents software or human errors from propagating while maintaining reliable data protection.
2Reliability
If backup is optimized for point-in-time recovery, then data protection is improved, but granular data management and restoration of specific files becomes difficult
Solution Approach 1:
The backup system segments the backup data into granular components (individual files, folders, or data objects) within each backup copy, allowing selective restoration of specific elements rather than requiring full backup restoration. This maintains point-in-time recovery capability while enabling easy granular data management.
Solution Approach 2:
The system adds a new dimension to backup management by organizing data hierarchically across multiple backup copies with different retention periods and granularities. This multi-dimensional structure allows users to access specific files from appropriate backup copies based on their needs, combining point-in-time recovery with granular restoration capability.
3Adaptability or versatility
If multiple backup copies with different retention periods are maintained, then data recovery flexibility is improved, but storage resource consumption increases
Solution Approach 1:
The backup system applies local quality by assigning different retention periods and storage characteristics to different backup copies based on their specific purposes. Recent backups may be stored with higher redundancy and longer retention, while older backups use more compact storage, optimizing the balance between recovery flexibility and storage efficiency.
Solution Approach 2:
The system dynamically changes storage parameters (retention period, compression level, redundancy) for different backup copies based on their age and importance. This allows the system to maintain high adaptability for recent data recovery while reducing storage consumption for historical backups, achieving an optimal balance between flexibility and resource usage.
Data Source
AI summary
A system or method for granular application data lifecycle sourcing from a single backup is disclosed. In one embodiment of the method, a computer system periodically creates a primary backup copy of data stored on a storage system in order to create a plurality of primary backup copies. The computer system also periodically creates a secondary backup copy of data stored on the storage system in order to create a first plurality of secondary backup copies, wherein each of the secondary backup copies of the first plurality is created in part by copying data from a respective one of the primary backup copies. The periodicity of creating the primary backup copies, however, is distinct from the periodicity of creating the secondary backup copies of the first plurality.