Multi-Protocol Migration Name Consistency via Cached Minority Names
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During multi-protocol file system migrations, name operations across different protocols like CIFS and NFS can result in inconsistencies due to differing name restrictions, leading to issues in maintaining identical file names on source and destination servers.
Innovation Solution
A method where a first directory entry is created using a majority protocol on the source side for a multi-protocol delta copy migration session, with minority protocol name information relayed and cached on the destination side, allowing the creation of a second directory entry using the majority protocol and resetting its name to the minority protocol name, ensuring consistency across protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If directory entries are created using majority protocol names during migration, then migration simplicity is improved, but name consistency between source and destination deteriorates due to different protocol name restrictions
Solution Approach 1:
The system performs preliminary actions by creating directory entries with majority protocol names first during the migration process, then subsequently updates them with the correct minority protocol names. This two-stage approach allows the migration to proceed smoothly initially while ensuring name consistency is established afterward.
Solution Approach 2:
The patent introduces an intermediary mechanism that maps between majority and minority protocol names. This intermediary layer handles the translation and coordination between the two naming systems, allowing directory entries to be created with one protocol's naming conventions while maintaining compatibility with the other protocol's restrictions.
2Manufacturing precision
If minority protocol name restrictions are enforced during migration, then name consistency is improved, but migration complexity increases
Solution Approach 1:
Instead of enforcing minority protocol name restrictions from the beginning, the system allows majority protocol names to be used during the initial migration phase. The enforcement of minority protocol naming conventions is deferred to a subsequent update stage, reducing initial migration complexity while still achieving name consistency.
Solution Approach 2:
The system dynamically adjusts its naming approach based on the migration stage. During the initial copy phase, it uses majority protocol names for simplicity. During the update phase, it transitions to enforcing minority protocol names for consistency. This dynamic behavior reduces overall complexity by adapting constraints to contextual needs.
3Productivity
If directory entries are created with majority protocol names on destination, then migration speed is improved, but file system integrity deteriorates due to protocol-specific name restrictions
Solution Approach 1:
The system performs a preliminary directory entry creation step using majority protocol names to achieve fast migration. This is followed by a corrective update step that ensures file system integrity by adjusting names to comply with minority protocol restrictions. The two-stage process prioritizes speed first, then integrity.
Solution Approach 2:
The patent implements a cushioning mechanism where potential name conflicts are anticipated and handled in advance. By preparing the directory structure with majority protocol names first and then systematically updating them, the system prevents integrity issues before they propagate, rather than allowing errors to occur during normal operations.
Data Source
AI summary
A method, computer program product, and computer system for creating, by a computing device, a first directory entry with a name using a majority protocol, wherein the creation may be done on a source side for a multi-protocol delta copy migration session. Minority protocol name information associated with the first directory entry using the majority protocol may be relayed to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side. A second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session may be created on the destination side. The name of the second directory entry created using the majority protocol may be reset to the minority protocol name created using the minority protocol name information cached on the destination side.


