krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-08 20:38:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Migration and recovery options guide (#2426)

Browse Source 
* Add migration and recovery options comparison page

Adds a new deploy-section page comparing the three data movement
options (migration tool, snapshots, cloud backups) across use case,
performance, operations, infrastructure limits, and resource
requirements — including the 2× RAM/disk headroom rule.

Closes #47

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Added 2× RAM and disk headroom warning for migration scenarios to other docs

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Edits

* Review feedback

* Review feedback

* Review feedback

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Abdon Pijpelink
2026-06-23 12:59:13 +02:00
committed by GitHub
co-authored by Claude Sonnet 4.6
parent 94a7c95893
commit 8dce906b74
4 changed files with 130 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/migrate-to-qdrant/from-qdrant.md
+7 -1
View File
@@ -7,7 +7,9 @@ weight: 110
# Migrate Between Qdrant Instances
Use the `qdrant` subcommand to copy a collection from one Qdrant instance to another — or between collections within the same instance. The tool automatically recreates the full collection schema (vector config, HNSW settings, quantization, sharding) on the target.
Use the `qdrant` subcommand to copy a collection from one Qdrant instance to another or copy data between collections within the same instance.
If the target collection does not exist, the tool automatically creates it using the source collection's configuration (vector config, HNSW settings, quantization, sharding). To change the target collection's configuration, create the target collection manually before running the migration.
## What You Need
@@ -17,6 +19,10 @@ Use the `qdrant` subcommand to copy a collection from one Qdrant instance to ano
- **Target collection name** (must be different from source if using the same instance)
- **API keys** — for each instance, if authentication is enabled
<aside role="alert">
The target cluster needs <strong>twice the RAM and disk</strong> of the source collection during migration. Qdrant keeps original segments alongside newly built ones during optimization. You can scale back down once the migration completes.
</aside>
## Concept Mapping
| Source Qdrant | Target Qdrant | Notes |