Backup Metadata for Selective Cloud Object Deletions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing unstructured data in cloud object storage for backup, archiving, and disaster recovery involves complex and resource-intensive post-upload activities such as modifications or deletions, especially when compliance with data regulatory laws is required, which current methods fail to address efficiently.
Innovation Solution
Leveraging backup process metadata to facilitate selective overwrites of data objects in cloud storage by identifying and modifying or deleting specific data portions using metadata records, ensuring compliance with regulatory requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If post-upload activities (modifications or deletions) are performed on backup data in cloud object storage, then data compliance with regulatory laws is achieved, but resource consumption increases significantly
Solution Approach 1:
The patent segments the backup data into individual data objects and further into data object portions, allowing selective modification or deletion of only the specific portions that need compliance adjustments rather than processing entire data objects or all backup data, thereby reducing resource consumption
Solution Approach 2:
The patent performs preliminary actions by identifying and locating specific data object portions that contain backup host information before performing modifications or deletions. This preliminary identification using metadata allows the system to precisely target only the necessary data portions, avoiding unnecessary resource consumption on unrelated data
2Reliability
If selective deletion of backup data is implemented to comply with data sovereignty laws, then regulatory compliance is achieved, but system complexity increases
Solution Approach 1:
The patent introduces metadata as an intermediary layer between the backup data and the deletion mechanism. This metadata contains information about data object portions that contain backup host information, allowing the system to selectively delete only relevant portions without requiring complex analysis of the actual backup data content, thus managing system complexity
3Adaptability or versatility
If cloud object storage is used for backup and archiving, then data scalability and elasticity are improved, but post-upload management operations become more complex
Solution Approach 1:
The patent segments cloud object storage data into manageable data objects and further into data object portions, each with associated metadata. This segmentation allows scalable storage while simplifying post-upload operations by enabling targeted management of specific portions rather than dealing with monolithic data structures
Solution Approach 2:
The patent adds a metadata dimension to the cloud object storage structure, creating a two-layer architecture where metadata provides indexing and identification information. This additional dimension enables efficient post-upload management operations without compromising the scalability of the underlying storage system
Data Source
AI summary
A method and system for leveraging backup process metadata for cloud object storage selective deletions. Under cloud object storage architecture, any unstructured data may be managed and stored in the cloud as objects. Objects thus provide an elastic, scalable format through which unstructured data may be maintained for a variety of purposes, including those directed to data backup, archiving, and/or disaster recovery. Further, any unstructured data, stored within any object, may pertain to one or many file(s). Should data, from multiple files, be stored within a shared object, any post-upload activity (e.g., modifications or deletions in keeping with data regulatory compliances) targeting said data, belonging to any one file or a subset of files, may be complex and resource-expensive. In addressing these undesirable qualities, embodiments disclosed herein use metadata, produced during and/or following backup processes protecting file data, to fulfill said post-upload activity resource-efficiently and without data compromising effects.


