milvus-backup: [Bug]: Milvus-backup only restored the collection meta instead of index data
Current Behavior
go get
go build
Change
config/backup.yamlto my own s3 information.
./milvus-backup create -n my_backup
./milvus-backup restore -n my_backup -s _recover
Expected Behavior
I should see a new collection named my_collection_recover with the same stats as my_collection_recover, yet the new collection only has the metadata except for index data.


Steps To Reproduce
See above
Environment
Ubuntu 20.04 LTS
4 core 32 G ram
Docker Compose
Milvus-Standalone 2.2.2
Anything else?
Logs backup.log
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 3
- Comments: 20
@wayblink I currently have the same issue, for legacy reasons, I’m on an older version of milvus-backup (The previous one, compatible with Milvus 2.2.8) too, but it seems that this issue still persists for other people? It would be great if you can provide some insights what might be wrong here. I’ve turned on debug logging and the only suspicious thing I can see is:
I can post whole (sanitized) log and config if required, but it seems to be correct. Note that I’m using S3 instead of Minio.
I had the same problem