SYSTEM AND METHOD FOR DEVELOPING AND IMPLEMENTING A MIGRATION PLAN FOR MIGRATING A FILE SYSTEM

• US 20160041996A1
• Filed: 08/11/2014
• Published: 02/11/2016
• Est. Priority Date: 08/11/2014
• Status: Abandoned Application

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Prinz, Alfred G. III, Ray, Fountain L. III, Heath, Douglas Tharon
• Application Number:
  US14/456,991
• Publication Number:
  US 20160041996A1
• 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
• CPC Class Codes: G06F 16/185 Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof details of archiving G06F16/11
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A migration plan is used to create a namespace for the destination file system based at least in part on a namespace of the source file system. The migration plan is also used to determine a destination collection of policies for implementation on the destination file system. At least one of the namespace or the collection of destination policies include an operator-specific configuration that is specified by the one or more rules or parameters of the operator input.

Claims

1. A method for implementing a file system migration as between a source file system and a destination file system, the method being implemented by one or more processors and comprising:

determining a migration plan for the file system migration, the migration plan mapping each of (i) a set of file system objects from the source file system to a corresponding set of file system objects at the destination file system, and (ii) a source policy collection for the set of file system objects to a destination policy collection for the corresponding set of file system objects as the destination file system, wherein the migration plan includes a set of parameters that are based at least in part on an operator input; and

implementing the migration of the file system objects using the migration plan, the migration plan specifying, for at least a first object container of the corresponding set of file system objects at the destination file system, at least one of a file contextual path, type, or policy implementation relating to the first object container, that is different as compared to a file path, type or policy implementation of a corresponding source object container of the set of file system objects of the source file system.

2. The method of claim 1, further comprising providing a user interface to receive the operator input, the user interface including a plurality of feature sets, the user interface including at least a type feature set to enable the operator to specify a parameter for implementing a first conversion rule to migrate one or more source object containers of a first container type as a corresponding one or more destination object containers of a second container type on the destination file system.

3. The method of claim 2, wherein the parameter is a global parameter that implements the first conversion rule to migrate all source object containers of the first container type in at least a given portion of the source file system as corresponding destination file system objects of the second type on the destination file system.

4. The method of claim 2, wherein the parameter is a selective parameter that implements the first conversion rule on an input specified set of source object containers of the first type in at least a given portion of the source file system as corresponding destination file system objects of the second type on the destination file system.

5. The method of claim 1, further comprising providing a user interface to receive the operator input, the user interface including a plurality of feature sets, including at least a location feature set to enable the operator to specify a parameter for implementing a mapping rule to specify a path for a set of destination object containers as compared to a corresponding set of source object containers.

6. The method of claim 1, further comprising providing a user interface to receive the operator input, to enable an operator to specify an input that specifies (i) a first parameter to migrate at least a first source object container of a first container type as a corresponding destination object container of a second container type, and (ii) a second parameter to implement a container-specific policy on the corresponding destination object container, the container-specific policy being available on the destination file system for the second container type and not the first container type.

7. The method of claim 1, further comprising providing a user interface to receive the operator input, to enable an operator to specify an input that specifies (i) a first parameter to migrate at least a first source object container of a first container type as a corresponding destination object container of a second container type, and (ii) a second parameter for implementing a mapping rule to specify a file path for the corresponding destination object container that is contextually different than the file path of the first source object container.

8. The method of claim 1, wherein the migration plan includes a set of parameters that are implemented by default and alterable by input from an operator.

9. The method of claim 1, wherein implementing the migration of the file system objects using the migration plan includes causing a quota tree or directory container on the source file system to be migrated as a volume container on the destination file system.

10. The method of claim 6, wherein the first object container of the destination file system is a volume, and the corresponding source object container of the source file system is a quota tree or directory.

11. The method of claim 1, wherein the migration plan includes a set of conversion rules for implementing the migration as between a source architecture of the source file system and a destination architecture of the destination file system, wherein the source and destination architectures are different.

12. A method for implementing a file system migration as between a source file system and a destination file system, the method being implemented by one or more processors and comprising:

determining a migration plan for the file system migration, the migration plan including a set of parameters and a set of rules, including one or more parameters or rules that are based on an operator input;

determining each of (i) a namespace for the source file system, the namespace identifying a set of file system objects and a file path for each of the file system objects in the set of file system objects, and (ii) a collection of source policies that are implemented for file system objects identified in the namespace of the source file system;

using the migration plan to create a namespace for the destination file system based at least in part on the namespace of the source file system; and

using the migration plan to determine a collection of destination policies for implementation on the destination file system, the collection of destination policies being based at least in part on the collection of source policies;

wherein at least one of the namespace or the collection of destination policies include an operator-specific configuration that is specified by the one or more rules or parameters of the operator input.

13. The method of claim 12, wherein using the migration plan to create the namespace for the destination file system includes creating the namespace of the destination file system in accordance with a destination architecture of the destination file system, the destination architecture being different than a source architecture.

14. The method of claim 13, wherein using the migration plan to create the namespace of the destination file system includes converting a set of entries for the namespace of the source file system, which individually specify one or more of a file path or policy for individual file system objects in the set of file system objects, into a corresponding set of entries for the namespace of the destination file system.

15. The method of claim 14, wherein using the migration plan to convert the set of entries includes converting individual entries in the set of entries from a source format and structure into a destination format and structure.

16. The method of claim 15, wherein converting the set of entries includes determining the set of entries for the namespace of the destination file system that are logically equivalent to the set of entries for the namespace of the source file system.

17. The method of claim 14, wherein using the migration plan to determine a collection of destination policies includes grouping multiple policy entries in the destination format into a single logically equivalent policy entry.

18. The method of claim 14, wherein using the migration plan to create the namespace of the destination file system includes generating one or more entries in the corresponding set of entries for the namespace of the destination file system to specify that a given destination object container is of a different container type than that of a corresponding source object container.

19. The method of claim 14, wherein using the migration plan to create the namespace of the destination file system includes generating one or more entries in the corresponding set of entries for the namespace of the destination file system to specify that a given destination object container has a different contextual file path or policy than that of a source object container.

20. A non-transitory computer-readable medium that stores instruction for implementing a file system migration as between a source file system and a destination file system, the instructions being executable by one or more processors of a computer system to cause the computer system to perform operations that comprise:

determining a migration plan for the file system migration, the migration plan including a set of parameters and a set of rules, including one or more parameters or rules that are based on an operator input;

determining each of (i) a namespace for the source file system, the namespace identifying a set of file system objects and a file path for each of the file system objects in the set of file system objects, and (ii) a collection of source policies that are implemented for file system objects identified in the namespace of the source file system;

using the migration plan to create a namespace for the destination file system based at least in part on the namespace of the source file system; and

using the migration plan to determine a collection of destination policies for implementation on the destination file system, the collection of destination policies being based at least in part on the collection of source policies;

wherein at least one of the namespace or the collection of destination policies include an operator-specific configuration that is specified by the one or more rules or parameters of the operator input.