SYSTEM AND METHOD FOR VALIDATING REPLICATION OF MUTABLE OPERATIONS PERFORMED ON A FILE SYSTEM OBJECT DURING A MIGRATION

• US 20150347425A1
• Filed: 05/29/2014
• Published: 12/03/2015
• Est. Priority Date: 05/29/2014
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: McKinion, James
• Granted Patent: US 9,547,652 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647

Abstract

Examples described herein provide for determining when individual file system operations are quiesced at a destination before validating a state of the file system object after migration. In one implementation, a metadata parameter is modified for individual file system objects after a set of mutable operations for each file system object is completed. The metadata parameter is recorded and subsequently used to determine when each of the individual file system objects are quiesced at the destination filer. The file system objects that are quiesced can be validated for migration and for implementation of any mutable file system operations that were completed at the source during the migration.

Claims

1. A non-transitory computer-readable medium that stores instructions that, when executed by one or more processors of a computer system, cause the computer system to perform operations that comprise:

(a) issuing one or more file system operations that are to be performed on each of multiple system objects of a file system data set at a source while the file system data set is migrated from the source to a destination, wherein the one or more file system operations for each of the multiple file system objects include one or more mutable operations which update at least one of a data or a metadata component of a specified file system object of the file system data set at the source;

(b) determining when each of the multiple file system objects is quiesced after the one or more mutable operation is performed on that file system object at the source; and

(c) for each file system object that is determined to be quiesced, validating that a state of the file system object at the destination replicates performance of the one or more mutable operations that are performed for the file system object at the source.

2. The non-transitory computer-readable medium of claim 1, wherein determining when each of the multiple file system objects is quiesced at the destination includes determining whether any mutable file system operation is pending or in progress for that file system object at the source.

3. The non-transitory computer-readable medium of claim 1, further comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

for each file system object, (i) updating a metadata item of the file system object from a client system upon completion of the one or more mutable operations, and (ii) recording the updated metadata item in association with the file system object.

4. The non-transitory computer-readable medium of claim 3, wherein determining when each of the multiple file system objects is quiesced includes determining whether metadata item of the file system object at the destination after completion of the one or more mutable operations is equivalent to the updated metadata item that is recorded in association with the file system object.

5. The non-transitory computer-readable medium of claim 3, wherein determining when each of the multiple file system objects is quiesced at the destination is based at least in part on the updated metadata item.

6. The non-transitory computer-readable medium of claim 3, wherein updating the metadata item is based on a predetermined logic to after the metadata item in response to completion of the one or more file system operations.

7. The non-transitory computer-readable medium of claim 6, wherein the metadata item for each of the multiple file system objects corresponds to one or more of a user identifier (UID) for the file system object, group identifier (GID) for the file system object, a size of the file system object or a set of permissions for the file system object.

8. The non-transitory computer-readable medium of claim 1, wherein (a) through (c) are performed on a client system that generates at least some of the one or more mutable operations for each of the multiple file system objects.

9. The non-transitory computer-readable medium of claim 1, wherein validating that the file system object at the destination replicates performance of the one or more mutable operations includes comparing a state of each file system object that is determined to be quiesced at the destination to a corresponding state of the file system object at the source.

10. The non-transitory computer-readable medium of claim 9, wherein comparing the state of each file system object that is determined to be quiesced at the destination to the corresponding state of the file system object at the source includes comparing one or more of a content or metadata of the file system object at each of the source and destination.

11. A method for validating replication of mutable operations on file system objects during migration, the method being implemented by one or more processors and comprising:

(a) issue one or more file system operations that are to be performed on each of multiple system objects of a file system data set at a source while the file system data set is migrated from the source to a destination, wherein the one or more file system operations for each of the multiple file system objects include one or more mutable operations which update at least one of a data or a metadata component of a specified file system object of the file system data set at the source;

(b) determining when each of the multiple file system objects is quiesced after the one or more mutable operation is performed on that file system object at the source; and

(c) for each file system object that is determined to be quiesced, validating that the file system object at the destination replicates performance of the one or more mutable operations that are performed for the file system object at the source.

12. The method of claim 11, wherein determining when each of the multiple file system objects is quiesced at the destination includes determining whether any mutable file system operation is pending or in progress for that file system object at the source.

13. The method of claim 11, further comprising:

for each file system object, (i) updating a metadata item of the file system object from a client system upon completion of the one or more mutable operations, and (ii) recording the updated metadata item in association with the file system object.

14. The method of claim 13, wherein determining when each of the multiple file system objects is quiesced includes determining whether metadata item of the file system object at the destination after completion of the one or more mutable operations is equivalent to the updated metadata item that is recorded in association with the file system object.

15. The method of claim 13, wherein determining when each of the multiple file system objects is quiesced at the destination is based at least in part on the updated metadata item.

16. The method of claim 13, wherein updating the metadata item is based on a predetermined logic to alter the metadata item in response to completion of the one or more file system operations.

17. The method of claim 16, wherein the metadata item for each of the multiple file system objects corresponds to one or more of a user identifier (UID) for the file system object, group identifier (GID) for the file system object, a size of the file system object or a set of permissions for the file system object.

18. The method of claim 11, wherein (a) through (c) are performed on a client system that generates at least some of the one or more mutable file system operations for each of the multiple file system objects.

19. The method of claim 11, wherein validating that the file system object at the destination replicates performance of the one or more mutable operations includes comparing a state of each file system object that is determined to be quiesced at the destination to a corresponding state of the file system object at the source.

20. A computer system comprising:

a memory that stores a set of instructions;

one or more processors that use the set of instructions to;

(a) issue one or more file system operations that are to be performed on each of multiple system objects of a file system data set at a source while the file system data set is migrated from the source to a destination, wherein the one or more file system operations for each of the multiple file system objects include one or more mutable operations which update at least at least one of a data or a metadata component of a specified file system object of the file system data set at the source;

(b) determine when each of the multiple file system objects is quiesced after the one or more mutable operation is performed on that file system object at the source; and

(c) for each file system object that is determined to be quiesced, validate that the file system object at the destination replicates performance of the one or more mutable operations that are performed for the file system object at the source.