Data retention in InfluxDB Cloud Dedicated

InfluxDB Cloud Dedicated enforces database retention periods at query time. Any points with timestamps beyond a database’s retention period are filtered out of query results, even though the data may still exist.

Database retention period

A database retention period is the duration of time that a database retains data. Retention periods are designed to automatically delete expired data and optimize storage without any user intervention.

Retention periods can be as short as an hour or infinite. Points in a database with timestamps beyond the defined retention period (relative to now) are not queryable, but may still exist in storage until fully deleted.

View database retention periods

Use the influxctl database list command to view your databases’ retention periods.

When does data actually get deleted?

InfluxDB routinely deletes Parquet files containing only expired data. InfluxDB retains expired Parquet files for approximately 100 days for disaster recovery. After the disaster recovery period, expired Parquet files are permanently deleted and can’t be recovered.

Was this page helpful?

Thank you for your feedback!

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: