Issues with backup

,
1

Hi, first time poster so please be gentle.

Probably something stupid I’m doing, but I recently migrated from a Raspberry Pi running influxd 1.0 to an x86 Ubuntu 16.04 running influxd 1.2.

Migration seemed to go fine, I basically installed influxd using apt from the the repos, replaced the config file with my old RPi config file, and then backed up my old metastore and database, and restored them to the new server.

All is well and I have Grafana graphing the data, new data is being added. However, when I’ve come to configuring backups, I’m seeing an issue. I can backup the metastore, but when I try and run a database backup I’m getting:

$ sudo influxd backup -database SmartThings /home/nnnn/influxdb_smartthings
2017/03/21 20:56:16 backing up db=SmartThings since 0001-01-01 00:00:00 +0000 UTC
2017/03/21 20:56:16 backing up metastore to /home/nnnn/influxdb_smartthings/meta.05
2017/03/21 20:56:16 backing up db=SmartThings rp=autogen shard=2 to /home/pete/influxdb_smartthings/SmartThings.autogen.00002.00 since 0001-01-01 00:00:00 +0000 UTC
2017/03/21 20:56:16 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (0)...
2017/03/21 20:56:17 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (1)...
2017/03/21 20:56:18 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (2)...
2017/03/21 20:56:19 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (3)...
2017/03/21 20:56:20 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (4)...
2017/03/21 20:56:21 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (5)...
2017/03/21 20:56:22 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (6)...
2017/03/21 20:56:23 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (7)...
2017/03/21 20:56:24 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (8)...
2017/03/21 20:56:25 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Retrying (9)...
2017/03/21 20:56:26 backup failed: copy backup to file: err=<nil>, n=0
backup: copy backup to file: err=<nil>, n=0

I’ve tried runnign it without sudo, with sudo, specifying a shard, and it doesn’t seem to matter. always getting the Download shard x failed copy backup message as above.

Am I doing something wrong?

Thanks for any help!

Pete

2

@Bunnikins This sounds like an issue. Can you please open an issue over on InfluxDB?

3

Hi:

Adding to this thread. I am on influxv1.1.

I moved my influx from an old ec2 to different region. In the old one getting the back up was fine and I restored it to the new ec2 instance. Now in the new ec2 instance, when I run the database backup, it says everything is fine, but only the meta info is saved. The data is not being saved.

Wondering if I am doing something incorrect?

Thank you,
Mouli

[ec2-user@ip-172-31-39-157 ~]$ influxd backup -database test1 ./influxBkup/
2017/03/25 21:10:24 backing up db=test1 since 0001-01-01 00:00:00 +0000 UTC
2017/03/25 21:10:24 backing up metastore to influxBkup/meta.06
2017/03/25 21:10:24 backing up db=test1 rp=autogen shard=21 to influxBkup/test1.autogen.00021.00 since 0001-01-01 00:00:00 +0000 UTC
2017/03/25 21:10:24 backing up db=test1 rp=autogen shard=20 to influxBkup/test1.autogen.00020.00 since 0001-01-01 00:00:00 +0000 UTC
2017/03/25 21:10:24 backing up db=test1 rp=autogen shard=19 to influxBkup/test1.autogen.00019.00 since 0001-01-01 00:00:00 +0000 UTC
2017/03/25 21:10:24 backing up db=test1 rp=autogen shard=28 to influxBkup/test1.autogen.00028.00 since 0001-01-01 00:00:00 +0000 UTC
2017/03/25 21:10:24 backing up db=test1 rp=autogen shard=36 to influxBkup/test1.autogen.00036.00 since 0001-01-01 00:00:00 +0000 UTC
2017/03/25 21:10:24 backup complete

2017/03/25 21:10:24 backup complete
[ec2-user@ip-172-31-39-157 ~]$ ls -al ./influxBkup/
total 36
drwxrwxr-x 2 ec2-user ec2-user 4096 Mar 25 21:10 .
drwx------ 8 ec2-user ec2-user 4096 Mar 25 21:04 …
-rw-rw-r-- 1 ec2-user ec2-user 3917 Mar 25 19:18 meta.00
-rw-rw-r-- 1 ec2-user ec2-user 3917 Mar 25 20:26 meta.01
-rw-rw-r-- 1 ec2-user ec2-user 3917 Mar 25 20:27 meta.02
-rw-rw-r-- 1 ec2-user ec2-user 3917 Mar 25 20:34 meta.03
-rw-rw-r-- 1 ec2-user ec2-user 3917 Mar 25 20:50 meta.04
-rw-rw-r-- 1 ec2-user ec2-user 3917 Mar 25 20:59 meta.05
-rw-rw-r-- 1 ec2-user ec2-user 3917 Mar 25 21:10 meta.06