Documentation

influx restore

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

The restore process

When restoring data from a backup file set, InfluxDB temporarily moves existing data and metadata while restore runs. After restore completes, the temporary data is deleted. If the restore process fails, InfluxDB preserves the data in the temporary location.

For information about recovering from a failed restore process, see Restore data.

Cannot restore to existing buckets

The influx restore command cannot restore data to existing buckets. Use the --new-bucket flag to create a bucket with a new name and restore data into it. To restore data and retain bucket names, delete existing buckets and then begin the restore process.

Usage

influx restore [flags]
  • Copy
  • Fill window

Flags

FlagDescriptionInput typeMaps to ?
-c--active-configCLI configuration to use for commandstring
-b--bucketName of the bucket to restore (mutually exclusive with --bucket-id)string
--bucket-idID of the bucket to restore (mutually exclusive with --bucket)string
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
--fullFully restore and replace all data on server
-h--helpHelp for the restore command
--hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
--hostHTTP address of InfluxDB (default http://localhost:8086)stringINFLUX_HOST
--http-debugInspect communication with InfluxDB servers.string
--jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
--new-bucketName of the bucket to restore tostring
--new-orgName of the organization to restore tostring
-o--orgOrganization name (mutually exclusive with --org-id)string
--org-idOrganization ID (mutually exclusive with --org)string
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
-t--tokenAPI tokenstringINFLUX_TOKEN

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Restore backup data
influx restore /path/to/backup/dir/
  • Copy
  • Fill window
Restore backup data for a specific bucket into a new bucket
influx restore \
  --bucket example-bucket \
  --new-bucket new-example-bucket \
  /path/to/backup/dir/
  • Copy
  • Fill window
Restore and replace all data

influx restore --full restores all time series data and InfluxDB key-value data such as tokens, dashboards, users, etc.

influx restore --full /path/to/backup/dir/
  • Copy
  • Fill window

Was this page helpful?

Thank you for your feedback!


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.

Read more

InfluxDB 3 Core and Enterprise are now in Beta

InfluxDB 3 Core and Enterprise are now available for beta testing, available under MIT or Apache 2 license.

InfluxDB 3 Core is a high-speed, recent-data engine that collects and processes data in real-time, while persisting it to local disk or object storage. InfluxDB 3 Enterprise is a commercial product that builds on Core’s foundation, adding high availability, read replicas, enhanced security, and data compaction for faster queries. A free tier of InfluxDB 3 Enterprise will also be available for at-home, non-commercial use for hobbyists to get the full historical time series database set of capabilities.

For more information, check out: