Garbage collection of expired snapshots
US-2019213123-A1 · Jul 11, 2019 · US
US12561280B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12561280-B2 |
| Application number | US-202418588795-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 27, 2024 |
| Priority date | Dec 28, 2018 |
| Publication date | Feb 24, 2026 |
| Grant date | Feb 24, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A cloud-native global file system to provide primary file storage for enterprise data is augmented to provide “direct-to-cloud” (D2C) migration of a data set. In addition to providing a filer, the service provider configures a direct-to-cloud migration tool executed in association with the hardware of the enterprise filesystem whose data set is being migrated. The migration tool reads the existing filesystem, transforms the data into a format consistent with that done by a filer, and pushes the result directly to an object store in the cloud. In a first pass, typically a large bulk of the data is moved and, depending on how the migration tool is configured, one or more additional passes may then be carried out. When migration is complete (or substantially complete), the filer then is activated to complete the migration (if need be) and take over the go-forward operations.
Opening claim text (preview).
Having described our invention, what we claim is as follows: 1 . A method to migrate a data set to a cloud-based object store associated with a cloud-based storage service, comprising: pooling together a set of migration machines, wherein at least one migration machine in the set comprises hardware and software; based on a size of the data set, automatically determining a division of migration labor across the set of migration machines; and migrating the data set to the cloud-based object store using the set of migration machines; wherein migrating the data set further includes applying a configurable Quality of Service (QOS) to a portion of the data set as the portion is migrated to the cloud-based object store by a given one of the set of migration machines. 2 . The method as described in claim 1 further including taking a given action with respect to permission metadata associated with the data set during migration of at least a portion of the data set. 3 . The method as described in claim 2 wherein the given action is one of: adding an access control list (ACL), removing an ACL, and permutating an ACL. 4 . The method as described in claim 1 further including encrypting at least a portion of the data set prior to migrating the portion to the cloud-based object store. 5 . A method to migrate a data set to a cloud-based object store associated with a cloud-based storage service, comprising: pooling together a set of migration machines, wherein at least one migration machine in the set comprises hardware and software; based on a size of the data set, automatically determining a division of migration labor across the set of migration machines; and migrating the data set to the cloud-based object store using the set of migration machines; wherein migrating the data set further includes applying a transformation to a portion of the data set as the portion is migrated to the cloud-based object store by a given one of the set of migration machines. 6 . The method as described in claim 5 further including taking a given action with respect to permission metadata associated with the data set during migration of at least a portion of the data set. 7 . The method as described in claim 6 wherein the given action is one of: adding an access control list (ACL), removing an ACL, and permutating an ACL. 8 . The method as described in claim 6 further including encrypting at least a portion of the data set prior to migrating the portion to the cloud-based object store.
Specific adaptations of the file system to access devices and non-file objects via standard file system access operations, e.g. pseudo file systems (dedicated interfaces to storage systems G06F3/0601) · CPC title
Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files · CPC title
Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof (details of archiving G06F16/11) · CPC title
Distributed file systems · CPC title
Details of migration of file systems (migration mechanisms in storage systems G06F3/0647) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.