Milvus 3.0 出了快照功能，给 AI 数据做轻量检查点，改模型换向量不用全量复制，搞 A/B 测试挺方便。
Milvus 3.0 的快照机制引用已有数据、索引和元数据文件而非复制全量数据。用户可在模型替换、重新嵌入、模式迁移前创建轻量检查点。不可变快照视图支持 A/B 评估、去重、回填验证和离线测试。通过对象存储服务端复制复用文件，避免重新导入和索引重建。注意快照不替代备份，备份用于长期保留和灾难恢复。
Milvus 3.0 resolves the fundamental AI workload conflict between continuously changing production da...
Milvus 3.0 resolves the fundamental AI workload conflict between continuously changing production data and stable offline computation by introducing low-cost, point-in-time, read-only collection snapshots. In AI systems, data states shift constantly: models are updated, embeddings are regenerated, and schemas evolve, while online collections must continuously serve queries and ingest new writes. Offline batch jobs, however, require fixed, reproducible data views to generate consistent results—a gap snapshots are designed to fill. 𝗦𝗻𝗮𝗽𝘀𝗵𝗼𝘁𝘀 achieve low overhead by referencing existing data, index, and metadata files instead of duplicating full datasets. This enables lightweight checkpoint creation before risky operations including model swapping, re-embedding, and schema migration. While the primary production collection keeps changing, immutable snapshot views support a wide range of isolated batch workflows, such as A/B evaluation, deduplication, backfill validation, and offline testing. Snapshots also accelerate data recovery and cloning. Milvus reuses existing data and index files via object storage server-side copy, eliminating expensive full data reimports and index rebuilds. This capability is critical for AI pipelines, because embeddings and derived features are version-dependent outputs rather than permanent source-data attributes. Snapshots provide stable, low-cost checkpoints for validating iterations and rolling back faulty releases without heavy backup overhead. Notably, snapshots do not replace backups. Snapshots rely on live collection resources and serve short-term logical operations: version rollback, cloning, and stable view isolation. Backups create independent, durable copies for long-term retention and disaster recovery. In summary, snapshots manage frequent data changes for agile AI iteration, while backups protect against permanent data loss. Kn milvus.io/blog/milvus-sn… svDWFw3lp 💬 0 🔄 0 ❤️ 0 👀 59 ⚡