Documentation

influxd-ctl restore

The influxd-ctl restore command restores data backed up from an InfluxDB Enterprise cluster.

influxd-ctl restore supports full, incremental, and metadata-only backups. To restore from a full backup, include the -full flag and provide the path to the backup manifest (/path/to/backups/backup.manifest). To restore from an incremental or metadata backup, provide the path to the directory that contains the backup files (/path/to/backups).

Destination database must be empty

The database data is restored to must be empty. influxd-ctl restore will fail if the destination database contains data.

Usage

influxd-ctl restore [flags] <backup-location>

Arguments

  • backup-location: Location of backup-related files. They type of backup you’re restoring from determines the type and location of backup files:

    • Restore from a full backup: Provide the path to the backup manifest file
    • Restore from an incremental backup: Provide the directory path of the backup
    • Restore from a metadata-only backup: Provide the directory path of the backup

Flags

FlagDescription
-dbDatabase to restore (if the backup contains more than one)
-fullRestore data from a full backup
-listList the contents of the backup
-meta-only-overwrite-forceRestore only metadata from a backup Danger: see below
-newdbChange database name when restoring (requires -db flag)
-newdurationChange retention policy duration (shard expiry) when restoring (requires -rp flag, use 0s for infinite)
-newrfNew replication factor to use during restore (limited by cluster size)
-newrpChange retention policy name when restoring (requires -rp flag)
-newshardShard ID to restore into (if different from the shard ID in the backup)
-rpRetention policy to restore (if the backup contains more than one)
-shardShard ID to restore

Only use the -meta-only-overwrite-force flag to restore from backups of the destination cluster. Metadata includes shard assignments to data nodes, so if you use this flag with metadata from a different cluster, you will lose data.

See Back up and restore for instructions on using this flag.

Examples

Restore from a full backup

influxd-ctl restore -full /path/to/full-backup/20230101T00000Z.manifest

View example output

Restore from an incremental backup

In this example, the restore command restores an incremental backup stored in the my-incremental-backup/ directory.

influxd-ctl restore /path/to/incremental-backup/

View example output

Restore from a metadata backup

In this example, the restore command restores an metadata backup stored in the metadata-backup/ directory.

influxd-ctl restore /path/to/metadata-backup/

View example output


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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