Rebuilding vector indexes can add a long wait when restoring a Milvus backup. On Milvus 3.0.1 and ...
Milvus(@milvusio) · 人工智能
Rebuilding vector indexes can add a long wait when restoring a Milvus backup. On Milvus 3.0.1 and later, 𝗺𝗶𝗹𝘃𝘂𝘀-𝗯𝗮𝗰𝗸𝘂𝗽 𝟬.𝟲 𝘂𝘀𝗲𝘀 𝘁𝗵𝗲 𝘀𝗻𝗮𝗽𝘀𝗵𝗼𝘁 𝗯𝗮𝗰𝗸𝘂𝗽 𝗳𝗼𝗿𝗺𝗮𝘁 to restore data and existing indexes together. Snapshot restores avoid the row-by-row import scan and index rebuild required by the older binlog backup format. After restoration, you can load the collection and verify your queries. In our internal test, we used three collections with 10 million 768-dimensional vectors each: roughly 92 GB of data and 32 GB of indexes. • Snapshot restore: 𝟯𝟮𝟰 𝘀𝗲𝗰𝗼𝗻𝗱𝘀, including indexes. • Binlog restore: 𝟱𝟬𝟱 𝘀𝗲𝗰𝗼𝗻𝗱𝘀, with indexes still to rebuild. That’s about 𝟯𝟲% 𝗹𝗲𝘀𝘀 𝘁𝗶𝗺𝗲 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗿𝗲𝘀𝘁𝗼𝗿𝗲 𝘁𝗮𝘀𝗸 in this test. Collection loading and query validation come afterward. For your next migration or recovery drill, create a snapshot backup so you can github.com/zilliztech/mil… ng with the data. Learn how to restore Milvus from a snaphot: https://t.co/szRi6ALNT1 💬 0 🔄 0 ❤️ 0 👀 75 ⚡ Powered by xgo.ing