Tiered storage is a hierarchical storage management architecture for Time series and analytics services you create in Timescale Cloud.
Engineered for infinite low-cost scalability, 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 Cloud.
Tiered storage DOES NOT work on Self-hosted TimescaleDB or Managed Service for TimescaleDB.
This section explains the following:
- Learn about the object storage tier: understand tiered storage.
- Manage tiering: enable and disable data tiering, automate tiering with policies, or tier and untier manually.
- Query tiered data: query and performance for tiered data.
- Replicas and forks with tiered data: how tiered storage works with forks and replicas.
Keywords
Found an issue on this page?Report an issue or Edit this page in GitHub.