Vserver Migration Between Clusters With Asynchronous Baseline Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage virtual machine (Vserver) migration technologies face challenges in efficiently transferring configuration information and data volumes from a source cluster to a destination cluster with minimal disruption to client systems, leading to potential data access interruptions.
Innovation Solution
A multi-phase migration process involving setup, transfer, cutover commit, post-cutover, and cleanup phases, utilizing group control, orchestration for failure handling, logical interface and volume placement, asynchronous data transfer, and a locking mechanism to ensure seamless migration with minimal disruption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Vserver migration is performed from source cluster to destination cluster, then storage system flexibility and resource optimization are improved, but data access interruption and migration time increase
Solution Approach 1:
The patent applies preliminary action by creating a destination Vserver and copying configuration information before the actual data migration. The destination Vserver is prepared in advance with all necessary settings, and configuration replication is performed before data transfer begins, enabling faster migration and reducing overall migration time.
Solution Approach 2:
The migration process is segmented into distinct phases: setup phase (creating destination Vserver and copying configuration), transfer phase (moving data volumes), cutover commit phase (switching active connections), and cleanup phase (removing source Vserver). This segmentation allows each phase to be optimized independently and enables parallel operations that reduce total migration time.
2Adaptability or versatility
If Vserver migration is performed, then storage resource optimization is improved, but data access disruption increases
Solution Approach 1:
The patent ensures continuity of useful action by maintaining dual-active Vservers during migration. The source Vserver continues serving client requests while the destination Vserver is being populated with data. Client connections are seamlessly switched from source to destination without interruption, ensuring continuous data access throughout the migration process.
Solution Approach 2:
The migration system acts as an intermediary between source and destination clusters, managing the transition of data and connections. The system coordinates configuration replication, data transfer, and connection switching to ensure that client access remains uninterrupted during the migration process.
3Productivity
If configuration information and data volumes are transferred, then Vserver migration completeness is improved, but migration complexity increases
Solution Approach 1:
Configuration information is copied to the destination Vserver during the setup phase before data volume transfer begins. This preliminary action includes copying Vserver configuration, volume settings, and metadata, which simplifies the subsequent data transfer process and ensures migration completeness without increasing operational complexity.
Solution Approach 2:
The patent merges configuration replication and data volume transfer into a coordinated migration process. The setup and transfer phases are integrated with proper sequencing, where configuration is prepared first and then data is transferred, reducing the overall complexity compared to handling these operations separately.
Data Source
AI summary
Methods and systems for Vserver migration are provided. One method includes executing a transfer phase of a migrate operation for migrating a Vserver of a source cluster to a destination cluster, using asynchronous baseline transfer to transfer a plurality of source storage volumes configured in a consistency group (CG) for the migrate operation to a plurality of destination storage volumes of a destination cluster; updating a state of each of the plurality of source storage volumes to a sync state indicating completion of a pre-commit phase of the migrate operation to initiate a commit phase of the migrate operation; and generating a snapshot of the plurality of destination storage volumes for performing data integrity checks between data stored at the source cluster and migrated data at destination cluster, after completing a commit phase of the migrate operation.