[Feature]:Restore suceessfully，but dosenot exit the data，just collection definition

[Jz-Lin]

Is your feature request related to a problem? Please describe.

milvus version:2.2.14 backup & restore ,but not found data,just collection definition ,entity count is zero milvus-backup create -n milvus_bakcup_1031_2 milvus-backup restore -n milvus_bakcup_1031_2 bakcup file:

Describe the solution you'd like.

No response

Describe an alternate solution.

No response

Anything else? (Additional Context)

No response

[IshanFernandoClouda]

https://github.com/zilliztech/milvus-backup/blob/69c09058b190d0ca79d47137b42ead3beabbc50a/configs/backup.yaml#L34-L42

Make sure that the bucket names are correct

[Jz-Lin]

the bakcup names is the same as the milvus instance config but the bakcuk file also just have meta dir, no binlogs dir

[zhuwenxing]

Collection definition is the metadata of collection, and it stores in etcd. so even though your minio config wrong, backup tools can still get them. But binlog(or segment) is stored in minio, so if the minio config is wrong, there will no data restore.

From the screenshots, most likely, your minio bucketName or rootpath is not right.

[Jz-Lin]

is there any command that i can test the minio bucketName or rootpath on backup config file is right ?

[wayblink]

is there any command that i can test the minio bucketName or rootpath on backup config file is right ?

You can use milvus-backup check command to verify your connections

[zhuwenxing]

is there any command that i can test the minio bucketName or rootpath on backup config file is right ?

You can get the info of minio from the mulvus.yaml in milvus pod or container if you have permission.

[Jz-Lin]

yes, i wrote the same as the mulvus.yaml in milvus pod before . mulvus.yaml rootPath is /root. now i change the bakcup.yaml , set rootPath : root , it backup sucessfully.