File-Level RAID Protection via Metadata Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional RAID systems lack the ability to define RAID protection levels on a file-by-file basis, instead relying on a lower pool level, which limits flexibility and efficiency in data protection and storage capacity utilization.
Innovation Solution
A method and system that allow each file to include metadata defining its RAID protection level, mapping this level to a corresponding physical protection level, and storing each block of the file accordingly, enabling file-level defined RAID protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If RAID protection level is defined at pool level (conventional approach), then system complexity is reduced and ease of operation is improved, but flexibility and adaptability are worsened because all files must use the same protection level
Solution Approach 1:
The patent segments the RAID protection level configuration from pool level to file level. Each file can now have its own protection level metadata, allowing different protection levels (RAID 0, 1, 5, 6, 10, etc.) to be applied to different files within the same storage pool. This segmentation enables fine-grained control over data protection while maintaining the underlying pool structure.
Solution Approach 2:
The system introduces dynamic protection level assignment where files can be migrated between different protection levels based on changing requirements. The file-based approach allows protection levels to be adjusted individually for each file, enabling dynamic adaptation to different data importance and access patterns without reconfiguring the entire pool.
2Adaptability or versatility
If file-level RAID protection is implemented, then adaptability and flexibility are improved, but device complexity and operational complexity increase
Solution Approach 1:
The system implements self-service through automated file-based protection level management. The storage system automatically reads protection level metadata from each file, determines the appropriate physical protection level, and applies it during storage operations. This automation eliminates the need for manual configuration of each file's protection level, reducing operational complexity despite the increased flexibility.
Solution Approach 2:
The patent introduces an intermediary layer that translates file-level protection level metadata into physical storage configurations. This intermediary mechanism handles the complexity of file-level management by automatically mapping logical protection requirements to physical RAID implementations, shielding users from the underlying complexity while enabling fine-grained control.
3Quantity of substance
If uniform protection level is applied to all files (pool level), then ease of operation is improved, but storage capacity utilization is worsened due to unnecessary copies of less important data
Solution Approach 1:
The patent applies local quality by assigning different protection levels to different files based on their specific requirements. Critical files receive higher protection (e.g., RAID 6 with dual parity), while less important files use lower protection (e.g., RAID 0 or RAID 1). This localized approach optimizes storage capacity utilization by avoiding unnecessary redundancy for non-critical data while maintaining strong protection for important files.
Solution Approach 2:
The system changes the protection level parameter on a per-file basis rather than applying a uniform parameter across the entire pool. By allowing individual files to have different protection level parameters, the system optimizes storage capacity usage by matching redundancy levels to actual data importance, thereby reducing wasted storage space on unnecessary copies.
Data Source
AI summary
A RAID (redundant array of independent storage devices) storage system where a file is stored at a physical protection level corresponding to a RAID protection level defined by metadata included in and/or with the file to be stored.