Documentation

influx replication create

Replication remotes and replication streams can only be configured for InfluxDB OSS.

The influx replication create command creates a new InfluxDB replication stream.

Usage

influx replication create [command options] [arguments...]

Flags

FlagDescriptionInput typeMaps to ?
-n--nameReplication stream namestring
-d--descriptionReplication stream descriptionstring
--org-idLocal organization IDstringINFLUX_ORG_ID
-o--orgLocal organization namestringINFLUX_ORG
--remote-idRemote connection ID to replicate data tostring
--local-bucket-idLocal bucket ID to replicate data fromstring
--remote-bucketRemote bucket name to replicate data to (mutually exclusive with --remote-bucket-id)string
--remote-bucket-idRemote bucket ID to replicate data to (mutually exclusive with --remote-bucket-name)string
--max-queue-bytesMax queue size in bytes (default: 67108860)integer
--drop-non-retryable-dataDrop data when a non-retryable error is encountered
--no-drop-non-retryable-dataDo not drop data when a non-retryable error is encountered
--max-ageSpecify a maximum age (in seconds) for data before it is droppedinteger
--hostInfluxDB HTTP address (default http://localhost:8086)stringINFLUX_HOST
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
-c--active-configCLI configuration to use for commandstring
--http-debugInspect communication with InfluxDB serversstring
--jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
--hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
-t--tokenInfluxDB API 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

Create a replication stream

  1. Create a remote connection, if you haven’t already.
  2. Use influx remote list to get the ID for the remote you want to replicate data to.
    $ influx remote list
    ID			        Name		Org ID
    0ooxX0xxXo0x 	    myremote    [...]
  3. Create the replication:
    influx replication create \
      --name myreplication
      --local-bucket example-local-bucket
      --remote-bucket example-remote-bucket
      --remote-id 0ooxX0xxXo0x

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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

InfluxDB Cloud Serverless