Documentation

influxd backup

This page documents an earlier version of InfluxDB. InfluxDB v2 is the latest stable version. See the equivalent InfluxDB v2 documentation: influx backup.

The influxd backup command crates a backup copy of specified InfluxDB OSS database(s) and saves the files in an Enterprise-compatible format to PATH (directory where backups are saved).

Usage

influxd backup [flags] PATH

Flags

Flag Description
-portable Generate backup files in a portable format that can be restored to InfluxDB OSS or InfluxDB Enterprise. Use unless the legacy backup is required.
-host InfluxDB OSS host to back up from. Optional. Defaults to 127.0.0.1:8088.
-db InfluxDB OSS database name to back up. Optional. If not specified, all databases are backed up when using -portable.
-rp Retention policy to use for the backup. Optional. If not specified, all retention policies are used by default.
-shard The identifier of the shard to back up. Optional. If specified, -rp is required.
-start Include all points starting with specified timestamp (RFC3339 format). Not compatible with -since.
-end Exclude all points after timestamp (RFC3339 format). Not compatible with -since.
-since Create an incremental backup of all points after the timestamp (RFC3339 format). Optional. Recommend using -start instead.
-skip-errors Continue backing up the remaining shards when the current shard fails to backup.

Was this page helpful?

Thank you for your feedback!


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: