Documentation

InfluxDB OSS

v2

influxd upgrade

Use the influxd upgrade command to upgrade an instance of InfluxDB 1.x to InfluxDB 2.7. This command copies all data in databases and retention policies (used in 1.x) over to buckets (used in 2.7).

Be sure to back up all data before upgrading with influx upgrade.

This command performs the following actions:

  1. Creates the InfluxDB 2.x configuration file using 1.x configuration file options. Unsupported 1.x options are reported to standard output. If the configuration file is not available, the 1.x database folder can be passed via th --v1-dir flag.
  2. Copies and upgrades 1.x database files.

The target 2.x database directory is specified by the --engine-path option. If changed, the bolt path can be specified by the --bolt-path option.

Usage

influxd upgrade [flags]
influxd upgrade [command]

Flags

Flag Description Input type
-m --bolt-path Path for boltdb database (default ~/.influxdbv2/influxd.bolt) string
-b --bucket Primary bucket name string
--config-file Custom InfluxDB 1.x config file path (default ~/.influxdb/influxdb.conf) string
--continuous-query-export-path Path for exported 1.x continuous queries (default ~/continuous_queries.txt) string
-e --engine-path Path for persistent engine files (default ~/.influxdbv2/engine) string
-f --force Skip the confirmation prompt
-h --help Help for influxd upgrade
-c --influx-configs-path Path for 2.x influx CLI configurations file (default ~/.influxdbv2/configs)
--log-level Supported log levels are debug, info, warn, and error (default info) string
--log-path Custom log file path (default ~/upgrade.log) string
-o --org Primary organization name string
--overwrite-existing-v2 Overwrite existing files at the output paths instead of aborting the upgrade process
-p --password Password for username string
-r --retention Duration bucket will retain data (default 0; retains data infinitely) string
-t --token Token for username. If not specified, a token is auto-generated. string
-u --username Primary username string
--v1-dir Path to source 1.x db directory containing meta, data, and wal sub-folders (default ~/.influxdb) string
--v2-config-path Destination path for upgraded 2.x configuration file (default ~/.influxdbv2/config.toml) string
-v --verbose Verbose output

Was this page helpful?

Thank you for your feedback!

© 2024 InfluxData, Inc.

What is your InfluxDB OSS URL?

Customize your InfluxDB OSS URL and we’ll update code examples for you.

Default
Custom

For more information, see InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: