Documentation

Undelete a table

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

To undelete a table:

  • A new table with the same name cannot already exist.
  • You must have appropriate permissions to manage databases.

When you undelete a table, it is restored with the same partition template and other settings as when it was deleted.

Tables 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 table are permanently removed and the table cannot be undeleted.

Undelete a table using the influxctl CLI

influxctl table undelete 
DATABASE_NAME
TABLE_ID

Replace the following:

  • DATABASE_NAME: Name of the database associated with the deleted table
  • TABLE_ID: ID of the deleted table to restore

View deleted table IDs

To view the IDs of deleted tables, use the influxctl table list command with the --filter-status=deleted flag–for example:

influxctl table list --filter-status=deleted 
DATABASE_NAME

Replace DATABASE_NAME with the name of the database associated with the table you want to undelete.


Was this page helpful?

Thank you for your feedback!


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