feat(ins): update doc sbs migration (#4505)

* feat(ins): update doc sbs migration * feat(ins): update * fix(ins): update * Apply suggestions from code review Co-authored-by: Néda <[email protected]> * feat(ins): update content * feat(ins): feature * feat(ins): add link --------- Co-authored-by: Néda <[email protected]>
scaleway · Feb 27, 2025 · 79a572c · 79a572c
1 parent e83e35a
commit 79a572c
Showing 1 changed file with 36 additions and 3 deletions.
diff --git a/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx
@@ -19,13 +19,14 @@ To facilitate the transition to Scaleway's new Block Storage management, two mai
 
 - [Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-instance-apicli-migration-endpoint-plan-and-apply):
    - **Advantage:** Migration can occur without service interruption, as the volume remains attached to the running Instance and fully accessible.
-   - **Drawback:** Only the volume's representation is migrated to the SBS API; the data itself does not move. This means the migrated volume will not benefit from low latency or higher IOPS, as it retains the original `b_ssd` characteristics.
+   - **Drawback:** Only the volume's representation is migrated to the SBS API; the data itself does not move. This means the migrated volume will not benefit from low latency or higher IOPS, as it **retains the original `b_ssd` characteristics**.
 
 - [Using the snapshot export/import features](#migrating-using-the-snapshot-exportimport-features):
    - **Advantage:** The migrated volume will fully support low latency, and it is possible to modify the IOPS up to 15k. All existing data of the old volume will be copied to the new Block Storage Low Latency volume.
    - **Drawback:** A snapshot must be manually created, exported, and imported. After importing, the snapshot must be converted into a volume, which must then be attached to the Instance. This process may require downtime.
 
-Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/block-storage/quickstart/) instead of Compute.
+Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/block-storage/quickstart/) instead of Compute.<br />
+Learn more about the [advantages of migrating from the Instance API to the Block Storage API for managing block volumes and snapshots](/block-storage/reference-content/advantages-migrating-to-sbs/).
 
 ## Comparison of migration methods
 
@@ -37,11 +38,33 @@ Each method caters to different needs, balancing uninterrupted service against a
 This guide offers step-by-step instructions to migrate your volumes and snapshots using either the [Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) tool (recommended) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-volumes-migrate-a-volume-andor-snapshots-to-sbs-scaleway-block-storage).
 Alternatively, you can use the [snapshot export/import feature](/instances/api-cli/snapshot-import-export-feature/) to migrate your unified volumes and snapshots to Block Storage Low Latency volumes.
 
-
 <Message type="important">
   Volumes **created and managed through Kubernetes** do not fall within the scope of the migration described on this page. Find specific instructions for migrating Kubernetes volumes behind the Scaleway Block Storage API in the [managing storage for Kubernetes documentation](/kubernetes/api-cli/managing-storage/#upgrading-to-csi-version-03).
 </Message>
 
+## Comparison of Block Storage volume types
+
+| Volume type                   | IOPS | Underlying hardware         | Latency         | Max volume size | Recommended use cases | Availability & resilience |
+|-----------------------------------|----------|--------------------------------|---------------------|----------------------|-------------------------|----------------------------|
+| `b_ssd` (Block Storage 5K legacy) | 5,000    | Legacy SSDs                    | Higher              | Up to 10 TB          | General-purpose workloads that do not demand high IOPS or low latency | Data is replicated three times across multiple disks for high availability and integrity |
+| `sbs_5k` (Block Low Latency 5K)   | 5,000    | Modern NVMe disks               | Low                 | 5 GB to 10 TB        | Development environments, web servers, and applications needing consistent performance | 99.99% SLA, triple-replicated data to safeguard against hardware failures |
+| `sbs_15k` (Block Low Latency 15K) | 15,000   | Modern NVMe disks               | Very low           | 5 GB to 10 TB        | High-performance databases, transactional applications, and I/O-intensive workloads | 99.99% SLA, triple-replicated data to safeguard against hardware failures |
+
+You can attach a maximum of 16 volumes (including the mandatory boot volume) to a single Instance.
+
+<Message type="tip">
+  Refer to [Understand the difference between Block Storage volumes and Block Storage Low Latency volumes](/block-storage/reference-content/differences-between-5kiops-volumes/) for more information on the differences between Block Storage 5K legacy volumes and Block Storage Low Latency 5K volumes.
+</Message>
+
+### Additional details:
+
+- `b_ssd`: These volumes are based on older SSD technology, providing reliable performance but with limitations in terms of speed and latency.
+- `sbs_5k`: These volumes use NVMe technology, offering better performance and lower latency. They allow flexibility to adjust storage based on your needs.
+- `sbs_15k`: These volumes offer even higher performance, with up to 15,000 IOPS, making them ideal for workloads requiring fast and reliable data access.
+    <Message type="note">
+      To maximize compatibility with Block Storage Low Latency 15K, select an Instance with at least [3 GiB/s of Block bandwidth](/instances/reference-content/instances-bandwidth-overview/).
+    </Message>
+
 <Macro id="requirements" />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
@@ -162,6 +185,11 @@ Alternatively, you can use the [snapshot export/import feature](/instances/api-c
   </TabsTab>
 </Tabs>
 
+<Message type="important">
+   After the migration, your volume's type will still be `b_ssd` (displayed as **Block SSD 5K legacy** in the Scaleway console).
+   To benefit from the new features and performance of Scaleway Block Storage, you must create a new volume (`sbs_5k` or `sbs_15k` displayed as **Block Low Latency 5K** or **Block Low Latency 15K** in the Scaleway console) using the snapshot export/import feature. For more information, see [Migrating using the snapshot export/import features](#migrating-using-the-snapshot-exportimport-features).
+</Message>
+
 ### Migrating an existing Block Storage snapshot to Scaleway Block Storage management
 
 <Message type="important">
@@ -255,6 +283,11 @@ Alternatively, you can use the [snapshot export/import feature](/instances/api-c
   </TabsTab>
 </Tabs>
 
+<Message type="important">
+   After the migration, your volume's type will still be `b_ssd` (displayed as **Block SSD 5K legacy** in the Scaleway console).
+   To benefit from the new features and performance of Scaleway Block Storage, you must create a new volume (`sbs_5k` or `sbs_15k` displayed as **Block Low Latency 5K** or **Block Low Latency 15K** in the Scaleway console) using the snapshot export/import feature. For more information, see [Migrating using the snapshot export/import features](#migrating-using-the-snapshot-exportimport-features).
+</Message>
+
 ## Migrating using the snapshot export/import features
 
 To convert your unified volumes and snapshots, you can use the snapshot export/import features as an alternative solution for transitioning a Block Storage legacy volume into a Block Storage Low Latency volume.