outcome:
out of my 6 DBs with 1-3 collections each only 2 collections were restored in total. But every database is at least being created (but not filled) when restoring a completely empty system.
1. backing up (works) with `./milvus-backup create -n my_backup`
2. restoring doesn't work, command: `./milvus-backup restore -n my_backup -s _recover`
I also tried to manually copy the data from the backup a-bucket to the milvus a-bucket before running the restore, but same result.
Environment
- milvus 2.4.9 via docker compose
- milvus-backup 0.4.23 running in a bitnami/pymilvus:2.4.6-debian-12-r2 container
- version of Milvus minio = Version of mivlus-backup minio = minio/minio:RELEASE.2023-03-20T20-16-18Z
- names: I want to backup and restore "milvus-minio-temp" to and from "milvus-backup-storage"
Current Behavior
Hello All, I'm facing some issues setting up a backup routine for Milvus 2.4.9.
command:
./milvus-backup restore -n my_backup -s _recover
outcome: out of my 6 DBs with 1-3 collections each only 2 collections were restored in total. But every database is at least being created (but not filled) when restoring a completely empty system.
logs:
Expected Behavior
all collections to be present in my DBs
Steps To Reproduce
Environment
Anything else?
No response