zilliztech / milvus-backup

Backup and restore tool for Milvus

zilliztech/milvus-backup Issues

[Bug]: when the partition key is enabled, restore will fail with error `execute job not allow to set partition name for collection with partition key`
Updated a month ago2
failed to check blob bucket exist
Updated a month ago
[Bug]: 在milvus:v2.3.9，使用milvus-backup:v0.4.12进行恢复，只能恢复元数据，无法恢复数据
Updated a month ago
[Bug]: When I used Tencent Cloud to store Milvus backups, an error occurred
Updated a month ago
[Feature]: Milvus Backup from MinIO S3 bucket to External S3 (AWS/GCP)
Updated 2 months ago
[Bug]: milvus-backup v0.3.3 in Milvus v2.2.11 standalone uses Docker. only restore schema but data is empty
Updated 2 months ago
The installation of Milvus standalone uses Docker. How can I backup it? Can I use the milvus backup tool?
Updated 2 months ago
[Bug]: Failed to Migrate to zilliz cloud
Updated 2 months ago1
[Enhancement]: Add the etcd also as part of backup
Updated 2 months ago
[Bug]: If there are upsert/delete operations on the collection, the data obtained from backup and the original data may be inconsistent
Updated 2 months ago
[Feature]: Licensing. Can Backup tool be part of MIT/Apache license ?
Updated 2 months ago
[Bug]: milvus-backup using metadata instead of aws credentials or role
Updated 2 months ago2
[Bug]: fail to flush the collection: knowledge_base
Updated 2 months ago1
help!!Fail to fill segment backup info
Closed 4 months ago15
[Feature]: If there are situations where 'RestoreBackup' partially completes the recovery of collections and some fail, there should be a channel to obtain details about the restoration process.
Updated 3 months ago
[Bug]: milvus-backup check failed for Azure Blob Storage Account
Updated 3 months ago
[Bug]: The backup is successful but the size information returned is wrong. Sometimes it is 0 and sometimes it is an incorrect value.
Closed 3 months ago
[Bug]: After the recovery is issued, query the recovery progress information. The returned progress may be inaccurate.
Closed 3 months ago
[Feature]:backup on localmode of milvus
Closed 3 months ago3
[Bug]: error="The specified bucket does not exist."]
Closed 4 months ago3
[Bug]: Nightly test timeout (2h) in 2.3.0-latest Milvus image while it can be finished in 1h in master-latest and 2.2.0-latest
Closed 4 months ago1
[DOCS]: milvus-backup minio 参数详解
Closed 4 months ago1
[Feature]:不同集群备份恢复报错Not found
Closed 4 months ago5
[Bug]: Stuck when backing up milvus
Closed 4 months ago1
[DOCS]: 配置文件中的storageType是什么意思
Closed 4 months ago4
Milvus Backup And Restoration (milvus is running as a cluster)
Updated 4 months ago7
[Feature]: 能不能提供区间备份，比如某个字段（id）在某个区间，把这部分备份和恢复
Updated 4 months ago1
[Bug]: Only backup meta
Closed 4 months ago2
[Bug]: The Content-Md5 you specified is not valid
Closed 5 months ago
[Bug]: 使用向量查询时，相同的向量查询的相似度相差甚远，使用cos计算的为0.999999，milvus查询的则为0.81，0.91
Closed 5 months ago2
[Bug]: Using the API to back up the collection, it is found that the quantity of backups has always been 0
Updated 5 months ago3
[Bug]: Size in list backup api response is 0, but in create backup api response, it has a valid value
Closed 5 months ago1
[Bug]: The data has been flushed before the backup, but there is much more data after the backup than before the backup.
Updated 5 months ago5
[Bug]: The index definition is missing from the restored data.
Closed 5 months ago2
[Bug]: indexes are loading when we restore data to another Milvus DB
Closed 5 months ago
[Feature]: incremental backup
Updated 5 months ago2
[Bug]: If there is an upsert operation before the backup, after the backup is restored, the data from the upsert will be considered as deleted
Closed 5 months ago3
[Typo]: change minio.cloudprovider comments to correctly reflect accepted cloudproviders in config.yaml
Closed 6 months ago1
[Feature]:不同集群备份恢复报错Not found
Closed 6 months ago
[Feature]:不同集群备份恢复报错not found
Closed 6 months ago
[Feature]: support backup for local SSD storage
Closed 6 months ago1
[Feature]:不同集群备份恢复报错not found
Closed 6 months ago
[Bug]: When I restored data, some DBs where missing
Updated 6 months ago2
[Bug]: Restore failed with error `workerpool: execute job bulk insert fail, info: fail to initialize in-memory segment data for shard id 0` and then the following task gets stucked
Updated 6 months ago5
[Bug]: Increase parameter control for the upper limit of S3 request volume
Updated 6 months ago
[Bug]: A集群的备份，无法还原到B集群
Closed 6 months ago1
[Bug]: Command 和 Server 返回值问题
Updated 6 months ago4
[Feature]:Restore suceessfully，but dosenot exit the data，just collection definition
Closed 6 months ago7
workerpool: execute job Access Denied.
Closed 6 months ago
[Enhancement]:Speed up backup
Closed 7 months ago