As the core component of data infrastructure, responsible for storing invaluable operations and monitoring data, the time-series database is not something that can be easily ripped and replaced. However, there can come a time when your TSDB begins to hold you back and you need to consider alternatives.
TDengine Enterprise provides zero-code connectors for a variety of databases, including InfluxDB, that allow you to replicate existing data to TDengine through a simple GUI. With our InfluxDB connector, you can easily synchronize TDengine with InfluxDB, allowing you to test TDengine thoroughly on production data before making decisions, and also ensuring complete continuity with no data loss. Best of all, the interface is simple, and the operation can be performed without writing code or involving development teams.
To replicate data from InfluxDB to TDengine Enterprise, all you’ll need to know is:
-
The IP address and port of your current InfluxDB deployment
-
The version of InfluxDB you’re currently running
-
The organization ID and token from InfluxDB, which you can obtain through the InfluxDB GUI
-
The InfluxDB buckets that you want to replicate
Once you have this information, create one database in TDengine for each bucket that you want to replicate. Note that because InfluxDB stores data with nanosecond-level precision, it’s recommended that you create nanosecond-precision databases in TDengine. You can create your databases in the taosExplorer GUI or by using SQL.
Then log in to taosExplorer, click Data In, and select Add Task. Fill out the information and you’re ready to go.
Once you click Save & Apply, the data replication task is started, and data is replicated into your TDengine deployment. Let it run for a few days and compare the results to make sure the data is identical — you can check row counts, for example. When you’re satisfied that the data is in sync, you can simply redirect your data sources to write data to TDengine instead of InfluxDB.
Because TDengine supports ingestion from Telegraf as well as the InfluxDB line protocol, all you’ll need to do is change those configurations to point to TDengine instead of your existing InfluxDB deployment. Once that has been completed and no new data is being written to InfluxDB, your migration is complete. Note that because TDengine only supports standard SQL, not InfluxQL or Flux, you’ll have to rewrite your queries — but with the deprecation of Flux, you would have to do so anyway just to upgrade to InfluxDB 3.
If you’re interested in exploring alternatives to InfluxDB and would like a truly seamless migration experience, contact us today for a demonstration of TDengine Enterprise. Our team can help you come up with a migration plan to ensure that your data stack and applications remain stable while you benefit from the higher performance and richer feature set of TDengine.
