InfluxDb 1.5 restore backup error

influxdb
backup

#1

Hi !
I’m facing an issue I was not able to solve, I spent my whole day on it…
I’m using InfluxDb 1.5. I created a backup using the command line, influxd.exe -backup -database xxxx . All seemed to work as expected ; I came up with a bunch of “xxxxxx”.autogen.“xxxx” files.
But… I can’t restore it. I want to restore it to a new db, and I’m using this syntax :
influxd restore -online -newdb <my_backup_files_path>

This is the output :

2018/03/15 17:19:46 Using metastore snapshot: <my_backup_files_path>\meta.00
2018/03/15 17:19:47 error updating meta: updating metadata on influxd service failed: err=read tcp 127.0.0.1:56100->127.0.0.1:8088: wsarecv: An existing connection was forcibly closed by the remote host., n=0
restore: updating metadata on influxd service failed: err=read tcp 127.0.0.1:56100->127.0.0.1:8088: wsarecv: An existing connection was forcibly closed by the remote host., n=0

I tried with the influxdb.exe process launched, I tried after having stopped it, I tried specifying the IP (all is on my local machine), I tried -portable, etc. None worked.

What have I missed ?


#2

Nobody can help me…?
I still have the very same error.
My app in in production ; if I can’t find a way to make this work, I’d have to search for another TSDB. This drives me crazy !


#3

Hi,

same problem here: basic local restore , database doesn’t exist. Same type of error return as described above.
C:\Influxdb>influxd restore -portable c:\Temp\backup6
2018/07/16 16:17:23 error updating meta: updating metadata on influxd service failed: err=read tcp [::1]:60031->[::1]:8088: wsarecv: An existing conne
ction was forcibly closed by the remote host., n=16
restore: updating metadata on influxd service failed: err=read tcp [::1]:60031->[::1]:8088: wsarecv: An existing connection was forcibly closed by the
remote host., n=16


#4

Any update on this issue. Facing the below error message.
error updating meta: updating metadata on influxd service failed: err=read tcp 192.168.2.2:50346->192.168.2.2:8088: wsarecv: An existing connection was forcibly closed by the remote host., n=16
restore: updating metadata on influxd service failed: err=read tcp 192.168.2.2:50346->192.168.2.2:8088: wsarecv: An existing connection was forcibly closed by the remote host., n=16

We tried -portable as well as legacy backup and restoration methods, both of them didn’t work.

As per my understanding, this has something to do with the tcp listening port 8088. After we transport data to the tcp port, there is some exception occurring and the listening port gets interrupted.

If any one has some solution or workaround, to restore kindly revert.


#5

Hi , can you , as a workaround , copy the backup files to the local server in a local backup location ?
And restore using the local backup ?


#6

Hi Marc,
I am not able to understand, what you mean to convey exactly. Can you please elaborate a bit.
I tried to copy manually the tsm files from data folder from source to destination db instance but it didn’t work.


#7

Hi ,
The topic is about a restore problem ,
I assumed you have a problem restoring your database from a backup taken with influxd.exe -backup .
Now you try to do a restore which fails .
The backup is located on a remote server.
My suggestion is to copy the backup to a local drive on your server and retry the restore with influxd restore …


#8

Thanks for the suggestion, MarcV.
We have copied backup files on local drive and tried to restore. Still we faced same error.


#9

Sorry to hear that Manoj … You could try using the restore option -newdb ?


#10

Tried, problem persist.


#11

Hi Manoj,
can you show the failing restore command ?
Is the influxd daemon running while you try the restore ?
As I understand correctly you have a second source database that is still ok , are you migrating that source to a new server ?


#12
  1. Command using
    inflxud restore -online -database “telegraf” “backup path”
  2. Is influxd daemon running
    Yes it is running.
  3. We are migrating source to new server.

Al last we copied wal,data and meta folder content. And it worked.