Providing virtual storage processor (VSP) mobility with induced file system format migration

Patent metadata

Field	Value
Publication number	US-9305071-B1
Application number	US-201314041097-A
Country	US
Kind code	B1
Filing date	Sep 30, 2013
Priority date	Sep 30, 2013
Publication date	Apr 5, 2016
Grant date	Apr 5, 2016

Abstract

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.

First claim

What is claimed is:

1. A method of providing virtual storage processor (VSP) mobility and induced file system format migration, the method comprising:
receiving, by processing circuitry, a VSP move command from a user, the VSP move command specifying (i) a source VSP which includes multiple source file systems which store data in a source file system format using block pointers having a first block pointer size defined by the source file system format, (ii) a destination, and (iii) a destination file system format which is different than the source file system format;
in response to the VSP move command, forming, by the processing circuitry, a destination VSP which includes multiple destination file systems;
while the source VSP is accessed by a set of host computers, copying, by the processing circuitry, data from the multiple source file systems of the source VSP to the multiple destination file systems of the destination VSP, the multiple destination file systems storing the copied data in the destination file system format using block pointers having a second block pointer size defined by the destination file system format, the second block pointer size being different than the first block pointer size; and
after the data is copied from the multiple source file systems to the multiple destination file systems, synchronizing, by the processing circuitry, state changes between the source VSP and the destination VSP.

2. A method as in claim 1 wherein the source VSP includes (i) a first set of configuration file systems storing source VSP configuration data and (ii) a first set of host file systems storing host data; and wherein forming the destination VSP includes:
providing (i) a second set of configuration file systems to store destination VSP configuration data and (ii) a second set of host file systems to store a copy of the host data, the first and second sets of configuration file systems being transparent to the set of host computers, and the first and second sets of host file systems being visible to the set of host computers.

3. A method as in claim 2 wherein the first set of configuration file systems and the first set of host file systems include existing inode structures to store the data using the block pointers having the first block pointer size defined by the source file system format; and wherein providing the second set of configuration file systems and the second set of host file systems includes:
provisioning the second set of configuration file systems and the second set of host file systems with new inode structures to store the copied data using the block pointers having the second block pointer size defined by the destination file system format.

4. A method as in claim 3 wherein a configuration database holds multiple VSP records corresponding to multiple VSPs; and wherein forming the destination VSP includes:
based on the VSP move command, (i) reading an existing set of entries from the configuration database to identify the first set of configuration file systems and the first set of host file systems of the source VSP, and (ii) creating a new set of entries in the configuration database to define the second set of configuration file systems and the second set of host file systems of the destination VSP, wherein reading the existing set of entries and creating the new set of entries is transparent to the set of host computers.

5. A method as in claim 3 wherein the source VSP resides in a source storage pool of a data storage array; wherein the destination VSP resides in a destination storage pool of the data storage array; and wherein copying the data from the multiple source file systems to the multiple destination file systems includes:
copying the data from the source storage pool and storing the copied data in the destination storage pool of the data storage array.

6. A method as in claim 3 wherein copying the data from the multiple source file systems to the multiple destination file systems while the source VSP is accessed by the set of host computers includes:
processing host input/output (I/O) requests directed to the first set of host file systems of the source VSP using the existing inode structures having the first block pointer size.

7. A method as in claim 6 wherein synchronizing the state changes between the source VSP and the destination VSP includes:
processing further host I/O requests directed to the first set of host file systems of the source VSP using the existing inode structures having the first block pointer size, and
copying new data stored in the first set of host file systems of the source VSP, and storing the copied new data in the second set of host file systems of the destination VSP using the new inode structures having the second block pointer size.

8. A method as in claim 6 wherein synchronizing the state changes between the source VSP and the destination VSP includes:
while processing host read requests from the second set of host file systems of the destination VSP using the new inode structures having the second block pointer size, copying new data stored in the first set of host file systems of the source VSP, and storing the copied new data in the second set of host file systems of the destination VSP using the new inode structures having the second block pointer size.

9. A method as in claim 3 wherein associations exist between (i) files of the first set of configuration file systems and the first set of host file systems and (ii) inode numbers of the existing inode structures; wherein provisioning the second set of configuration file systems and the second set of host file systems with new inode structures includes:
identically assigning inode numbers of the new inode structures to files of the second set of configuration file systems and the second set of host file systems to preserve, at the destination VSP, the associations exist between (i) the files of the first set of configuration file systems and the first set of host file systems and (ii) the inode numbers of the existing inode structures.

10. A method as in claim 9 wherein provisioning the second set of configuration file systems and the second set of host file systems with new inode structures further includes:
populating the new inode structures with inode structure attributes from the existing inode structure to maintain file attributes between (i) the files of the first set of configuration file systems and the first set of host file systems of the source VSP and (ii) the files of the second set of configuration file systems and the second set of host file systems of the destination VSP.

11. A method as in claim 3 , further comprising:
receiving a VSP rollback command from the user, the VSP rollback command identifying the destination, and
in response to the VSP rollback command, terminating synchronization of the state changes between the source VSP and the destination VSP to rollback to using the source VSP for primary access to the data.

12. A method as in claim 3 , further comprising:
receiving a VSP commit command from the user, the VSP commit command identifying the destination, and
in response to the VSP commit command, (i) preventing processing of new host input/output (I/O) requests in the source VSP, (ii) terminating synchronization of the state changes between the source VSP and the destination VSP, and (iii) processing the new host I/O requests in the destination VSP using the new inode structures having the second block pointer size.

13. A method as in claim 1 wherein synchronizing the state changes between the source VSP and the destination VSP includes:
after the data is copied from th

Assignees

• Emc Corp

Inventors

• Bono Jean-Pierre
• Corniquet Frederic
• De Forest Miles A
• Tummala Himabindu
• Forrester Walter C

Classifications

• G06F17/30575 Primary

  Physics · mapped topic

• G06F16/119 Primary

  Details of migration of file systems (migration mechanisms in storage systems G06F3/0647) · CPC title