Dynamic Device Identifier Binding for Storage Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems require disruptive changes, such as reconfiguration and rebooting, when data is migrated from one storage device to another with a different device identifier, leading to operational disruptions.
Innovation Solution
Implementing a method for dynamic binding of device identifiers to data storage devices, allowing a single device identifier to be detached from one storage device and attached to another without rebooting the host or reconfiguring the application, enabling seamless data operations across different storage devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If static binding of device identifier to data storage device is used, then system stability is improved, but adaptability deteriorates when data migration is required
Solution Approach 1:
The patent applies dynamics by transforming the static binding mechanism into a dynamic one. The device identifier binding is made changeable over time, allowing the same identifier to be detached from one storage device and attached to another. This enables the system to adapt to data migration requirements while maintaining identifier consistency, directly resolving the contradiction between binding stability and migration flexibility.
Solution Approach 2:
The patent changes the parameter of binding state from fixed to variable. By introducing dynamic binding capabilities, the system can modify the association between device identifiers and storage devices based on operational needs. This parameter change allows the system to maintain stability during normal operation while enabling flexible adaptation during data migration.
2Adaptability or versatility
If data migration between storage devices is performed, then data management flexibility is improved, but operational disruption increases
Solution Approach 1:
The patent introduces a binding manager as an intermediary component that mediates between data migration operations and application operations. This mediator handles the complex task of detaching identifiers from source devices and attaching them to destination devices transparently, isolating the disruption to applications and maintaining operational continuity during migration.
Solution Approach 2:
The patent replaces the traditional mechanical approach of reconfiguring applications and rebooting systems with a software-based dynamic binding mechanism. By substituting the manual reconfiguration process with automated identifier detachment and attachment operations, the system achieves data migration flexibility without the operational disruptions traditionally associated with migration.
3Adaptability or versatility
If host reconfiguration is required for data migration, then data storage flexibility is improved, but time consumption increases
Solution Approach 1:
The patent implements self-service by enabling the binding manager to automatically handle identifier detachment and attachment operations without requiring manual host reconfiguration. The system performs the migration-related binding changes autonomously, eliminating the time-consuming manual intervention traditionally required when migrating data between storage devices.
Solution Approach 2:
The patent applies preliminary action by pre-establishing the dynamic binding framework and binding manager before data migration occurs. This preliminary setup enables rapid, automated identifier redistribution during migration operations, eliminating the need for time-consuming host reconfiguration and boot operations that would otherwise be required.
Data Source
AI summary
Described are techniques for performing dynamic binding of device identifiers to data storage devices. A first device identifier assigned to an application on a host is received. The first device identifier is a unique detachable device identifier dynamically bound to different data storage devices at different points in time in accordance with data storage devices used by the application. The first device identifier is attached to a first data storage device of the data storage system used by the application at a first point in time. The first device identifier is detached from the first data storage device thereby making the first data storage device unavailable for data operations from the application. The first device identifier is attached to a second data storage device used by the application at a second point in time thereby making the second data storage device available for data operations from the application.


