File System Migration Without Client Unmounting

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data migration systems disrupt client access to file systems during the migration process, requiring clients to unmount and causing interruptions in service.

Innovation Solution

A data migration system that intercepts communications between clients and file systems, replicates file system objects asynchronously, and manipulates attributes to maintain continuity, allowing clients to transition seamlessly from a source file system to a destination file system without interruption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data migration is performed using traditional methods, then data can be transferred from source to destination file system, but client access is disrupted and service continuity is interrupted

Engineering Contradiction:

Improveservice continuityVSAvoidmigration efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by creating a mirror copy of the source file system at the destination before actual migration begins. This mirror copy is prepared in advance with all necessary file system objects, attributes, and structures, enabling seamless switching later without disrupting client access during the migration process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism that captures client requests during migration and redirects them appropriately. This intermediary layer ensures that clients continue to access files without interruption while data is being migrated in the background, maintaining service continuity throughout the migration process.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If file system objects are replicated asynchronously, then service interruption is minimized, but attribute consistency between source and destination must be maintained

Engineering Contradiction:

Improvemigration speedVSAvoidattribute consistency

Core Design Contradiction:

ProductivityVSManufacturing precision

Solution Approach 1:

The system implements feedback mechanisms that continuously monitor and compare attributes between source and destination file system objects during asynchronous replication. This feedback ensures that even though replication occurs asynchronously for speed, attribute consistency is maintained through continuous verification and correction.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent utilizes parameter changes by manipulating file system attributes (such as timestamps, ownership, permissions) to ensure consistency between source and destination. By carefully controlling and adjusting these parameters during replication, the system maintains attribute accuracy while benefiting from asynchronous replication speed.

Inventive Principle:

Principle #35Parameter changes

3Ease of manufacture

If clients are required to unmount from source file system, then migration can proceed, but access latency increases and performance is degraded

Engineering Contradiction:

Improvemigration simplicityVSAvoidaccess latency

Core Design Contradiction:

Ease of manufactureVSLoss of time

Solution Approach 1:

The system maintains continuity of useful action by allowing clients to keep mounted and accessing the source file system throughout the migration process. Data is replicated in the background without requiring clients to unmount or interrupt their operations, eliminating access latency and performance degradation associated with traditional migration methods.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS9311314B2System and method for migrating data from a source file system to a destination file system with use of attribute manipulation

Publication Date: 2016.04.12 NETAPP INC

AI summary

A system for migrating data from a source file system to a destination file system while the source file system is in active use, in part by transitioning the client's use of the source file system to that of the destination file system without unmounting the client from the source file system.