How to Recover Milvus Data After etcd Corruption Without a Backup
Jul 22, 2026Jack Li

Summary
This post describes a specific, non-standard data recovery procedure for Milvus instances suffering from etcd corruption without a backup. It details the steps involved: starting a clean Milvus instance, recreating the collection schema, copying old MinIO binlogs to a recovery prefix, using the Java SDK's bulkInsert API in backup mode to import candidate segments, and validating each segment before inclusion in the final recovered collection. It also explains why MinIO alone cannot rebuild a collection and the importance of validating segments to avoid duplicates.
More from the AI Data Storage Engine trail
- Milvus Snapshots: Point-in-Time Collection Views Without Copying Data
- Announcing Milvus 3.0: Lake-Native Vector Search and a More Powerful Retrieval Engine
- Open Tag: An Open-Source Claude Tag for Claude Code and Codex
- How Force Merge Compaction Nearly Doubled Milvus Search QPS
- When AI Agents Do the Work, What Do We Lose?