Documentation

InfluxDB Clustered

Undelete a database

Use the influxctl database undelete command to restore a previously deleted database in your InfluxDBed cluster.

To undelete a database:

  • The database name must match the name of the deleted database.
  • A new database with the same name cannot already exist.
  • You must have appropriate permissions to manage databases.

When you undelete a database, it is restored with the same retention period, table limits, and column limits as when it was deleted.

Databases can only be undeleted for a configurable “hard-delete” grace period after they are deleted. After this grace period, all Parquet files associated with the deleted database are permanently removed and the database cannot be undeleted.

Undelete a database using the influxctl CLI

influxctl database undelete 
DATABASE_NAME

Replace the following:

  • DATABASE_NAME: Name of the deleted database to restore

Recreate tokens for the database

After successfully undeleting a database:

  1. Verify the database was restored by listing all databases.
  2. If you previously deleted tokens associated with the deleted database, create new database tokens
    • Any tokens that existed before deletion are not restored. Create new database tokens with appropriate permissions for the restored database.
  3. Update your applications to use the new database tokens.

Undeleted databases retain their original configuration

When a database is undeleted, it retains the same database ID, retention period, and table/column limits it had before deletion. However, database tokens are not restored and must be recreated.

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

What is your InfluxDB cluster URL?

Enter your InfluxDB 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