-
Notifications
You must be signed in to change notification settings - Fork 50
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 check failed for Azure Blob Storage Account #312
Comments
Why this issue is closed? |
Facing the same issue. Is there any solution available? |
No idea. I have modified the code to resolve the backup issue, but it wasn't right I think. Because restore fails now. |
What changes did you make in the code above to make the backup start working? |
Inside |
Issue raised again here: #446 |
+1 |
Current Behavior
Expected Behavior
No response
Steps To Reproduce
Deploy Milvus on Azure with AKS with Azure Blob Storage Account ready as external object storage for Milvus as described at https://milvus.io/docs/azure.md : ... minio: enabled: false externalS3: enabled: true host: core.windows.net port: 443 rootPath: "file" bucketName: "milvus-bucket" # the storage account container name cloudProvider: azure useSSL: true accessKey: "my_storage_account_name" # the storage account name secretKey: "my_storage_account_key1" Check Milvus blobs in Azure SA container ... Configure backup2az_rg-tmw4xrkn.yaml for milvus-backup : http: simpleResponse: true milvus: address: 10.45.255.4 port: 19530 authorizationEnabled: true tlsMode: 0 user: "root" password: "rootpass" minio: storageType: "azure" address: "core.windows.net" # Address of MinIO/S3 port: 443 # Port of MinIO/S3 accessKeyID: "my_storage_account_name" # accessKeyID of MinIO/S3 secretAccessKey: "my_storage_account_key1" # MinIO/S3 encryption string useSSL: true # Access to MinIO/S3 with SSL useIAM: false iamEndpoint: "" bucketName: "milvus-bucket" # Milvus Bucket name in MinIO/S3, make it the same as your milvus instance rootPath: "file" # Milvus storage root path in MinIO/S3, make it the same as your milvus instance backupAccessKeyID: "my_storage_account_name" # the storage account name backupSecretAccessKey: "my_storage_account_key1" # the storage account key1 backupBucketName: "milvus-bucket-backup" backupRootPath: "file-backup" backup: maxSegmentGroupSize: 2G parallelism: backupCollection: 4 copydata: 128 restoreCollection: 2 keepTempFiles: false gcPause: enable: false Run: milvus-backup --config ./backup2az_rg-tmw4xrkn.yaml check
Environment
Anything else?
The text was updated successfully, but these errors were encountered: