influxdata / influxdata/influxdb
influxdb_2.0.0-beta backup and restore to 2.1.1 fails 'Error: no backup manifests'
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. influx backup -p ./ on source VM
2. on new VM run influx restore ./
__Expected behavior:__
DB to be restored
__Actual behavior:__
New VM shows:
Error: no backup manifests found at: xxxxxx
__Environment info:__
* System info: Linux 5.4.0-97-generic x86_64
* InfluxDB version:
* New: InfluxDB 2.1.1 (git: 657e1839de) build_date: 2021-11-09T03:03:48Z
* old: InfluxDB 2.0.0-beta.16 (git: 50964d732c) build_date: 2020-08-07T20:18:07Z
Basically I run the backup on the old VM with:
`influx backup -p /xxxxx/backup/ -t xxxxxx`
This spits out 26 tsm files and a .bolt.
and on the new VM I run:
`influx restore /xxxxx/backup`
which gives:
`Error: no backup manifests found at "/mnt/media/backup"`
If I do:
`influx backup -portable -p /xxxxx/backup/ -t xxxxxx`
I get the same result.
I'm obviously missing the meta data but I can't find anything in the documentation about backing up meta data.
Contributor guide
Research direction
Start by reproducing the reported `influx backup` and `influx restore` commands using the stated InfluxDB 2.0.0-beta.16 and 2.1.1 versions, then inspect the generated backup directory for the manifests and metadata mentioned in the report. Done means determining whether this version combination can restore successfully, or documenting the required migration or backup procedure if it cannot.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100