Dynamic Data Protection Metadata for Adaptive Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data protection systems are inflexible and do not adapt to dynamically changing needs and storage limitations, as they rely on fixed mappings between address ranges and data protection operations, failing to optimize resource usage and accommodate varying data importance.
Innovation Solution
A method and system that utilize data protection metadata to dynamically determine the relevance of data protection operations for write instructions, allowing for the execution of different data protection schemes such as change recording, asynchronous remote copying, and synchronous remote copying, based on the metadata associated with each write operation, enabling flexible and adaptive data protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If fixed mapping between address ranges and data protection operations is used, then system simplicity is maintained, but adaptability to dynamically changing needs deteriorates
Solution Approach 1:
The patent applies dynamics by transitioning from a static fixed mapping system to a dynamic metadata-driven system. Write instructions now include data protection metadata that can be modified over time, allowing the system to adapt to changing needs. The metadata field enables runtime adjustments to data protection operations without reconfiguring the entire system mapping.
Solution Approach 2:
The patent implements parameter changes by introducing data protection metadata as a configurable parameter within write instructions. This metadata can be changed over time to reflect varying data importance and storage constraints, allowing the system to adjust protection levels dynamically without changing the underlying fixed mapping structure.
2Productivity
If data protection metadata is added to write instructions, then data protection efficiency is improved, but write instruction complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the write instruction into distinct functional components: the core write operation and the optional data protection metadata field. This segmentation allows the metadata to be added as a separate, modular element that provides enhanced functionality without fundamentally altering the basic write instruction structure.
Solution Approach 2:
The data protection metadata acts as an intermediary between the write operation and the data protection system. It carries additional information about data importance and protection requirements, enabling the system to make intelligent decisions about which protection operations to apply without complicating the fundamental write process.
3Loss of energy
If dynamic data protection schemes are implemented, then resource usage optimization is achieved, but system complexity increases
Solution Approach 1:
The patent applies local quality by allowing different data protection operations to be applied to different data blocks based on their specific metadata characteristics. Rather than applying a uniform protection scheme system-wide, the system evaluates each write instruction's metadata and applies appropriate protection only where needed, optimizing resource usage for each local context.
Solution Approach 2:
The patent implements partial action by applying data protection operations selectively based on metadata indicators of data importance. Not all data requires the same level of protection - the system applies protection operations only to data blocks that meet specific criteria defined in their metadata, avoiding unnecessary resource consumption for less critical data.
Data Source
AI summary
A system, method and computer program product for performing a data protection operation is provided. The method includes receiving a write instruction that is associated with a writable entity, the write instruction includes a writable entity identifier, and data protection metadata indicative of a relevancy of at least one data protection operation to be applied in relation to the write instruction, and participating in an execution of a relevant data protection operation, if such a relevant data protection operation exists.