Storage Controller Tagging for Replication Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Storage systems face inefficiencies in data replication due to relocated data being mistaken for new data, leading to unnecessary replication of old data during garbage collection and read optimization processes.
Innovation Solution
A storage system with a storage controller that tracks data relocation using tags and a medium history table to differentiate between user writes and system activities, preventing the replication of old data by maintaining sequence numbers and recording data evolution, thereby replicating only new data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If garbage collection and read optimization processes are executed to reduce mapping complexity, then storage system efficiency is improved, but relocated data is mistakenly identified as new data causing redundant replication
Solution Approach 1:
The system performs preliminary actions by maintaining tags alongside data during garbage collection and read optimization operations. These tags record the original write time and location of data before relocation, enabling the system to distinguish between genuinely new data and relocated data in subsequent replication operations.
Solution Approach 2:
Tags serve as an intermediary mechanism between the data and the replication system. These tags carry metadata about the data's history (original write time, location) without being part of the actual data payload, allowing the replication system to make informed decisions about what needs to be replicated without altering the data itself.
2Productivity
If data relocation is performed during garbage collection, then storage locations are freed for new data, but the relocated data appears as new data triggering unnecessary replication
Solution Approach 1:
The system performs preliminary actions by maintaining tags alongside data during garbage collection and read optimization operations. These tags record the original write time and location of data before relocation, enabling the system to distinguish between genuinely new data and relocated data in subsequent replication operations.
Solution Approach 2:
The replication system uses feedback from the tags to determine whether data needs to be replicated. By comparing the tag information (original write time, location) with current data state, the system receives feedback that indicates whether the data is newly written or merely relocated, allowing it to skip replication for relocated data and save time.
3Measurement precision
If tags and medium history tables are maintained to track data relocation, then replication accuracy is improved, but device complexity increases
Solution Approach 1:
The system merges the tag storage with the existing medium history table structure. Rather than creating entirely separate data structures, the tags are integrated into the medium history tracking mechanism, combining the functionality of data relocation tracking with the existing history table to minimize additional complexity.
Solution Approach 2:
The medium history table is enhanced to serve multiple functions: it continues to track medium hierarchy evolution while also storing tag information for data relocation tracking. This multi-functionality reduces the need for separate dedicated structures, thereby limiting the increase in device complexity while maintaining high measurement precision.
Data Source
AI summary
Systems, methods, and computer readable storage mediums for maintaining the history of remapped data in a storage system. A first portion of a first medium may be remapped to a second medium as part of read optimization operations, wherein the second medium is younger than the first medium. A tag associated with the first portion of the first medium may be retained when the first portion is remapped to the second medium. When the second medium is replicated to another storage array, the first portion of the first medium may be prevented from being replicated based on the tag identifying the first portion as being part of a previous replication operation.