I find that if I use influxd backup -start <datetime> without specifying -end <datetime> that everything is backed up. I had expected to backup from the start to the current time. Is this expected behaviour? The workaround is simple, to include -end with a time in the future and it works as expected.
I am running influxdb 1.8.0 on Ubuntu 20.04.
@clanlaw,
If you include start, but exclude stop, it should backup from the start time until the most recent point.
Conversely, if you include stop, but exclude start all data will be backed up starting from 1970-01-01.
Hi @Anaisdg, that is what I assumed, but for me that is not happening. So for example if I do
influxd backup -portable -database Tydwr -start 2020-06-10T21:12:08Z -host <server>:8088 ~/temp/influxdb_backup
then I get a full backup from the begining of time. However, if I do
influxd backup -portable -database Tydwr -start 2020-06-10T21:12:08Z -end 2050-01-01T00:00:00Z -host <server>:8088 ~/temp/influxdb_backup
then I do get just the incremental backup.
I have tried multiple times and with various different start times but for me it is absolutely consistent.
Looking at the output I see, for example
backing up db=Tydwr rp=autogen shard=4 to /home/me/temp/influxdb_backupstartonly/Tydwr.autogen.00004.00 with boundaries start=2020-06-10T21:12:08Z, end=0001-01-01T00:00:00Z
The end time there looks suspicious, but that may just be what is expected. There is definitely no -end in the command line. Very odd.
