-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: milvus-backup v0.3.3 in Milvus v2.2.11 standalone uses Docker. only restore schema but data is empty #322
Comments
Why not use according to the version recommended by the official website?BackUp v0.2.1ORv0.2.2 |
Because I use Milvus v2.2.11 @4-Struggle Why use milvus-backup v0.2.1 OR v0.2.2 ? |
Sorry, that's my question up there. As A user, I personally feel that the corresponding troubleshooting idea is to first confirm that the corresponding image version of machine A and machine B is the same, and finally confirm the corresponding backup version. Then try a different version of the backup |
Current Behavior
On machine A standalone uses Docker.
On machine B standalone uses Docker.
Milvus on B collections are empty but I has data on A . logs on two machine didn't has any error.
some logs on B
On A log
backup.log
On B log
backup.log
verify_data
only get this
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: