Documentation

Restore a Chronograf database

Chronograf uses Bolt to store Chronograf-specific key-value data. Generally speaking, you should never have to manually administer your internal Chronograf database. However, rolling back to a previous version of Chronograf does require restoring the data and data-structure specific to that version.

Chronograf’s internal database, chronograf-v1.db, is stored at your specified --bolt-path which, by default, is the current working directory where the chronograf binary is executed. In the upgrade process, an unmodified backup of your Chronograf data is stored inside the backup directory before any necessary migrations are run. This is done as a convenience in case issues arise with the data migrations or the upgrade process in general.

The backup directory contains a copy of your previous chronograf-v1.db file. Each backup file is appended with the corresponding Chronograf version. For example, if you moved from Chronograf 1.4.4.2 to 1.11.3, there will be a file called backup/chronograf-v1.db.1.4.4.2.

Chronograf backup directory structure

  • chronograf-working-dir/
    • chronograf-v1.db
    • backup/
      • chronograf-v1.db.1.4.4.0
      • chronograf-v1.db.1.4.4.1
      • chronograf-v1.db.1.4.4.2

Roll back to a previous version

If there is an issue during the upgrade process or you simply want/need to roll back to an earlier version of Chronograf, you must restore the data file associated with that specific version, then downgrade and restart Chronograf.

The process is as follows:

1. Locate your desired backup file

Inside your backup directory, locate the database file with a the appended Chronograf version that corresponds to the version to which you are rolling back. For example, if rolling back to 1.4.4.2, find backup/chronograf-v1.db.1.4.4.2.

2. Stop your Chronograf server

Stop the Chronograf server by killing the chronograf process.

3. Replace your current database with the backup

Remove the current database file and replace it with the desired backup file:

# Remove the current database
rm chronograf-v1.db

# Replace it with the desired backup file
cp backup/chronograf-v1.db.1.4.4.2 chronograf-v1.db

4. Install the desired Chronograf version

Install the desired Chronograf version. Chronograf releases can be viewed and downloaded either from the InfluxData downloads page or from the Chronograf releases page on Github.

5. Start the Chronograf server

Restart the Chronograf server. Chronograf will use the chronograf-v1.db in the current working directory.

Rerun update migrations

This process can also be used to rerun Chronograf update migrations. Go through steps 1-5, but on step 3 select the backup you want to use as a base for the migrations. When Chronograf starts again, it will automatically run the data migrations required for the installed version.


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.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 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 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:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

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