milvus backup crossStorage side effect
#39230
-
When performing backup/restore operations in Milvus, if the copy API between object storage services is not supported, i need to set |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
@wayblink thanks for your work! |
Beta Was this translation helpful? Give feedback.
-
|
@huanghaoyuanhhy is the new maintainer of the milvus-backup. The The NewCopier() method returns a Copier object for copying data files from source to target storage. If the The Copier.copyByServer() gets a Reader from the source storage and calls UploadObject() of the target storage: So, all the jobs are done by remote s3/minio/azure API, technically has no impact to the source Milvus. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for answer! |
Beta Was this translation helpful? Give feedback.
@huanghaoyuanhhy is the new maintainer of the milvus-backup.
The
crossStorageis used here, assigned to the method NewCopier():https://github.com/zilliztech/milvus-backup/blob/731d697b6bc64abc9e23acde12f1f8caed7a2fe3/core/backup_context.go#L246
The NewCopier() method returns a Copier object for copying data files from source to target storage. If the
crossStorageis true, the Copier.copyByServer() is called:https://github.com/zilliztech/milvus-backup/blob/731d697b6bc64abc9e23acde12f1f8caed7a2fe3/core/storage/copier.go#L254
The Copier.copyByServer() gets a Reader from the source storage and calls UploadObject() of the target storage:
https://github.com/zilliztech/milvus-backup/blob/731d6…