-
Notifications
You must be signed in to change notification settings - Fork 48
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]: Data recovery fails #435
Comments
Please run Have you check whether the path 'backup/firstbackup4/meta/backup_meta.json' exists? What is your S3 provider? I guess it may related to the path assembly. Try add |
|
Is there something wrong with my profile? Now the backup can be successful, but when checking, the message is empty, and the backup file cannot be found when restoring. |
You are checking the source milvus or the target cluster? If is the source. If is the target, please run |
I use the same configuration file when performing backup and restore. The backup can be successful, but the recovery cannot be successful. See above for my profile |
A problem has been found. The backup execution prompt was successful, but it was not seen on the object store(cos from Tencent). Only a meta directory was found |
@suyestyle mentioned above. The config may be wrong. No binlog data is backuped actually. Please config the minio part the same as your milvus cluster. |
I modified the configuration according to the actual situation of my environment by referring to the official configuration. If there are errors in the configuration file, please help me correct them. I use object storage (Tencent's cos) instead of minio. Thank you very much. |
Now the backup is reporting an error.
|
I can't check the correctness by eye as it is all related to your env. Please make sure it is the same with the milvus config. |
This is a milvus inner exception, you have to see the milvus log to find the issue. |
milvus log
Backup log
milvus all log
|
Current Behavior
I successfully backed up the data using the milvus-backup, but a message was displayed indicating that I could not find the backup file during data restoration
Expected Behavior
No response
Steps To Reproduce
No response
Environment
cat configs/backup.yaml
Anything else?
No response
The text was updated successfully, but these errors were encountered: