From 071284155804f150dbb998f35829c80f4e0e5cba Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Tue, 14 Jan 2025 15:01:01 +0100 Subject: [PATCH] docs(bls): improve doc --- .../how-to/migrate-volumes-snapshots-to-sbs.mdx | 13 ++++++++----- faq/blockstorage.mdx | 9 +++++---- .../advantages-migrating-to-sbs.mdx | 10 +++++++--- 3 files changed, 20 insertions(+), 12 deletions(-) diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index 2755860e4c..81be52c7c9 100644 --- a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -24,7 +24,7 @@ To facilitate the transition to Scaleway's new Block Storage management, two mai - [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](/storage/block/quickstart/) instead of Compute. ## Comparison of migration methods @@ -255,15 +255,18 @@ Alternatively, you can use the [snapshot export/import feature](/compute/instanc ## Migrating using the snapshot export/import features -To convert your unified volumes and snapshots you can use the snapshot export/import feature as an alternative solution to transition a Block Storage legacy volume into a Block Storage Low Latency volume. +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. The process below requires manual intervention and **does not preserve the original volume’s ID**. While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround. - Steps: - 1. [Export a snapshot of your unified volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). - 2. [Import the snapshot into a new local or Block volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). +Follow the procedure below: + +1. [Create a snapshot of your Block Storage legacy volume](/compute/instances/how-to/create-a-snapshot/). +2. [Export the snapshot](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). +3. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). + ## Going further diff --git a/faq/blockstorage.mdx b/faq/blockstorage.mdx index 075a68e9f1..80180953ea 100644 --- a/faq/blockstorage.mdx +++ b/faq/blockstorage.mdx @@ -56,17 +56,18 @@ Block Storage volumes are compatible with [Scaleway Instances](/compute/instance ## How can I convert a Block Storage legacy volume into a Block Storage Low Latency volume? -Currently, there is no direct way to change the storage class of a volume while preserving its ID. -However, you can use the snapshot export/import feature as a temporary solution to transition a Block Storage legacy volume into a Block Storage Low Latency volume. + +Although there is no direct way to change the storage class of a volume while preserving its ID, you can still convert a Block Storage legacy volume (along with its data) into a Block Storage Low Latency volume using the snapshot export/import features as a temporary solution. This allows you to transition a Block Storage legacy (`b_ssd`) snapshot into a Block Storage Low Latency (`sbs_5k` or `sbs_15k`) snapshot and then turn the snapshot into a Block Storage Low Latency volume. The process below requires manual intervention and **does not preserve the original volume's ID**. While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround. -1. [Export a snapshot of your Block Storage volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). -2. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). +1. [Create a snapshot of your Block Storage legacy volume](/compute/instances/how-to/create-a-snapshot/). +2. [Export the snapshot](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). +3. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). Find out how to [migrate your Block Storage volumes and snapshots](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API. diff --git a/storage/block/reference-content/advantages-migrating-to-sbs.mdx b/storage/block/reference-content/advantages-migrating-to-sbs.mdx index 69ed403ac0..81582e6b90 100644 --- a/storage/block/reference-content/advantages-migrating-to-sbs.mdx +++ b/storage/block/reference-content/advantages-migrating-to-sbs.mdx @@ -7,8 +7,8 @@ content: paragraph: Learn the key advantages of migrating to the Block Storage API for managing your Block Storage volumes and snapshots. tags: volumes block-storage 5kiops 10kiops sbs low-latency migration dates: - validation: 2025-01-13 - posted: 2025-01-13 + validation: 2025-01-14 + posted: 2025-01-14 categories: - storage --- @@ -90,7 +90,11 @@ When transitioning to the Block Storage API, you may notice changes in how volum ## How to transition? -For a step-by-step guide to transitioning your block volumes and snapshots from the Instance API to the Block Storage API, refer to [our migration documentation](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/). +- For a step-by-step guide to transitioning your block volumes and snapshots from the Instance API to the Block Storage API, refer to [our migration documentation](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/). + +- To identify which API manages your volumes and snapshots, refer to the [dedicated documentation](/storage/block/api-cli/identifying-volume-snapshot-api/). + +- To find out how to convert a Block Storage legacy volume into a Block Storage Low Latency volume, read [the dedicated documentation](/faq/blockstorage/#how-can-i-convert-a-block-storage-legacy-volume-into-a-block-storage-low-latency-volume). ---