Stub file selection and migration
A method comprises selecting at least a given stub file of one or more stub files for migration from a source storage location to a target storage location. The selection of the given stub file is based at least in part on a database entry comprising source storage location path information for the given stub file. The one or more stub files correspond to one or more archived files, and the one or more stub files and one or more non-stub files are stored in the source storage location. In the method, the given stub file is migrated to the target storage location without migrating the one or more non-stub files to the target storage location. The method further includes modifying the database entry by replacing the storage location path information with target storage location path information for the given stub file.
1. An apparatus comprising:
at least one processing platform comprising at least one processing device that comprises a processor coupled to a memory;
said at least one processing platform being configured:
to select at least a first stub file and a second stub file of a plurality of stub files for migration from a source storage location to a target storage location, wherein the plurality of stub files correspond to a plurality of archived files, wherein the plurality of stub files and one or more non-stub files are stored in the source storage location, wherein the selection of the first stub file and the second stub file is based at least in part on a plurality of database entries comprising source storage location path information for the first stub file and the second stub file, and wherein the plurality of database entries satisfy one or more policy constraints defined by a user;
to migrate the first stub file and the second stub file to the target storage location without migrating the one or more non-stub files to the target storage location, wherein the migrating comprises generating the first stub file and the second stub file in the target storage location;
to modify the plurality of database entries by replacing the storage location path information with target storage location path information for the first stub file and the second stub file;
to determine that the modifying of a database entry of the plurality of database entries for the second stub file failed;
to delete the generated second stub file from the target storage location responsive to the determination, wherein the second stub file is maintained in the source storage location; and
to repeat the migrating and the modifying steps in connection with the second stub file following the deletion.
2. The apparatus of claim 1 wherein, in migrating the first stub file to the target storage location, said at least one processing platform is further configured to delete the first stub file from the source storage location.
3. The apparatus of claim 1 wherein, in selecting the first stub file and the second stub file for migration, said at least one processing platform is configured to evaluate the plurality of database entries comprising the source storage location path information to determine that the plurality of database entries comprising the source storage location path information satisfy the one or more policy constraints.
4. The apparatus of claim 3 wherein said at least one processing platform is further configured to generate a policy comprising the one or more policy constraints.
5. The apparatus of claim 3 wherein the one or more policy constraints comprise at least one of a file access time, a file modification time, a file size, a file name and a directory name.
6. The apparatus of claim 3 wherein said at least one processing platform is further configured to generate an interface for the user to define the one or more policy constraints.
7. The apparatus of claim 3 wherein said at least one processing platform is further configured to reject an additional stub file of the plurality of stub files for migration, wherein the additional stub file corresponds to an additional database entry comprising source storage location path information for the additional stub file.
8. The apparatus of claim 7 , wherein, in rejecting the additional stub file, said at least one processing platform is configured to evaluate the additional database entry to determine that the additional database entry fails to satisfy the one or more policy constraints.
9. The apparatus of claim 1 wherein said at least one processing platform is configured generate an interface for a user to select a protocol to use for reading the plurality of stub files from the source storage location and for writing the plurality of stub files to the target storage location.
10. The apparatus of claim 1 wherein the plurality of database entries further comprise data about one or more attributes of the first stub file and the second stub file, and wherein the one or more attributes comprise at least one of a file modification time, a file size, an archive time and a storage protocol.
11. The apparatus of claim 10 wherein said at least one processing platform comprises a cloud tiering appliance.
12. The apparatus of claim 1 wherein the plurality of archived files are archived to a cloud storage platform.
13. A method comprising:
selecting, by at least one processing platform comprising a processor coupled to a memory, at least a first stub file and a second stub file of a plurality of stub files for migration from a source storage location to a target storage location, wherein the plurality of stub files correspond to a plurality of archived files, wherein the plurality of stub files and one or more non-stub files are stored in the source storage location, wherein the selection of the first stub file and the second stub file is based at least in part on a plurality of database entries comprising source storage location path information for the first stub file and the second stub file, and wherein the plurality of database entries satisfy one or more policy constraints defined by a user;
migrating, by the at least one processing platform, the first stub file and the second stub file to the target storage location without migrating the one or more non-stub files to the target storage location, wherein the migrating comprises generating the first stub file and the second stub file in the target storage location;
modifying, by the at least one processing platform, the plurality of database entries by replacing the storage location path information with target storage location path information for the first stub file and the second stub file;
determining, by the at least one processing platform, that the modifying of a database entry of the plurality of database entries for the second stub file failed;
deleting, by the at least one processing platform, the generated second stub file from the target storage location responsive to the determination, wherein the second stub file is maintained in the source storage location; and
repeating, by the at least one processing platform, the migrating and the modifying steps in connection with the second stub file following the deletion.
14. The method of claim 13 wherein migrating the first stub file to the target storage location further comprises deleting the first stub file from the source storage location.
15. The method of claim 13 wherein selecting the first stub file and the second stub file for migration comprises evaluating the plurality of database entries comprising the source storage location path information to determine that the plurality of database entries comprising the source storage location path information satisfy the one or more policy constraints.
16. The method of claim 15 further comprising rejecting an additional stub file of the plurality of stub files for migration, wherein the additional stub file corresponds to an additional database entry comprising source storage location path information for the additional stub file.
17. A computer program product comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing platform, which comprises a processor coupled to a memory, causes said at least one processing platform:
to select at least a first stub file and a second stub file of a plurality of stub files for migration from a source storage location to a target storage location, wherein the plurality of stub files correspond to a plurality of archived files, wherein the plurality of stub files and one or more non-stub files are stored in the source storage location, wherein the selection of the first stub file and the second stub file is based at least in part on a plurality of database entries comprising source storage location path information for the first stub file and the second stub file, and wherein the plurality of database entries satisfy one or more policy constraints defined by a user;
to migrate the first stub file and the second stub file to the target storage location without migrating the one or more non-stub files to the target storage location, wherein the migrating comprises generating the first stub file and the second stub file in the target storage location;
to modify the plurality of database entries by replacing the storage location path information with target storage location path information for the first stub file and the second stub file;
to determine that the modifying of a database entry of the plurality of database entries for the second stub file failed;
to delete the generated second stub file from the target storage location responsive to the determination, wherein the second stub file is maintained in the source storage location; and
to repeat the migrating and the modifying steps in connection with the second stub file following the deletion.
18. The computer program product according to claim 17 wherein, in migrating the first stub file to the target storage location, the program code further causes said at least one processing platform to delete the first stub file from the source storage location.
19. The computer program product according to claim 17 wherein, in selecting the first stub file and the second stub file for migration, the program code further causes said at least one processing platform to evaluate the plurality of database entries comprising the source storage location path information to determine that the plurality of database entries comprising the source storage location path information satisfy the one or more policy constraints.
20. The computer program product according to claim 19 wherein the program code further causes said at least one processing platform to reject an additional stub file of the plurality of stub files for migration, wherein the additional stub file corresponds to an additional database entry comprising source storage location path information for the additional stub file.