Migrating data from legacy storage systems to object storage systems
First Claim
1. A method for migrating a dataset from a file storage system to an object storage system by converting a file to an object, comprising:
- identifying file data associated with a file of a file system of a file storage system;
converting the file into an object using the file data;
responsive to determining that a prior object version of the object does not exist within at least one data constituent volume of an object storage system;
storing the object within a first data constituent volume of the object storage system, the storing comprising;
identifying a service level objective for the file; and
selecting the first data constituent volume for storage of the object based upon the first data constituent volume comprising one or more characteristics that correspond to the service level objective; and
creating an entry within a namespace volume associated with the object storage system, the entry comprising a redirector mapping a front-end data path for the object to a back-end data path, the back-end data path specifying a path to the object within the first data constituent volume; and
responsive to determining that the prior object version of the object does exist within a second data constituent volume of the object storage system;
receiving a data difference between the prior object version and the object;
creating a new object within the second data constituent volume based upon the prior object version and the data difference; and
creating a new redirector, within the namespace volume, for the new object.
1 Assignment
0 Petitions
Accused Products
Abstract
One or more techniques and/or systems are provided for migrating a dataset from a file storage system to an object storage system. That is, a snapshot of a file system may be received from the file storage system. The snapshot may comprise file data associated with a file of the file system. The file may be converted into an object using the file data. The object may be stored within a data constituent volume of the object storage system. A namespace volume, used to track objects, may be populated with a redirector that maps a front-end data path (e.g., a path used by clients to reference the object) to a back-end data path that specifies a path to the object within the data constituent volume. In this way, a dataset of one or more files may be migrated from the file storage system to the object storage system.
-
Citations
20 Claims
-
1. A method for migrating a dataset from a file storage system to an object storage system by converting a file to an object, comprising:
-
identifying file data associated with a file of a file system of a file storage system; converting the file into an object using the file data; responsive to determining that a prior object version of the object does not exist within at least one data constituent volume of an object storage system; storing the object within a first data constituent volume of the object storage system, the storing comprising; identifying a service level objective for the file; and selecting the first data constituent volume for storage of the object based upon the first data constituent volume comprising one or more characteristics that correspond to the service level objective; and creating an entry within a namespace volume associated with the object storage system, the entry comprising a redirector mapping a front-end data path for the object to a back-end data path, the back-end data path specifying a path to the object within the first data constituent volume; and responsive to determining that the prior object version of the object does exist within a second data constituent volume of the object storage system; receiving a data difference between the prior object version and the object; creating a new object within the second data constituent volume based upon the prior object version and the data difference; and creating a new redirector, within the namespace volume, for the new object. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A system for migrating a dataset from a file storage system to an object storage system by converting a file to an object, comprising:
a migration component configured to; identify file data associated with a file of a file system of a file storage system; convert the file into an object using the file data; responsive to determining that a prior object version of the object does not exist within at least one data constituent volume of an object storage system; store the object within a first data constituent volume of the object storage system; identify an inode to path (I2P) data structure from the file system, the I2P data structure comprising a mapping of an inode to the file; define a front-end data path based at least in part upon the mapping; and create an entry within a namespace volume associated with the object storage system, the entry comprising a redirector mapping the front-end data path for the object to a back-end data path, the back-end data path specifying a path to the object within the first data constituent volume; and responsive to determining that the prior object version of the object does exist within a second data constituent volume of the object storage system; receive a data difference between the prior object version and the object as the file data; create a new object within the second data constituent volume based upon the prior object version and the data difference, comprising; create a new redirector, within the namespace volume, for the new object. - View Dependent Claims (16, 17, 18, 19)
-
20. A non-transitory computer-readable storage medium comprising processor-executable instructions that when executed perform a method for migrating a dataset from a file storage system to an object storage system by converting a file to an object, comprising:
-
receiving a plurality of snapshots through one or more data streams; assigning a priority to respective data streams; queuing the one or more data streams for processing based upon priorities assigned to respective data streams; identifying file data, within a snapshot of the plurality of snapshots, associated with a file of a file system of a file storage system; converting the file into an object using the file data; responsive to determining that a prior object version of the object does not exist within at least one data constituent volume of an object storage system; storing the object within a first data constituent volume of the object storage system; creating an entry within a namespace volume associated with the object storage system, the entry comprising a redirector mapping a front-end data path for the object to a back-end data path, the back-end data path specifying a path to the object within the first data constituent volume; and responsive to determining that the prior object version of the object does exist within a second data constituent volume of the object storage system; receiving a data difference between the prior object version and the object; creating a new object within the second data constituent volume based upon the prior object version and the data difference; and creating a new redirector, within the namespace volume, for the new object.
-
Specification