Milvus-Backup Version
0.5.9
Can you reproduce this issue on the latest version?
Yes, it also happens on the latest version
Current Behavior
In a Milvus 2.6.7 environment, restoring a backed-up collection using the official milvus-backup tool failed with the core error no binlog for field:id (specifically for the auto-increment primary key field). The error points to the segment 463164218295959239, where the binlog file for the id field could not be recognized, leading to a bulk insert data failure.
Expected Behavior
No response
Steps To Reproduce
1. Create Backup (Successful)
./milvus-backup create -c TestVector.test_v3 -n test_v3_backup_20251229_020002
[2025/12/29 02:01:44.773 +08:00] [INFO] [backup/task.go:115] ["backup all collections successfully"] [backup_id=08b6321d-e417-11f0-b8a8-00163e2c86f3]
[2025/12/29 02:01:44.773 +08:00] [INFO] [backup/task.go:119] ["skip backup rbac"] [backup_id=08b6321d-e417-11f0-b8a8-00163e2c86f3]
[2025/12/29 02:01:44.773 +08:00] [INFO] [backup/task.go:123] ["start backup rpc channel pos"] [backup_id=08b6321d-e417-11f0-b8a8-00163e2c86f3]
[2025/12/29 02:01:44.773 +08:00] [INFO] [backup/task.go:353] ["try to get rpc channel pos"] [backup_id=08b6321d-e417-11f0-b8a8-00163e2c86f3] [rpc_channel=by-dev-replicate-msg]
[2025/12/29 02:01:44.775 +08:00] [WARN] [backup/task.go:123] ["Failed to back up RPC channel position. This won't cause the backup to fail, but may lead to inconsistency when reconnecting to CDC for incremental data replication."] [backup_id=08b6321d-e417-11f0-b8a8-00163e2c86f3] [error="backup: call replicate message failed: client: replicate message failed: client: operation failed: error_code:UnexpectedError reason:\"service unavailable: not supported in streaming mode\" code:2 retriable:true detail:\"service unavailable: not supported in streaming mode\""]
[2025/12/29 02:01:44.775 +08:00] [INFO] [backup/task.go:95] ["backup successfully"] [backup_id=08b6321d-e417-11f0-b8a8-00163e2c86f3]
[2025/12/29 02:01:44.775 +08:00] [INFO] [runtime/asm_amd64.s:1700] ["stop renewal pause gc lease"] [component=gc-pauser]
[2025/12/29 02:01:44.782 +08:00] [INFO] [backup/task.go:126] ["resume gc done"] [component=gc-pauser] [resp="{\"msg\": \"OK\"}"]
2.Restore Backup (Failed)
./milvus-backup restore -c TestVector.test_v3 -n test_backup_20251229_020002 -s _bak
Environment
Anything else?
No response
Milvus-Backup Version
0.5.9
Can you reproduce this issue on the latest version?
Yes, it also happens on the latest version
Current Behavior
In a Milvus 2.6.7 environment, restoring a backed-up collection using the official milvus-backup tool failed with the core error no binlog for field:id (specifically for the auto-increment primary key field). The error points to the segment 463164218295959239, where the binlog file for the id field could not be recognized, leading to a bulk insert data failure.
Expected Behavior
No response
Steps To Reproduce
Environment
Anything else?
No response