Tiered storage is Timescale's hierarchical storage management architecture. Engineered for infinite low-cost scalability, tiered storage is available for the Time series and analytics instances you create in Timescale.
Tiered storage consists of the:
High-performance tier: rapid access to the most recent, and frequently accessed data.
Object storage tier: store data that is rarely accessed and has lower performance requirements. For example, to save old data for auditing or reporting purposes over long periods of time, even forever. The Object store is low-cost bottomless data storage built on Amazon S3. You use it to avoid the higher costs and data size limitations associated with the high-performance tier.
No matter the tier your data is stored in, query it when you need it. Timescale seamlessly accesses the correct storage tier and generates the response.
You use the API to define tiering policies that automatically migrate data from the high-performance storage tier to the object store as it ages. You use retention policies to remove very old data from the object store.
With tiered storage you don't need an ETL process, infrastructure changes, or custom-built, bespoke solutions to offload data to secondary storage and fetch it back in when needed. Kick back and relax, we do the work for you.
Info
Tiered storage is only available for the Time series and analytics instances you create in Timescale. Tiered storage DOES NOT work on Self-hosted TimescaleDB or Managed Service for TimescaleDB.
In this section you can:
- Learn about the object storage tier before you start using tiered storage.
- Take a tour of tiered storage features.
- Learn how to enable the object storage tier on your service.
- Manually tier chunks to schedule individual chunks to be tiered.
- Create a Tiering Policy to automatically schedule chunks to be tiered.
- Learn how to query tiered data.
- Manually untier chunks to move data back to the high-performance local storage tier.
Keywords
Found an issue on this page?Report an issue or Edit this page in GitHub.