Virtual data backup
US-2015227602-A1 · Aug 13, 2015 · US
US9830091B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9830091-B2 |
| Application number | US-201514627034-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 20, 2015 |
| Priority date | Feb 20, 2015 |
| Publication date | Nov 28, 2017 |
| Grant date | Nov 28, 2017 |
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 storage platform computing apparatus obtains a lifecycle management policy and configuration information for a cloud repository identified in the lifecycle management policy. The configuration information includes at least one access parameter for the cloud repository. The lifecycle management policy is applied to determine when an object is required to be replicated to the cloud repository in response to a received write request. A request to store the object in the cloud repository is generated, when the object is determined to be required to be stored in the cloud repository, wherein the request includes the access parameter. The request is sent to the cloud repository using a representational state transfer (REST) interface associated with the cloud repository.
Opening claim text (preview).
What is claimed is: 1. A method for policy-based data tiering using a cloud architecture, the method comprising: identifying a lifecycle management policy from a plurality of lifecycle management policies based on at least one of a parameter of a write request and a characteristic of data requested to be written by the write request; determining that the identified lifecycle management policy indicates multiple storage tiers which at least comprise a first storage tier and a second storage tier; retrieving configuration information including at least one access parameter for a cloud repository that corresponds to the second storage tier, wherein the access parameter comprises at least one of a login and an access key for the cloud repository; storing the data as a set of one or more objects to a first storage location corresponding to the first storage tier; and replicating the set of one or more objects to a second storage location corresponding to the cloud repository using the access parameter; and updating metadata for the set of one or more objects to indicate the first and second storage locations and to indicate a unique tag for retrieving the configuration information regardless of changes to the configuration information. 2. The method as set forth in claim 1 , further comprising: based on a request to retrieve the data, retrieving the metadata for the set of one or more objects and at least the access parameter using the unique tag included in the metadata; and obtaining the set of one or more objects from the cloud repository using the access parameter. 3. The method as set forth in claim 1 , further comprising, accessing a listing of geographic locations of archive nodes and cloud repositories, which include the cloud repository, to determine which of the archive nodes is geographically closer to the cloud repository, wherein storing the data as the set of objects to the first storage location comprises communicating for storage the set of one or more objects to the archive node determined to be closer to the cloud repository. 4. The method as set forth in claim 1 , wherein the identified lifecycle management policy also indicates a third storage tier, the method further comprising, retrieving second configuration information for a second cloud repository corresponding to the third storage tier; replicating the set of one or more objects to a third storage location corresponding to the second cloud repository using a second access parameter indicated in the second configuration information, wherein the second access parameter comprises at least one of a login and an access key for the second cloud repository; and updating the metadata to also indicate the third storage location and a second unique tag for retrieving the second configuration information regardless of changes to the second configuration information. 5. The method of claim 4 , wherein replicating the set of one or more objects to the third storage location occurs after expiration of a first time period based on the lifecycle management policy indicating that data having a first characteristic reside in the second storage tier for the first time period before being moved to the third storage tier, wherein the data has the first characteristic. 6. The method of claim 1 wherein storing the data as the set of one or more objects to the first storage location comprises storing the data as the set of objects in a local storage device or communicating the set of one or more objects to an archive node for storing in archival storage. 7. A non-transitory computer readable medium having stored thereon instructions for policy-based data tiering using a cloud architecture comprising executable code to: identify a lifecycle management policy from a plurality of lifecycle management policies based on at least one of a parameter of a write request and a characteristic of data requested to be written by the write request; determine storage tiering indicated in the identified lifecycle management policy; retrieve configuration information including at least one access parameter for a cloud repository based, at least in part, on the storage tiering indicated in the identified lifecycle management policy, wherein the access parameter comprises at least one of a login and an access key for the cloud repository; store the data as a set of one or more objects to a first storage location corresponding to a first storage tier of the storage tiering; and replicate the set of one or more objects to a second storage location corresponding to the cloud repository which corresponds to a second storage tier of the storage tiering, wherein the code to replicate comprises code to use the access parameter; and update metadata for the set of one or more objects to indicate the first and second storage locations and to indicate a unique tag for retrieving the configuration information regardless of changes to the configuration information. 8. The non-transitory computer readable medium as set forth in claim 7 , further having stored therein code to: based on a request to retrieve the data, retrieve the metadata for the set of one or more objects and at least the access parameter using the unique tag included in the metadata; and obtain the set of one or more objects from the cloud repository using the access parameter. 9. The non-transitory computer readable medium as set forth in claim 7 , further having stored therein executable code to access a listing of geographic locations of archive nodes and cloud repositories, which include the cloud repository, to determine which of the archive nodes is located geographically closer to the cloud repository than one or more other of the archive nodes, wherein the code to store the data as the set of objects to the first storage location comprises the code to communicate the set of one or more objects to the archive node determined to be closer to the cloud repository. 10. The non-transitory computer readable medium as set forth in claim 7 , wherein the identified lifecycle management policy also indicates a third storage tier for the storage tiering, non-transitory computer readable medium further comprising code to, retrieve second configuration information for a second cloud repository corresponding to the third storage tier; replicate the set of one or more objects to a third storage location corresponding to the second cloud repository using a second access parameter indicated in the second configuration information, wherein the second access parameter comprises at least one of a login and an access key for the second cloud repository; and update the metadata to also indicate the third storage location and a second unique tag for retrieving the second configuration information regardless of changes to the second configuration information. 11. The non-transitory computer readable medium of claim 10 , wherein replication of the set of one or more objects to the third storage location is dependent upon expiration of a first time period based on the lifecycle management policy indicating that data having a first characteristic reside in the second storage tier for the first time period before being moved to the third storage tier, wherein the data has the first characteristic. 12. The non-transitory computer readable medium of claim 7 wherein the code to store the data as the set of one or more objects to the first storage location comprises code to store the data as the set of objects in a local storage device or to communicate the set of one or more objects to an archive node for storing in archival storage. 13. A storage platform computing appara
Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS] · CPC title
Replication mechanisms · CPC title
in relation to data integrity, e.g. data losses, bit errors · CPC title
Lifecycle management · CPC title
Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.