Documentation

Dual write to InfluxDB OSS and InfluxDB Cloud

If you want to back up your data in two places, or if you’re migrating from InfluxDB OSS to InfluxDB Cloud Serverless, you may want to set up Telegraf to dual write.

Use Telegraf to write to both InfluxDB OSS and InfluxDB Cloud Serverless simultaneously.

The sample configuration below uses:

Use the configuration below to write your data to both OSS and Cloud Serverless instances simultaneously.

Sample configuration

# Include any other input, processor, or aggregator plugins that you want to include in your configuration.

# Send data to InfluxDB OSS v2
[[outputs.influxdb_v2]]
  ## The URLs of the InfluxDB instance.
  ##
  ## Multiple URLs can be specified for a single cluster, only ONE of the
  ## urls will be written to each interval.
  ## urls exp: http://127.0.0.1:9999
  urls = ["http://localhost:8086"]

  ## OSS token for authentication.
  token = "${INFLUX_TOKEN_OSS}"

  ## Organization is the name of the organization you want to write to. It must already exist.
  organization = "ORG_NAME_OSS"

  ## Destination bucket to write to.
  bucket = "BUCKET_NAME_OSS"

# Send data to InfluxDB Cloud Serverless instance
 [[outputs.influxdb_v2]]
  ## The URLs of the InfluxDB Cloud instance.

  urls = ["https://cloud2.influxdata.com"]

  ## Cloud token for authentication.
  token = "${INFLUX_TOKEN}"

  ## For InfluxDB Cloud Serverless, set organization to an empty string.
  organization = ""

  ## Destination bucket to write into.
  bucket = "BUCKET_NAME"

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