Documentation

influxd restore

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

The influxd restore command restores backup data and metadata from an InfluxDB backup directory.

Shut down the influxd server before restoring data.

Usage

influxd restore [flags]

Flags

FlagDescriptionMaps To
-portableActivate portable restore mode, which consumes files in an improved Enterprise-compatible format that includes a manifest. If not specified, the legacy restore mode is used.INFLUXDB_CONFIG_PATH
-hostInfluxDB OSS host to connect to where the data will be restored
-dbName of database to be restored from the backup (InfluxDB OSS or InfluxDB Enterprise).
-newdbName of the InfluxDB OSS database to import archived data into. Optional. If not specified, then the value of -db <db_name> is used. The new database name must be unique to the target system.
-rpName of retention policy to restore. Optional. Requires that db is specified.
-newrpName of retention policy to restore to. Optional. Requires that -rp is specified.
-shardShard ID to restore. Optional. Requires that -db and -rp are specified.

Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, 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