SEAMLESS MIGRATION OF STUBS AND DATA BETWEEN DIFFERENT FILER TYPES

1 . A method for migrating one or more sub-clients of a source filer to one or more sub-clients of a destination filer, the method comprising:

receiving a request to migrate data of a source filer to a destination filer;

identifying one or more sub-clients of the source filer, wherein at least one sub-client of the one or more sub-clients comprises a logical grouping of data associated with a data agent of a client computing device in communication with the source filer;

presenting the identified one or more sub-clients to a user of a client computing device, wherein the presenting comprises displaying a prompt requesting a selection of one or more sub-clients from the identified one or more sub-clients;

receiving a selection of one or more sub-clients from the identified one or more sub-clients;

creating one or more sub-clients on the destination filer, wherein each sub-client of the one or more sub-clients of the destination filer corresponds to a sub-client of the selected one or more sub-clients;

synchronizing data of each sub-client of the selected one or more sub-clients with a corresponding sub-client of the created one or more sub-clients on the destination filer, wherein synchronizing comprises:

identifying a file of a sub-client of the selected one or more sub-clients;

determining whether the identified file is a first stub file, wherein the first stub file is a reference to data stored in a secondary storage device in communication with the source filer;

creating a second stub file referencing the data referenced by the first stub file; and

storing the second stub file at a sub-client of the one or more created sub-clients on the destination filer; and

generating a notification to an administrator of the source filer that the synchronization is completed.

2 . The method of claim 1 , wherein the first stub file is compatible with the source filer, and not compatible with the destination filer, and the second stub file is compatible with the destination filer, and not compatible with the source filer.

3 . The method of claim 1 , wherein the second stub file is created based on a filer type of the destination filer.

4 . The method of claim 1 , wherein the selected one or more sub-clients is less than all of the identified one or more sub-clients.

5 . The method of claim 1 , further comprising:

receiving a cutoff date by which to migrate data of the selected one or more sub-clients from the source filer to the destination filer;

determining whether the current date is the cutoff date; and

in response to a determination that the current date is the cutoff date, determining whether there is a difference in the data of each sub-client of the selected one or sub-clients with their corresponding sub-client on the destination filer.

6 . The method of claim 1 , further comprising:

in response to a determination that there is a difference in the data of at least one sub-client of the selected one or sub-clients with its corresponding sub-client on the destination filer, performing a synchronization of data between the corresponding sub-clients having the determined differences.

7 . The method of claim 6 , further comprising:

disabling access to the source filer after the synchronization is performed between the sub-clients having the differences in data determined after the determination is made that the current date is the cutoff date.

8 . The method of claim 1 , further comprising:

receiving a cutoff date by which to migrate data of the selected one or more sub-clients from the source filer to the destination filer;

determining whether the current date is the cutoff date; and

requesting authorization to perform a cutover from the source filer to the destination filer, wherein the cutover from the source filer to the destination filer comprises:

updating a data agent of the client computing device to use a sub-client on the destination filer rather than the corresponding sub-client on the source filer.

9 . A system for migrating one or more sub-clients of a source filer to one or more sub-clients of a destination filer, the system comprising:

one or more non-transitory, computer-readable mediums having computer-executable instructions stored thereon; and

one or more processors that, having executed the computer-executable instructions, configure the system to perform a plurality of operations comprising:

receiving a request to migrate data of a source filer to a destination filer;

identifying one or more sub-clients of the source filer, wherein at least one sub-client of the one or more sub-clients comprises a logical grouping of data associated with a data agent of a client computing device in communication with the source filer;

presenting the identified one or more sub-clients to a user of a client computing device, wherein the presenting comprises displaying a prompt requesting a selection of one or more sub-clients from the identified one or more sub-clients;

receiving a selection of one or more sub-clients from the identified one or more sub-clients;

creating one or more sub-clients on the destination filer, wherein each sub-client of the one or more sub-clients of the destination filer corresponds to a sub-client of the selected one or more sub-clients;

