In-Place Data Modification via Holding Area Copy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems face challenges in performing non-disruptive in-place data modification, such as encryption, without disrupting application access or requiring additional storage space, and with minimal risk of data loss.
Innovation Solution
A method involving copying source data to a holding storage area, diverting I/O operations to the copy, tracking changes, incorporating modifications back into the source data, and suspending I/O operations if changes are below a threshold, allowing for seamless resumption of operations while maintaining the holding area as a backup.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is unloaded from source storage area for modification, then data modification can be performed, but application access to data is disrupted
Solution Approach 1:
The patent creates a copy of the source data in a holding storage area before modification. This copy serves as the active data that applications access, while the original source data remains intact and can be modified. The copy mechanism allows modification operations to proceed without disrupting application access to the data.
Solution Approach 2:
The holding storage area acts as an intermediary between the source storage area and applications. It receives copies of source data, allows modifications to be applied to these copies, and maintains them as active data for application access. This intermediary layer decouples the modification process from application access, resolving the contradiction between being able to modify data and maintaining continuous access.
2Productivity
If data is migrated to a new device for non-disruptive access, then application access continues, but increased permanent space requirements are needed
Solution Approach 1:
The patent segments the storage architecture into distinct functional areas: source storage area for original data, holding storage area for active data copies, and modification workspace. The holding storage area is used temporarily during the modification process rather than being a permanent migration destination, reducing the total storage space required compared to full data migration approaches.
Solution Approach 2:
The holding storage area is used temporarily to hold data copies during the modification process. Once modifications are complete and verified, the holding storage area resources can be recovered or reused, rather than requiring permanent allocation of additional storage space for migrated data.
3Quantity of substance
If data is modified in-place without backup, then storage space is preserved, but risk of data loss increases
Solution Approach 1:
The patent creates a protective copy of the source data in the holding storage area before performing modifications. This copy serves as a cushion or safety buffer - if modifications fail or corrupt the source data, the copy remains intact and can be used for recovery. This beforehand copying reduces data loss risk while maintaining storage space efficiency through the temporary nature of the holding area.
Solution Approach 2:
By creating a copy in the holding storage area before modification, the system establishes a backup mechanism that doesn't require permanent additional storage allocation. The copy protects against data loss during the modification process, and the holding area resources can be recovered after successful modification, balancing data protection with storage efficiency.
4Reliability
If I/O operations are continuously diverted to data copy, then source data can be modified safely, but performance overhead increases
Solution Approach 1:
The patent implements periodic synchronization between the holding storage area and source storage area, rather than continuous real-time operations. I/O operations are diverted to the data copy during modification periods, and changes are periodically incorporated back to the source data. This periodic approach reduces the performance overhead of continuous diversion while maintaining modification safety through the copy mechanism.
Data Source
AI summary
Non-disruptive modification of data in-place includes generating a copy of source data to a holding area. Data modification, such as encryption and/or other transformation process, may be performed on the source data in the source area while I/O operations of applications needing access to the source data is diverted to the data copy in the holding area. Updates to the data copy in the holding area from the continued I/O operations are tracked and the data updates are modified and transferred to the source area. Following successful modification of the source data, the I/O operations of the applications are re-directed back to the source area having the newly modified source data. The holding area may then be freed for subsequent use.