US 12,423,125 B2
Methods and systems for storage virtual machine migration between clusters of a networked storage system
Atul Ramesh Pandit, Los Gatos, CA (US); Kalaivani Arumugham, Sunnyvale, CA (US); Akhil Kaushik, Bangalore (IN); Ching-Yuk Paul Ngan, Redwood City, CA (US); Kazunobu Nishime, Milpitas, CA (US); Rakesh Bhargava M R, Bangalore (IN); and William R. Taylor, San Jose, CA (US)
Assigned to NETAPP, INC., San Jose, CA (US)
Filed by NETAPP, INC., San Jose, CA (US)
Filed on Apr. 26, 2022, as Appl. No. 17/729,885.
Claims priority of application No. 202141049497 (IN), filed on Oct. 29, 2021.
Prior Publication US 2023/0137443 A1, May 4, 2023
Int. Cl. G06F 9/455 (2018.01); G06F 9/50 (2006.01)
CPC G06F 9/45558 (2013.01) [G06F 9/5016 (2013.01); G06F 9/5072 (2013.01); G06F 9/5077 (2013.01); G06F 2009/4557 (2013.01); G06F 2009/45579 (2013.01); G06F 2009/45583 (2013.01); G06F 2009/45595 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
executing, by a processor, a transfer phase of a migrate operation for migrating a source storage virtual machine (Vserver) of a source cluster to a destination cluster, the transfer phase using asynchronous baseline transfer to transfer data and configuration of a plurality of source storage volumes configured in a consistency group (CG) for the migrate operation to a plurality of destination storage volumes of the destination cluster;
wherein the asynchronous baseline transfer is managed as a group;
updating, by the processor, 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;
locking, by the processor, the source Vserver to prevent any configuration changes for a certain duration during the commit phase, while persistently maintaining a state of the migrate operation at both the source cluster and destination cluster;
generating, by the processor, 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 the destination cluster, after completing the commit phase;
transitioning, by the processor, the migrate operation state to a point of no return state (PONR), upon completing the commit phase and initializing the Vserver at the destination cluster for processing input/output requests; and
retaining, by the processor, a snapshot of the source Vserver and restarting the source Vserver, if the migrate operation fails.