# US 2019/0171365 A1 · Hybrid data tiering > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0171365 A1 - Document ID: US20190171365A1 - Status: Published application - Kind: A1 - Application number: 16/195,845 - Filed: 2018-11-19 - Published: 2019-06-06 - Earliest claimed: 2017-11-28 - Assignees: Pure Storage, Inc. - Applicants: Pure Storage, Inc. - Inventors: TYLER POWER; MARK COX; MARK EMBERSON - Web page: https://patentgrep.com/patent/US20190171365A1 ## CPC - G06F 3/065: {Replication mechanisms} - G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]} - G06F 3/0604: {Improving or facilitating administration, e.g. storage management} - G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors} - G06F 3/0649: {Lifecycle management} - G06F 3/0683: {Plurality of storage devices} - G06F 3/0685: {Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Hybrid data tiering, including: replicating multiple data objects from a first storage location on a first computer system to a second storage location at a second computer system; identifying, in accordance with a retention policy, some of the multiple data objects to continue storing at the first storage location, wherein all of the multiple data objects remain stored at the second storage location; and selecting the identified some of the multiple data objects to remain stored at the first storage location. ## Claims ### Claim 1 A method for hybrid data tiering, the method comprising: replicating multiple data objects from a first storage location on a first computer system to a second storage location at a second computer system; identifying, in accordance with a retention policy, some of the multiple data objects to continue storing at the first storage location, wherein all of the multiple data objects remain stored at the second storage location; and selecting the identified some of the multiple data objects to remain stored at the first storage location. ### Claim 2 (depends on 1) The method of claim 1, wherein the first storage location is part of a storage system at a first geographic location, and wherein the second storage location is implemented within a remote, cloud services provider. ### Claim 3 (depends on 2) The method of claim 2, wherein the cloud services provider implements the second storage location as data object store or block storage. ### Claim 4 (depends on 1) The method of claim 1, wherein the first storage location is part of a local storage system at a first geographic location, and wherein the second storage location is implemented within a remote storage system. ### Claim 5 (depends on 1) The method of claim 1, wherein the retention policy specifies that a greater number of references to a given object correspond to a higher priority for the given object remaining stored at the first storage location. ### Claim 6 (depends on 1) The method of claim 1, wherein the retention policy is based upon a pattern of storage access from one or more processes operating on storage at the first storage location. ### Claim 7 (depends on 1) The method of claim 1, wherein the retention policy specifies different retention behavior for different users, or wherein the retention policy specifies different retention behavior for different priority processes operating at the first storage location. ### Claim 8 (depends on 1) The method of claim 1, wherein the selected data objects to remain stored at the first storage location correspond to a data backup, and wherein the retention policy specifies a length of time for the selected data objects to remain stored at the first storage location based on an expected window of time within which data backup is expected to be referenced, and wherein the data objects among the multiple data objects not selected to remain stored at the first storage location are deleted. ### Claim 9 (depends on 1) The method of claim 1, wherein one or more given data objects not selected to remain stored at the first storage location are not removed until after the one or more given data objects are successfully stored at the second storage location. ### Claim 10 An apparatus for hybrid data tiering comprising: one or more hardware processors; one or more data storage resources; and a hybrid data tiering controller module configured to: replicate multiple data objects from a first storage location on a first computer system to a second storage location at a second computer system; identify, in accordance with a retention policy, some of the multiple data objects to continue storing at the first storage location, wherein all of the multiple data objects remain stored at the second storage location; and select selecting the identified some of the multiple data objects to remain stored at the first storage location. ### Claim 11 (depends on 10) The apparatus of claim 10, wherein the first storage location is part of a storage system at a first geographic location, and wherein the second storage location is implemented within a remote, cloud services provider. ### Claim 12 (depends on 10) The apparatus of claim 10, wherein the cloud services provider implements the second storage location as data object store or block storage. ### Claim 13 (depends on 10) The apparatus of claim 10, wherein the first storage location is part of a local storage system at a first geographic location, and wherein the second storage location is implemented within a remote storage system. ### Claim 14 (depends on 10) The apparatus of claim 10, wherein the retention policy specifies that a greater number of references to a given object correspond to a higher priority for the given object remaining stored at the first storage location. ### Claim 15 (depends on 10) The apparatus of claim 10, wherein the retention policy is based upon a pattern of storage access from one or more processes operating on storage at the first storage location. ### Claim 16 (depends on 10) The apparatus of claim 10, wherein the retention policy specifies different retention behavior for different users, or wherein the retention policy specifies different retention behavior for different priority processes operating at the first storage location. ### Claim 17 (depends on 10) The apparatus of claim 10, wherein the selected data objects to remain stored at the first storage location correspond to a data backup, and wherein the retention policy specifies a length of time for the selected data objects to remain stored at the first storage location based on an expected window of time within which data backup is expected to be referenced, and wherein the data objects among the multiple data objects not selected to remain stored at the first storage location are deleted. ### Claim 18 (depends on 10) The apparatus of claim 10, wherein one or more given data objects not selected to remain stored at the first storage location are not removed until after the one or more given data objects are successfully stored at the second storage location. ### Claim 19 A computer program product for hybrid data tiering, the computer program product disposed upon a computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of: replicating multiple data objects from a first storage location on a first computer system to a second storage location at a second computer system; identifying, in accordance with a retention policy, some of the multiple data objects to continue storing at the first storage location, wherein all of the multiple data objects remain stored at the second storage location; and selecting the identified some of the multiple data objects to remain stored at the first storage location. ### Claim 20 (depends on 19) The computer program product of claim 19, wherein the first storage location is part of a storage system at a first geographic location, and wherein the second storage location is implemented within a remote, cloud services provider.