# US 12,001,872 B2 · Object tiering from local store to cloud store > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,001,872 B2 - Document ID: US12001872B2 - Status: Granted - Kind: B2 - Application number: 17/357,300 - Filed: 2021-06-24 - Published: 2022-04-14 - Granted: 2024-06-04 - Earliest claimed: 2020-10-14 - Assignees: Nutanix, Inc. - Applicants: Nutanix, Inc. - Inventors: Ajaykrishna Raghavan; Biswa Ranjan Panda; Bharath Kumar; Karan Gupta - Web page: https://patentgrep.com/patent/US12001872B2 ## CPC - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)} - G06F 3/0604: {Improving or facilitating administration, e.g. storage management} - G06F 3/0649: {Lifecycle management} - G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]} - G06F 3/0685: {Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays} - G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An object tiering system transfers or tiers data objects from a data store to a cloud store. The system includes a processor and a memory having stored instructions that, when executed by the processor, cause the processor to ingest a first plurality of data objects in the data store, map a second plurality of data objects having a common tiering date to a region, and upon reaching the common tiering date, transfer the region to the cloud store. In some embodiments, the mapping is done a priori when each data object is ingested or at a first time before the common tiering date. In some embodiments, the common tiering date is a second time for transferring the second plurality of data objects from the data store to the cloud store. In some embodiments, the first plurality of objects includes the second plurality of objects. ## Claims ### Claim 1 An object tiering system for tiering objects including tiering from a data store to a cloud store, the system comprising: a processor and a memory having stored instructions that, when executed by the processor, cause the processor to: ingest a first plurality of data objects in the data store; map a second plurality of data objects having a common tiering date to a region, wherein the mapping is done a priori when each data object is ingested or at a first time before the common tiering date, wherein the common tiering date is a second time for transferring the second plurality of data objects from the data store to the cloud store, wherein the first plurality of objects includes the second plurality of objects; and upon reaching the common tiering date, transfer the region to the cloud store. ### Claim 2 (depends on 1) The system of claim 1, wherein the data store is a local store. ### Claim 3 (depends on 1) The system of claim 1, wherein the instructions, when executed by the processor, further cause the processor to: map metadata associated with the second plurality of data objects to a metadata region based on a common metadata tiering date; and transfer the metadata region to the cloud store upon reaching the common metadata tiering date. ### Claim 4 (depends on 1) The system of claim 1, wherein the common tiering date is based on object access time. ### Claim 5 (depends on 1) The system of claim 1, wherein the common tiering date is part of a lifecycle policy. ### Claim 6 (depends on 5) The system of claim 5, wherein the instructions, when executed by the processor, further cause the processor to map the second plurality of data objects having the lifecycle policy to the region. ### Claim 7 (depends on 1) The system of claim 1, wherein the region having the mapped data object is stored in a plurality of sequential locations in the data store, and wherein transferring the region to the cloud store comprises reading the region from the plurality of sequential locations. ### Claim 8 A method comprising: ingesting a first plurality of data objects in a data store; mapping a second plurality of data objects having a common tiering date to a region, wherein the mapping is done a priori when each data object is ingested or at a first time before the common tiering date, wherein the common tiering date is a second time for transferring the second plurality of data objects from the data store to a cloud store, wherein the first plurality of objects includes the second plurality of objects; and upon reaching the common tiering date, transferring the region to the cloud store. ### Claim 9 (depends on 8) The method of claim 8, further comprising: map metadata associated with the second plurality of data objects to a metadata region based on a common metadata tiering date; and transfer the metadata region to the cloud store upon reaching the common metadata tiering date. ### Claim 10 (depends on 8) The method of claim 8, wherein the common tiering date is based on object access time. ### Claim 11 (depends on 8) The method of claim 8, wherein the common tiering date is part of a lifecycle policy. ### Claim 12 (depends on 11) The method of claim 11, further comprising mapping the second plurality of data objects having the lifecycle policy to the region. ### Claim 13 (depends on 8) The method of claim 8, wherein the region having the mapped data object is stored in a plurality of sequential locations in the data store, and wherein transferring the region to the cloud store comprises reading the region from the plurality of sequential locations. ### Claim 14 A non-transitory computer-readable medium comprising computer-executable instructions embodied thereon that, when executed by a processor, cause the processor to perform a process comprising: ingesting a first plurality of data objects in a data store; mapping a second plurality of data objects having a common tiering date to a region, wherein the mapping is done a priori when each data object is ingested or at a first time before the common tiering date, wherein the common tiering date is a second time for transferring the second plurality of data objects from the data store to a cloud store, wherein the first plurality of objects includes the second plurality of object; and upon reaching the common tiering date, transferring the region to the cloud store. ### Claim 15 (depends on 14) The medium of claim 14, wherein the data store is a local store. ### Claim 16 (depends on 14) The medium of claim 14, wherein the instructions, when executed by the processor, cause the processor to perform the process further comprising: mapping metadata associated with the second plurality of data objects to a metadata region based on a common metadata tiering date; and transferring the metadata region to the cloud store upon reaching the common metadata tiering date. ### Claim 17 (depends on 14) The medium of claim 14, wherein the common tiering date is based on object access time. ### Claim 18 (depends on 14) The medium of claim 14, wherein the common tiering date is part of a lifecycle policy. ### Claim 19 (depends on 18) The medium of claim 18, wherein the instructions, when executed by the processor, cause the processor to perform the process further comprising mapping the second plurality of data objects having the lifecycle policy to the region. ### Claim 20 (depends on 14) The medium of claim 14, wherein the region having the mapped data object is stored in a plurality of sequential locations in the data store, and wherein transferring the region to the cloud store comprises reading the region from the plurality of sequential locations.