synchronizing data of each sub-client of the selected one or more sub-clients with a corresponding sub-client of the created one or more sub-clients on the destination filer, wherein synchronizing comprises:

identifying a file of a sub-client of the selected one or more sub-clients;

determining whether the identified file is a first stub file, wherein the first stub file is a reference to data stored in a secondary storage device in communication with the source filer;

creating a second stub file referencing the data referenced by the first stub file; and

storing the second stub file at a sub-client of the one or more created sub-clients on the destination filer; and

generating a notification to an administrator of the source filer that the synchronization is completed.

10 . The system of claim 9 , wherein the first stub file is compatible with the source filer, and not compatible with the destination filer, and the second stub file is compatible with the destination filer, and not compatible with the source filer.

11 . The system of claim 9 , wherein the second stub file is created based on a filer type of the destination filer.

12 . The system of claim 9 , wherein the selected one or more sub-clients is less than all of the identified one or more sub-clients.

13 . The system of claim 9 , wherein the plurality of operations further comprises:

receiving a cutoff date by which to migrate data of the selected one or more sub-clients from the source filer to the destination filer;

determining whether the current date is the cutoff date; and

in response to a determination that the current date is the cutoff date, determining whether there is a difference in the data of each sub-client of the selected one or sub-clients with their corresponding sub-client on the destination filer.

14 . The system of claim 9 , wherein the plurality of operations further comprises:

in response to a determination that there is a difference in the data of at least one sub-client of the selected one or sub-clients with its corresponding sub-client on the destination filer, performing a synchronization of data between the corresponding sub-clients having the determined differences.

15 . The system of claim 14 , wherein the plurality of operations further comprises:

disabling access to the source filer after the synchronization is performed between the sub-clients having the differences in data determined after the determination is made that the current date is the cutoff date.

16 . The system of claim 9 , wherein the plurality of operations further comprises:

receiving a cutoff date by which to migrate data of the selected one or more sub-clients from the source filer to the destination filer;

determining whether the current date is the cutoff date; and

requesting authorization to perform a cutover from the source filer to the destination filer, wherein the cutover from the source filer to the destination filer comprises:

updating a data agent of the client computing device to use a sub-client on the destination filer rather than the corresponding sub-client on the source filer.

17 . A non-transitory, computer-readable medium having computer-executable instructions stored thereon that, when executed by one or more processors, cause a system to perform a plurality of operations comprising:

receiving a request to migrate data of a source filer to a destination filer;

identifying one or more sub-clients of the source filer, wherein at least one sub-client of the one or more sub-clients comprises a logical grouping of data associated with a data agent of a client computing device in communication with the source filer;

presenting the identified one or more sub-clients to a user of a client computing device, wherein the presenting comprises displaying a prompt requesting a selection of one or more sub-clients from the identified one or more sub-clients;

receiving a selection of one or more sub-clients from the identified one or more sub-clients;

creating one or more sub-clients on the destination filer, wherein each sub-client of the one or more sub-clients of the destination filer corresponds to a sub-client of the selected one or more sub-clients;

synchronizing data of each sub-client of the selected one or more sub-clients with a corresponding sub-client of the created one or more sub-clients on the destination filer, wherein synchronizing comprises:

identifying a file of a sub-client of the selected one or more sub-clients;

determining whether the identified file is a first stub file, wherein the first stub file is a reference to data stored in a secondary storage device in communication with the source filer;

creating a second stub file referencing the data referenced by the first stub file; and

storing the second stub file at a sub-client of the one or more created sub-clients on the destination filer; and

generating a notification to an administrator of the source filer that the synchronization is completed.

18 . The non-transitory, computer-readable medium of claim 17 , wherein:

the first stub file is compatible with the source filer, and not compatible with the destination filer, and

the second stub file is compatible with the destination filer, and not compatible with the source filer.

19 . The non-transitory, computer-readable medium of claim 17 , wherein the second stub file is created based on a filer type of the destination filer.

20 . The non-transitory, computer-readable medium of claim 17 , wherein the selected one or more sub-clients is less than all of the identified one or more sub-clients.