Migrate InfluxDB OSS instances to InfluxDB Enterprise clusters
Migrate a running instance of InfluxDB open source (OSS) to an InfluxDB Enterprise cluster.
Migration transfers all users from the OSS instance to the InfluxDB Enterprise cluster.
Migrate an OSS instance to InfluxDB Enterprise
Complete the following tasks to migrate data from OSS to an InfluxDB Enterprise cluster without downtime or missing data.
Upgrade InfluxDB OSS and InfluxDB Enterprise to the latest stable versions.
On each meta node and each data node, add the IP and hostname of your OSS instance to the
/etc/hostsfile. This will allow the nodes to communicate with the OSS instance.
On the OSS instance, take a portable backup from OSS using the influxd backup command with the
influxd backup -portable -host <IP address>:8088 /tmp/mysnapshot
Note the current date and time when you take the backup. For more information, see influxd backup.
Restore the backup on the cluster by running the following:
influxd-ctl restore <path-to-backup-files>
To avoid data loss, dual write to both OSS and Enterprise while completing the remaining steps. This keeps the OSS and cluster active for testing and acceptance work. For more information, see Write data with the InfluxDB API.
Export data from OSS from the time the backup was taken to the time the dual write started. For example, if you take the backup on
2020-07-19T00:00:00.000Z, and started writing data to Enterprise at
2020-07-19T23:59:59.999Z, you would run the following command:
influx_inspect export -compress -start 2020-07-19T00:00:00.000Z -end 2020-07-19T23:59:59.999Z`
For more information, see
Verify data is successfully migrated to your Enterprise cluster. See:
Next, stop writes to OSS instance, and remove it.
Stop writes and remove OSS
Stop all writes to the InfluxDB OSS instance.
influxdbservice on the InfluxDB OSS instance server.
- Double check that the service is stopped. The following command should return nothing:
ps ax | grep influxd
Remove the InfluxDB OSS package.
Rebalance the cluster
- Use the
ALTER RETENTION POLICYstatement to increase the replication factor on all existing retention polices to the number of data nodes in your cluster.
- Rebalance your cluster manually to meet the desired replication factor for existing shards.
- If you were using Chronograf, add your Enterprise instance as a new data source.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.