A Milvus Snapshot is a named, read-only, point-in-time version of a collection. It records referenc...

TL;DR · AI 摘要
Milvus快照通过引用而非复制数据,实现高效的数据版本管理。其核心价值在于模型升级前的数据备份与回滚验证。
核心要点
- 快照通过引用对象存储文件实现零数据冗余,节省存储成本
- 创建前需执行Flush操作确保数据完整性
- 适用于模型升级和数据回填前的版本锁定场景
结构提纲
按章节快速跳转。
思维导图
用一张图看清主题之间的关系。
查看大纲文本(无障碍 / 无 JS 友好)
- Milvus快照机制
- 核心特性
- 引用存储
- 只读版本
- 使用场景
- 模型升级备份
- 数据回填验证
- 操作流程
- Flush准备
- 创建命名快照
- 验证与清理
金句 / Highlights
值得收藏与分享的关键句。
快照记录引用而非复制数据,存储效率提升显著
Growing segments不包含在快照中需提前Flush
快照文件引用阻止垃圾回收,需及时清理无用快照
Milvus on X: "A Milvus Snapshot is a named, read-only, point-in-time version of a collection. It records references to the data and index files already in object storage, rather than duplicating the dataset. That makes it useful before a model upgrade or data backfill. Here’s the basic https://t.co/i1kRAJgAog" / X
Milvus
@milvusio
A Milvus Snapshot is a named, read-only, point-in-time version of a collection. It records references to the data and index files already in object storage, rather than duplicating the dataset. That makes it useful before a model upgrade or data backfill. Here’s the basic workflow: • 𝗦𝗲𝘁 𝘁𝗵𝗲 𝗯𝗼𝘂𝗻𝗱𝗮𝗿𝘆 If recent writes must be included, run Flush first. Growing segments are not included in a snapshot. • 𝗖𝗿𝗲𝗮𝘁𝗲 𝘁𝗵𝗲 𝘀𝗻𝗮𝗽𝘀𝗵𝗼𝘁 Give it a meaningful name, such as before_model_v2, so its retention purpose is clear. • 𝗨𝘀𝗲 𝗶𝘁 Restore into a new collection to validate a rollback, or read it through Spark / External Collection as fixed input. Then clean up. Snapshot-referenced files cannot be garbage-collected, so drop snapshots when they no longer earn their storage. Full walkthrough:
milvus.io/blog/milvus-sn…
4:42 PM · Aug 12, 2026
146
Views