Virtual Storage Processor Mobility with File System Format Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data storage systems face challenges in efficiently managing and migrating virtual storage processors (VSPs) due to the intermingling of virtual data mover content within a physical storage processor's root file system, which impairs mobility and management, requiring complex steps and potential disruptions when moving file systems, settings, and servers.

Innovation Solution

The implementation of virtual storage processors as self-describing and independent entities with their own namespaces and network addresses, allowing for transparent migration and management, including induced file system format migration, where all file systems and configuration data are migrated while preserving file characteristics, enabling seamless mobility and unified management of file-based and block-based objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If VSPs are implemented as self-describing and independent entities with their own namespaces, then VSP mobility and independence are improved, but the complexity of managing format migration and data consistency increases

Engineering Contradiction:
ImproveVSP mobilityVSAvoidmigration management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the storage processor functionality into independent virtual storage processors (VSPs), each with its own namespace and configuration. This segmentation enables VSPs to be moved independently between physical storage processors while maintaining their identity and data integrity, thus improving mobility without proportionally increasing management complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements copying mechanisms to replicate VSP data and configuration from source to destination during migration. The system creates copies of file systems and maintains synchronization between source and destination VSPs, enabling seamless mobility while automating the complex tasks of data consistency management and format migration.

Inventive Principle:
Principle #26Copying

2Reliability

If all file systems and configuration data are migrated during VSP movement, then data completeness and integrity are improved, but the time required for migration and potential service disruption increase

Engineering Contradiction:
Improvedata integrityVSAvoidmigration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-configuring the destination VSP with the appropriate namespace, file system structures, and configuration data before actual data migration begins. This preliminary setup ensures that when data is copied, the destination is ready to receive and integrate it seamlessly, reducing overall migration time while maintaining complete data integrity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements continuous data synchronization mechanisms that allow the migration process to maintain data consistency between source and destination throughout the transfer. The system continuously updates the destination VSP with changes from the source, enabling migration to proceed without stopping service and minimizing disruption time while ensuring complete data integrity.

Inventive Principle:
Principle #20Continuity of useful action

3Ease of operation

If file system identifiers and inode numbers are preserved during migration, then transparency to hosts and usability are improved, but the complexity of format conversion and data mapping increases

Engineering Contradiction:
Improvehost transparencyVSAvoidformat conversion complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer in the form of a migration tool that operates within the I/O stack but above block-based storage and replication. This intermediary automatically handles the complex tasks of format conversion, data mapping, and identifier preservation, translating between different file system formats while maintaining host transparency without requiring manual intervention or increasing operational complexity for users.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If a migration tool is implemented within the I/O stack above block-based storage, then comprehensive data migration capability is improved, but the system complexity and number of components increase

Engineering Contradiction:
Improvemigration capabilityVSAvoidsystem component count
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The migration tool is designed as a universal component within the I/O stack that can handle multiple migration scenarios, file system formats, and data types through a single integrated interface. By consolidating migration functionality into one multi-functional tool rather than separate specialized components, the system achieves comprehensive migration capability while minimizing the increase in system complexity and component count.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9305071B1Providing virtual storage processor (VSP) mobility with induced file system format migration
Publication Date: 2016.04.05 EMC IP HLDG CO LLC
  • US9305071B1 patent drawing
  • US9305071B1 patent drawing
  • US9305071B1 patent drawing

AI summary

A technique provides virtual storage processor (VSP) mobility with induced file system format migration. The technique involves receiving a command specifying (i) a source VSP which includes source file systems which store data in a source file system format, (ii) a destination, and (iii) a destination file system format. The technique further involves forming, in response to the command, a destination VSP which includes destination file systems. The technique further involves copying, while the source VSP is accessed by a set of host computers, data from the source file systems of the source VSP to the destination file systems of the destination VSP. The destination file systems store the copied data in the destination file system format. The technique further involves synchronizing, after the data is copied from the source file systems to the destination file systems, state changes between the source VSP and the destination VSP.