Documentation

InfluxDB Cloud Dedicated

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 automatically delete expired data and optimize storage without the need for 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. Expired Parquet files are retained for approximately 30 days for disaster recovery purposes. After this period, the files are permanently deleted and cannot be recovered. For more information see data durability.

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

What is your InfluxDB Cloud Dedicated cluster URL?

Enter your InfluxDB Cloud Dedicated cluster URL and we’ll update code examples for you.

Enter cluster URL

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2