motleyagency / influxdb-incremental-restore Goto Github PK

For simplicity

Something like:

https://github.com/AndiDittrich/Node.CLI-Progress

or

https://github.com/visionmedia/node-progress

I was looking for a solution to keep two InfluxDB instances in sync when I found this repo. I tried restoring a backup from our Influx01 to Influx02 running on a t2.medium and it took 15 minutes for a modestly sized dataset.

Also, the merge attempt failed several times before completing.

Any ideas on what is causing this issue? Is merging the data that resource intensive?

By default the API runs at 8086 and the daemon in 8088

Command cleanup should clean the databases the script has created if they exist

Hi,

We just found this utility is useful and tried to restore our influxdb incremental backups, but we are getting issues as below.

1. Initially the restoration failed with the below error,
   ERR: partial write: field type conflict: input field "value" on measurement "measurement_name" is type float, already exists as type integer dropped=77
   So as suggested by you I tried "-useTargetMeasurements"
2. Now I'm getting the below error
   Using target measurements: host::tag,metric_type::tag,value::float
   Using target measurements: host::tag,metric_type::tag,value::float
   ERROR: Command failed: influx -host 127.0.0.1 -port 8086 -format=column -execute SELECT host::tag,metric_type::tag,value::float INTO test_db..agents.online FROM test_db_20190630T000016Z..agents.online GROUP BY *
   error parsing query: too many segments in "hip_restore_test".."agents".online at line 1, char 1

Also we noticed that the field types are changing to "float" in restored database (For some fields).
In original database field type for some measurements is "Integer" but in incremental_restored backup database the field type is "float"

Can you please check and let us know if any workarounds are there?

I tried this, with Influx 1.8.0, and it is perfect (and very much needed) except that everything is restored to the autogen retention policy instead of the ones actually in use. Using influxd restore does restore ok (but not the whole set of backups of course.
Is this a known issue or am I doing something wrong?
If I explicitly specify a retention policy (-rp) then the policy is created but there is no data there.
I am using nodejs 12.18.0 on Ubuntu 19.10.
I very much hope there is a solution to this as it would save me a lot of hassle.

It's a step that might take a long time and currently is pretty much on mute