Documentation

Back up data

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

Use the influx backup command to back up data and metadata stored in InfluxDB. InfluxDB copies all data and metadata to a set of files stored in a specified directory on your local filesystem.

InfluxDB 1.x/2.x compatibility

The InfluxDB 2.7 influx backup command is not compatible with versions of InfluxDB prior to 2.0.0. For information about migrating data between InfluxDB 1.x and 2.7, see:

The influx backup command cannot back up data stored in InfluxDB Cloud.

The influx backup command requires:

  • The directory path for where to store the backup file set
  • The root authorization token (the token created for the first user in the InfluxDB setup process).
Back up data with the influx CLI
# Syntax influx backup <backup-path> -t <root-token>  # Example influx backup \  path/to/backup_$(date '+%Y-%m-%d_%H-%M') \  -t xXXXX0xXX0xxX0xx_x0XxXxXXXxxXX0XXX0XXxXxX0XxxxXX0Xx0xx==

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