diff --git a/macros/compute/how-to-migrate-to-sbs.mdx b/macros/compute/how-to-migrate-to-sbs.mdx deleted file mode 100644 index ffefd90752..0000000000 --- a/macros/compute/how-to-migrate-to-sbs.mdx +++ /dev/null @@ -1,300 +0,0 @@ ---- -macro: how-to-migrate-to-sbs ---- -import Requirements from '@macros/iam/requirements.mdx' - -To enhance performance and reliability, Scaleway is transitioning the management of Block Storage volumes and snapshots from Compute to Storage. - -To facilitate the transition to Scaleway's new Block Storage management, two main approaches for migrating your volumes exist, each with its unique benefits and drawbacks: - -- [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**. - -- [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.
-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 - -| Migration Method | Advantage | Drawback | -|--------------------------------|-----------------------------------------------|---------------------------------------------| -| Instance API/CLI migration | No service interruption, volume remains accessible | Data characteristics remain the same; no performance boost | -| Snapshot export/import | Full support for low latency and customizable IOPS | Requires downtime; manual snapshot handling | - -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. - - - 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). - - -## 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. - - - 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. - - -### 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. - - 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/). - - - - -- A Scaleway account logged into the [console](https://console.scaleway.com) -- An [Instance](/instances/how-to/create-an-instance/) using [Block Storage volumes](/block-storage/how-to/create-a-volume/) - - - - The easiest way to migrate your Block Storage volumes and snapshots is by using the [Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) tool. - - If you encounter an error about quota limitations during the migration process, [contact our Support team](https://console.scaleway.com/support/tickets/create) for assistance. - - - - To ensure continued access to managing your volumes, you must convert your **unified volumes and snapshots** into either **local** or **Block volumes** before the **end-of-life date of June 2nd, 2025**. After this date, unified volumes and snapshots will no longer be supported by any API. - - #### Key migration deadlines: - - April 30th, 2025: - - Creation of new unified volumes via the Instance API will be disabled. - - Unified volumes will no longer be supported by the Instance API. - - June 2nd, 2025: - - Unified volumes and snapshots can no longer be managed via any API. Existing unified resources must be converted by this date to avoid loss of manageability. - - -## Migrating using the Instance API/CLI migration endpoint (Plan and Apply): - - - During migration, unified snapshots will be converted into [Block Storage](/block-storage/) snapshots and removed from Compute. If a unified snapshot is part of an image, it will be replaced by the corresponding Block Storage snapshot. - - -### Migrating an existing Block Storage volume to Scaleway Block Storage management - - - This process applies only to Block SSD (`b_ssd`) volumes. - - - - - - When you migrate a volume, the volume and any snapshots created from it will be migrated as well. - - 1. Use the following command to list your Block Storage volumes and retrieve the ID of the volume you wish to migrate: - ``` - $ scw instance volume list - ID STATE SERVER ID SERVER NAME - 369feb53-165f-437d-875e-188725df462b available - ``` - 2. Plan the volume migration using the `scw instance volume plan-migration ` command. This command returns the volume and its snapshots that will be migrated, along with a unique `ValidationKey` required to start the migration. - ``` - $ scw instance volume plan-migration 369feb53-165f-437d-875e-188725df462b - Volume.ID 369feb53-165f-437d-875e-188725df462b - Volume.Name vol-peaceful-davinci - Volume.Size 25 GB - Volume.VolumeType b_ssd - Volume.CreationDate 2 weeks ago - Volume.ModificationDate 2 weeks ago - Volume.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 - Volume.Project 4a2e00bf-5126-43ce-9b09-be943c619139 - Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c - Volume.Server.Name scw-naughty-robinson - Volume.State available - Volume.Zone fr-par-1 - Snapshots.0.ID a377afe5-a9a3-4706-b8c2-8d1c247a620f - Snapshots.0.Name image-scw-quirky-torvalds_snap_0 - Snapshots.0.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 - Snapshots.0.Project 4a2e00bf-5126-43ce-9b09-be943c619139 - Snapshots.0.VolumeType b_ssd - Snapshots.0.Size 10 GB - Snapshots.0.State available - Snapshots.0.CreationDate 2 weeks ago - Snapshots.0.ModificationDate 5 days ago - Snapshots.0.Zone fr-par-1 - Snapshots.1.ID 384799c2-c4dd-40ab-bd65-ed95cd7b4d5c - Snapshots.1.Name snap-eloquent-edison - Snapshots.1.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 - Snapshots.1.Project 4a2e00bf-5126-43ce-9b09-be943c619139 - Snapshots.1.VolumeType b_ssd - Snapshots.1.Size 10 GB - Snapshots.1.State available - Snapshots.1.CreationDate 2 weeks ago - Snapshots.1.ModificationDate 5 days ago - Snapshots.1.Zone fr-par-1 - ValidationKey 30d129ca895c4cd59f4c429e12dab300 - ``` - 3. Execute the migration using the `scw instance volume apply-migration validation-key= zone=` command. - ``` - $ scw instance volume apply-migration 369feb53-165f-437d-875e-188725df462b validation-key=30d129ca895c4cd59f4c429e12dab300 zone=fr-par-1 - ✅ Success - ``` - The volume migration is complete. You can now manage the migrated volume from the [Block Storage volumes section](https://console.scaleway.com/block-storage/volumes) in the Scaleway console. - - - - When you migrate a volume using the API, the volume and any snapshots created from the volume will be migrated. - - - 1. Plan the migration by sending a `POST` request to the Scaleway API: - - ```bash - curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/plan" \ - --header "Content-Type: application/json" \ - --header "X-Auth-Token: $SCW_SECRET_KEY" \ - --data "{ - \"volume_id\": \"$SCW_VOLUME_ID\" - }" - ``` - - This request returns the volume and its snapshots that will be migrated, along with a unique `ValidationKey` required to start the migration. - - 2. Confirm and execute the migration by sending another `POST` request: - - ```bash - curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/apply" \ - --header "Content-Type: application/json" \ - --header "X-Auth-Token: $SCW_SECRET_KEY" \ - --data "{ - \"volume_id\": \"$SCW_VOLUME_ID\", - \"validation_key\": \"$SCW_VALIDATION_KEY\" - }" - ``` - - - - - 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). - - -### Migrating an existing Block Storage snapshot to Scaleway Block Storage management - - - This process applies to Block SSD (`b_ssd`) or Unified (`unified`) snapshots. - - - - - - When you migrate a snapshot, the source volume of the snapshot and any snapshots created from this volume will also be migrated. - - 1. Use the following command to list your snapshots and retrieve the ID of the snapshot you wish to migrate: - ``` - $ scw instance snapshot list - ID NAME - a377afe5-a9a3-4706-b8c2-8d1c247a620f snap-eloquent-edison - ``` - 2. Plan the snapshot migration using the `scw instance snapshot plan-migration ` command. This command returns the source volume of the snapshot and any related snapshots that will be migrated, along with a unique `ValidationKey`. - ``` - $ scw instance snapshot plan-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f - Volume.ID 369feb53-165f-437d-875e-188725df462b - Volume.Name vol-peaceful-davinci - Volume.Size 25 GB - Volume.VolumeType b_ssd - Volume.CreationDate 2 weeks ago - Volume.ModificationDate 2 weeks ago - Volume.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 - Volume.Project 4a2e00bf-5126-43ce-9b09-be943c619139 - Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c - Volume.Server.Name scw-naughty-robinson - Volume.State available - Volume.Zone fr-par-1 - Snapshots.0.ID a377afe5-a9a3-4706-b8c2-8d1c247a620f - Snapshots.0.Name image-scw-quirky-torvalds_snap_0 - Snapshots.0.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 - Snapshots.0.Project 4a2e00bf-5126-43ce-9b09-be943c619139 - Snapshots.0.VolumeType b_ssd - Snapshots.0.Size 10 GB - Snapshots.0.State available - Snapshots.0.CreationDate 2 weeks ago - Snapshots.0.ModificationDate 5 days ago - Snapshots.0.Zone fr-par-1 - Snapshots.1.ID 384799c2-c4dd-40ab-bd65-ed95cd7b4d5c - Snapshots.1.Name snap-eloquent-edison - Snapshots.1.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 - Snapshots.1.Project 4a2e00bf-5126-43ce-9b09-be943c619139 - Snapshots.1.VolumeType b_ssd - Snapshots.1.Size 10 GB - Snapshots.1.State available - Snapshots.1.CreationDate 2 weeks ago - Snapshots.1.ModificationDate 5 days ago - Snapshots.1.Zone fr-par-1 - ValidationKey 30d129ca895c4cd59f4c429e12dab300 - ``` - 3. Execute the migration using the `scw instance snapshot apply-migration validation-key= zone=` command. - ``` - $ scw instance snapshot apply-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f validation-key=30d129ca895c4cd59f4c429e12dab300 zone=fr-par-1 - ✅ Success. - ``` - The snapshot migration is complete. You can now manage the migrated snapshot from the [Block Storage Snapshot section](https://console.scaleway.com/block-storage/volumes) in the Scaleway console. - - - - When you migrate a snapshot using the API, the source volume of the snapshot and any snapshots created from this volume will also be migrated. - - - 1. Plan the migration by sending a `POST` request to the Scaleway API: - - ```bash - curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/plan" \ - --header "Content-Type: application/json" \ - --header "X-Auth-Token: $SCW_SECRET_KEY" \ - --data "{ - \"snapshot_id\": \"$SCW_SNAPSHOT_ID\" - }" - ``` - - This request returns the source volume and any related snapshots that will be migrated, along with a unique `ValidationKey`. - - 2. Confirm and execute the migration by sending another `POST` request: - - ```bash - curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/apply" \ - --header "Content-Type: application/json" \ - --header "X-Auth-Token: $SCW_SECRET_KEY" \ - --data "{ - \"snapshot_id\": \"$SCW_SNAPSHOT_ID\", - \"validation_key\": \"$SCW_VALIDATION_KEY\" - }" - ``` - - - - - 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). - - -## 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. - - - 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. - - -Follow the procedure below: - -1. [Create a snapshot of your Block Storage legacy volume](/block-storage/how-to/create-a-snapshot/). -2. [Export the snapshot](/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 - -To learn more about managing your migrated Block Storage volumes and snapshots from the Scaleway console, refer to the [Block Storage Quickstart Guide](/block-storage/quickstart/). Additionally, you can explore advanced features using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/). - -If you encounter any issues during migration, contact [Scaleway's Support team](https://console.scaleway.com/support/tickets) for assistance. \ No newline at end of file diff --git a/menu/navigation.json b/menu/navigation.json index a333db58a1..ecc084dbd1 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -4995,12 +4995,8 @@ "slug": "create-volume-from-snapshot" }, { - "label": "Identify which API is managing your volumes", - "slug": "identify-api-managing-volumes" - }, - { - "label": "Migrate volumes and snapshots to Scaleway SBS", - "slug": "migrate-volumes-snapshots-to-sbs" + "label": "Identify the type of a volume or a snapshot", + "slug": "identify-volumes-snapshot-type" }, { "label": "Detach a volume", @@ -5036,10 +5032,6 @@ "label": "Increasing volume size via the API", "slug": "increasing-volume-size" }, - { - "label": "Identifying the API managing Block Storage volumes and snapshots", - "slug": "identifying-volume-snapshot-api" - }, { "label": "Unmounting a volume", "slug": "unmounting-a-volume" @@ -5054,10 +5046,6 @@ "label": "Differences between Block Storage volumes and Block Storage Low Latency volumes", "slug": "differences-between-5kiops-volumes" }, - { - "label": "Advantages of migrating from the Instance API to the Block Storage API for managing block volumes and snapshots", - "slug": "advantages-migrating-to-sbs" - }, { "label": "Block Storage and Instances bandwidth overview", "slug": "block-instances-bandwidth-overview" diff --git a/pages/block-storage/api-cli/identifying-volume-snapshot-api.mdx b/pages/block-storage/api-cli/identifying-volume-snapshot-api.mdx deleted file mode 100644 index 91a0d35c47..0000000000 --- a/pages/block-storage/api-cli/identifying-volume-snapshot-api.mdx +++ /dev/null @@ -1,353 +0,0 @@ ---- -title: Identifying the API managing Block Storage volumes and snapshots -description: Learn how to determine which API (Instance or Block Storage) manages your volumes and snapshots on Scaleway using CLI and API commands. -dates: - validation: 2025-07-31 - posted: 2025-01-13 ---- -import Requirements from '@macros/iam/requirements.mdx' -import BlockStorageMigration from '@macros/storage/block-storage-migration.mdx' - - -This page shows you how to identify the API managing your Block Storage volumes and snapshots, using the Scaleway API and CLI. - - - - - -- A Scaleway account logged into the [console](https://console.scaleway.com) -- Created [Block Storage volumes](/block-storage/how-to/create-a-volume/) -- [Created an API key](/iam/how-to/create-api-keys/) and set [your secret key as an environment variable](/scaleway-sdk/reference-content/environment-variables/#reserved-environment-variables) -- [Installed curl](https://curl.se/download.html) -- Installed the [Scaleway CLI](https://cli.scaleway.com/) - -## Listing all volumes and snapshots created in a specific Availability Zone - -The Scaleway Instance and Block Storage APIs identify their volumes differently. Volumes created with the Instance API are identified as `b_ssd` volumes, whereas volumes created with the Block Storage API are identified as `sbs_5k` or `sbs_15k` volumes. - -### Listing volumes created with the Instance API - -Open a terminal and run the following command to list your volumes managed by the Instance API. Make sure that you replace `{zone}` with the desired Availability Zone. - - ```bash - curl -X GET \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - "https://api.scaleway.com/instance/v1/zones/{zone}/volumes" - ``` - -Below is an example of the output that should display if you have created volumes in the `fr-par-1` Availability Zone using the Instance API. - -The `volume_type` field is set to `b_ssd`, meaning the volumes were created via the Instance API. - -``` -{ - "volumes": [ - { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "System volume", - "volume_type": "b_ssd", - "export_uri": null, - "organization": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "project": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "server": { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "scw-brave-elion" - }, - "size": 25000000000, - "state": "available", - "creation_date": "2024-01-30T13:11:15.554809+00:00", - "modification_date": "2024-01-30T13:11:17.078820+00:00", - "tags": [], - "zone": "fr-par-1" - }, - { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "Volume-data", - "volume_type": "b_ssd", - "export_uri": null, - "organization": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "project": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "server": { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "scw-brave-elion" - }, - "size": 20000000000, - "state": "available", - "creation_date": "2024-01-30T13:11:15.554809+00:00", - "modification_date": "2024-01-30T13:11:15.554809+00:00", - "tags": [], - "zone": "fr-par-1" - } - ] -} -``` - -### Listing volumes created with the Block Storage API - -Open a terminal and run the following command to list your volumes managed by the Block Storage API. Make sure that you replace `{zone}` with the desired Availability Zone. - -```bash - curl -X GET \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - "https://api.scaleway.com/block/v1alpha1/zones/{zone}/volumes" -``` - -Below is an example of the output that should display if you have created volumes in the `fr-par-1` Availability Zone using the Block Storage API. - -The `volume_type` field is set to either `sbs_15k` or `sbs_5k`, meaning the volumes were created via the Block Storage API. - -``` -{ - "volumes": [ - { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "volume-nifty-allen", - "type": "sbs_15k", - "size": 25000000000, - "status": "in_use", - "specs": { - "perf_iops": 15000, - "class": "sbs" - }, - "zone": "fr-par-1" - }, - { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "volume-xenodochial-mccarthy", - "type": "sbs_15k", - "size": 30000000000, - "status": "in_use", - "specs": { - "perf_iops": 15000, - "class": "sbs" - }, - "zone": "fr-par-1" - } - ], - "total_count": 2 -} -``` - -## Identifying the API managing snapshots - -### Using the Instance API - -Open a terminal and run the following command to list all snapshots created via the Instance API. Make sure that you replace `{zone}` with the desired Availability Zone. - -```bash - curl -X GET \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - "https://api.scaleway.com/instance/v1/zones/{zone}/snapshots" -``` - -An output similar to the following displays: - -``` -{ - "snapshots": [ - { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "snap-magical-driscoll", - "volume_type": "b_ssd", - "creation_date": "2024-01-29T15:19:12.357297+00:00", - "modification_date": "2024-01-29T15:22:13.885529+00:00", - "organization": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "project": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "size": 25000000000, - "state": "available", - "base_volume": null, - "tags": [], - "zone": "fr-par-1", - "error_details": null - } - ] -} -``` - -### Using the Block Storage API - -Open a terminal and run the following command to list all snapshots created via the Block Storage API. Make sure that you replace `{zone}` with the desired Availability Zone. - -```bash - curl -X GET \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - "https://api.scaleway.com/block/v1alpha1/zones/{zone}/snapshots" -``` - -An output similar to the following displays: - -``` -{ - "snapshots": [ - { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "snap-elated-thompson", - "parent_volume": { - "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "name": "volume-xenodochial-mccarthy", - "type": "sbs_15k", - "status": "in_use" - }, - "size": 30000000000, - "project_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", - "created_at": "2024-07-25T14:18:43.929942Z", - "updated_at": "2024-07-25T14:18:43.929942Z", - "references": [], - "status": "available", - "tags": [], - "class": "sbs", - "zone": "fr-par-1" - } - ] -} -``` - -## Identifying the API managing volumes with the CLI - -### Using the Scaleway Instance CLI - -1. Open your terminal and run the following command to list all your volumes. - - ```bash - scw instance volume list - ``` - - An output similar to the following displays: - - ``` - ID STATE SERVER ID - b582c548-6dc0-4e77-bb93-9615b9baa380 available a4138186-f362-41b2-adc2-c46a2e1a46b7 - 59d48a65-3501-49eb-9a93-be9a6b262e1e available bc1b3dde-b175-42f1-b322-f6d441fc49ca - 49985053-0141-4180-acfa-7f1a51526dac available 4780cdd0-1303-4dfe-9d72-92207eb195b1 - 7e1a9b98-b7ee-4bbc-8f8f-a7abbfffc937 available 67003b8c-2fe2-4346-a381-405896aa87b4 - 86bef16c-78db-4125-aa91-1ed9de9a50eb available 67003b8c-2fe2-4346-a381-405896aa87b4 - 7c232b97-63da-46e3-a018-399e1690b14b available ea5b27d7-268f-40fe-aff7-6943fbcac379 - 1a506e55-0741-4afd-8fbc-bc086ace0265 available 8860802f-0337-4901-b58c-ba3975922349 - ``` - -2. Copy the ID of the volume for which you want to check the type. - -3. Run the command below to get information about your volume, including its type. Make sure that you replace `` with the ID of the volume. - - ```bash - scw instance volume get - ``` - An output similar to the following displays: - ``` - Volume.ID 7c232b97-63da-46e3-a018-399e1690b14b - Volume.Name System volume - Volume.Size 10 GB - Volume.VolumeType b_ssd - Volume.CreationDate 1 year ago - Volume.ModificationDate 1 year ago - Volume.Organization 0c514155-9e5e-41a2-a900-9fdf0195b563 - Volume.Project 0c514155-9e5e-41a2-a900-9fdf0195b563 - Volume.Server.ID ea5b27d7-268f-40fe-aff7-6943fbcac379 - Volume.Server.Name scw-optimistic-wilbur - Volume.State available - Volume.Zone fr-par-1 - ``` - -4. Check the `Volume.VolumeType` field to learn if your volume is managed by the Instance API or the Block Storage API. Note that in our example, the `Volume.VolumeType` field displays `b_ssd`, meaning our volume is managed by the Instance API. - -### Using the Scaleway Block Storage CLI - -Open your terminal and run the following command to list all your volumes. - - ```bash - scw block volume list - ``` - -An output similar to the following should display: - - ```bash - ID NAME TYPE SIZE - 7a9f3816-7bb7-44ea-a103-832b9685cdc6 volume-nifty-allen sbs_15k 25 GB - cdab395b-c1b9-4a3b-a759-2add13eb2bcb volume-xenodochial-mccarthy sbs_15k 30 GB - 6708229e-bd8c-46f6-bcec-cd3ab93198b7 volume-interesting-keller sbs_5k 25 GB - 672d6c01-465f-43bd-a315-0ac48d49fec5 volume-amazing-lamarr sbs_5k 25 GB - 965b5361-01c5-4ca5-81dd-fa0307e36d20 volume-eloquent-grothendieck sbs_5k 25 GB - 13307e4a-c075-4421-b9b5-436732a1c739 vol-admiring-noether sbs_5k 25 GB - ``` - - Note that the `TYPE` field displays `sbs_15k` or `sbs_5k`, meaning our volumes are managed by the Block Storage API. - -## Identifying the API managing snapshots with the CLI - -### Using the Scaleway Instance CLI - -1. Open a terminal and run the following command to list your snapshots: - - ```bash - scw instance snapshot list - ``` - An output similar to the following displays: - ``` - ID NAME ORGANIZATION - d4b45594-7398-481d-8299-46292e07e404 snap-magical-driscoll 0c514155-9e5e-41a2-a900-9fdf0195b563 - ``` -2. Note the ID of the snapshot you want to check the type of. - -3. Get more information about your snapshot, including its type. Make sure that you replace `` with the ID of the snapshot. - - ```bash - scw instance snapshot get - ``` - - An output similar to the following displays: - - ```bash - Snapshot.ID d4b45594-7398-481d-8299-46292e07e404 - Snapshot.Name snap-magical-driscoll - Snapshot.Organization 0c514155-9e5e-41a2-a900-9fdf0195b563 - Snapshot.Project 0c514155-9e5e-41a2-a900-9fdf0195b563 - Snapshot.VolumeType b_ssd - Snapshot.Size 25 GB - Snapshot.State available - Snapshot.CreationDate 10 months ago - Snapshot.ModificationDate 10 months ago - Snapshot.Zone fr-par-1 - ``` - -4. Check the `Snapshot.VolumeType` field to see the type of the snapshot. Note that in the example above, the `Snapshot.VolumeType` field displays `b_ssd`, meaning our volume is managed by the Instance API. - -### Using the Scaleway Block Storage CLI - -1. Open a terminal and run the following command to list your snapshots: - - ```bash - scw block snapshot list - ``` - An output similar to the following displays: - - ``` - ID NAME SIZE PROJECT ID - 7f6ab0bd-cd0d-466b-b1e3-bd309dddfcf8 snap-elated-thompson 30 GB 0c514155-9e5e-41a2-a900-9fdf0195b563 - 92fa0096-30cf-4e7e-a1fe-2fbe73f524b9 snap-busy-albattani 25 GB e53c4255-f982-4d9d-a003-5ea43cb33707 - ``` -2. Note the ID of the snapshot for which you want to check the type. - -3. Run the command below to get information about your snapshot, including its type. Make sure that you replace `` with the ID of the snapshot. - - ```bash - scw block snapshot get - ``` - - An output similar to the following displays: - - ``` - ID 92fa0096-30cf-4e7e-a1fe-2fbe73f524b9 - Name snap-busy-albattani - ParentVolume.ID 965b5361-01c5-4ca5-81dd-fa0307e36d20 - ParentVolume.Name volume-eloquent-grothendieck - ParentVolume.Type sbs_5k - ParentVolume.Status available - Size 25 GB - ProjectID e53c4255-f982-4d9d-a003-5ea43cb33707 - CreatedAt 1 week ago - UpdatedAt 1 week ago - Status available - Zone fr-par-1 - Class sbs - ``` -4. Check the `ParentVolume.Type` field to see the type of the snapshot. Note that in the example above, the `ParentVolume.Type` field displays `sbs_5k`, meaning our volume is managed by the Block Storage API. \ No newline at end of file diff --git a/pages/block-storage/faq.mdx b/pages/block-storage/faq.mdx index 2847117eab..3aaf9ae8cc 100644 --- a/pages/block-storage/faq.mdx +++ b/pages/block-storage/faq.mdx @@ -79,9 +79,9 @@ Although there is no direct way to change the storage class of a volume while pr 2. [Export the snapshot](/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](/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API. +## Can I manage my Block Storage volumes using the Scaleway Instances API? -Find out about the [advantages of migrating the management of your volumes and snapshots](/block-storage/reference-content/advantages-migrating-to-sbs) from the Instance API to the Block Storage API. +It is no longer possible to manage your Block Storage volumes using the Instances API. ## Compatibility and integration diff --git a/pages/block-storage/how-to/identify-api-managing-volumes.mdx b/pages/block-storage/how-to/identify-api-managing-volumes.mdx deleted file mode 100644 index 606e7b98b4..0000000000 --- a/pages/block-storage/how-to/identify-api-managing-volumes.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: How to identify which API is managing your volumes -description: Learn how to identify which API is managing your volumes and snapshots using the Scaleway console. -tags: identify-volume-type identify-snapshot bssd sbs volume snapshot api -dates: - validation: 2025-03-24 - posted: 2025-03-24 ---- -import Requirements from '@macros/iam/requirements.mdx' -import BlockStorageMigration from '@macros/storage/block-storage-migration.mdx' - - -You can manage Block Storage resources using either the [Block Storage API](https://www.scaleway.com/en/developers/api/block/), or the [Instances API](https://www.scaleway.com/en/developers/api/instance/). - -This page shows you how to identify the API that manages your volumes and snapshots using the Scaleway console. Refer to our [dedicated documentation](/block-storage/api-cli/identifying-volume-snapshot-api/) to learn how to identify the API managing your volumes and snapshots using the API and CLI. - - - -- A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created [Block Storage volumes](/block-storage/how-to/create-a-volume/) -- Created [snapshots](/block-storage/how-to/create-a-snapshot/) - - - -## How to identify your volume type - -1. Click **Block Storage** in the **Storage** section of the side menu. A list of your volumes displays. - -2. Leave the **Block Storage API** filter in the drop-down, or select **Instance API** to display either your volumes managed by the Block Storage API, or the Instance API. - -3. Click the **Volume type** drop-down and select the volume type(s) to filter for. - -4. Click **Apply filters**. The volumes you have filtered for display. - -5. Optionally, click a specific volume to display its information page, and verify the volume type next to the **Type** field. - -6. Click **Clear filters** once you are done. - -## How to identify your snapshot type - -1. Click **Block Storage** in the **Storage** section of the side menu. - -2. Click the **Snapshots** tab. A list of your snapshots displays. - -3. Leave the **Block Storage API** filter in the drop-down or select **Instance API** to display either your snapshots managed by the Block Storage API, or the Instances API. - -4. Click the **Snapshot type** drop-down and select the snapshot type(s) to filter for. - -5. Optionally, click the icon next to a specific snapshot to display its information page, and verify the type next to the **Type** field. - -6. Click **Clear filters** once you are done. \ No newline at end of file diff --git a/pages/block-storage/how-to/identify-volumes-snapshot-type.mdx b/pages/block-storage/how-to/identify-volumes-snapshot-type.mdx new file mode 100644 index 0000000000..c18da9c70d --- /dev/null +++ b/pages/block-storage/how-to/identify-volumes-snapshot-type.mdx @@ -0,0 +1,46 @@ +--- +title: How to identify the type of a volume or a snapshot +description: Learn how to identify the type of a Block Storage volume or snapshot using the Scaleway console. +tags: identify-volume-type identify-snapshot bssd sbs volume snapshot +dates: + validation: 2025-09-25 + posted: 2025-03-24 +--- +import Requirements from '@macros/iam/requirements.mdx' +import BlockStorageMigration from '@macros/storage/block-storage-migration.mdx' + + +Scaleway Block Storage allows you to identify the type of a volume or snapshot using the Scaleway console. + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created [Block Storage volumes](/block-storage/how-to/create-a-volume/) +- Created [snapshots](/block-storage/how-to/create-a-snapshot/) + + + +## How to identify your volume type + +1. Click **Block Storage** in the **Storage** section of the side menu. A list of your volumes displays. + +2. Click the **Volume type** drop-down and select the volume type(s) to filter for. + +3. Click **Apply filters**. The volumes you have filtered for display. + +4. Optionally, click a specific volume to display its information page, and verify the volume type next to the **Type** field. + +5. Click **Clear filters** once you are done. + +## How to identify your snapshot type + +1. Click **Block Storage** in the **Storage** section of the side menu. + +2. Click the **Snapshots** tab. A list of your snapshots displays. + +3. Click the **Snapshot type** drop-down and select the snapshot type(s) to filter for. + +4. Optionally, click the icon next to a specific snapshot to display its information page, and verify the type next to the **Type** field. + +5. Click **Clear filters** once you are done. \ No newline at end of file diff --git a/pages/block-storage/how-to/migrate-volumes-snapshots-to-sbs.mdx b/pages/block-storage/how-to/migrate-volumes-snapshots-to-sbs.mdx index 3e706643cb..564bf2eb71 100644 --- a/pages/block-storage/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/pages/block-storage/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -6,7 +6,301 @@ dates: validation: 2025-06-09 posted: 2025-06-09 --- -import HowToMigrateToSbs from '@macros/compute/how-to-migrate-to-sbs.mdx' +import Requirements from '@macros/iam/requirements.mdx' - +To enhance performance and reliability, Scaleway is transitioning the management of Block Storage volumes and snapshots from Compute to Storage. + +To facilitate the transition to Scaleway's new Block Storage management, two main approaches for migrating your volumes exist, each with its unique benefits and drawbacks: + +- [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**. + +- [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.
+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 + +| Migration Method | Advantage | Drawback | +|--------------------------------|-----------------------------------------------|---------------------------------------------| +| Instance API/CLI migration | No service interruption, volume remains accessible | Data characteristics remain the same; no performance boost | +| Snapshot export/import | Full support for low latency and customizable IOPS | Requires downtime; manual snapshot handling | + +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. + + + 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). + + +## 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. + + + 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. + + +### 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. + + 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/). + + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- An [Instance](/instances/how-to/create-an-instance/) using [Block Storage volumes](/block-storage/how-to/create-a-volume/) + + + - The easiest way to migrate your Block Storage volumes and snapshots is by using the [Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) tool. + - If you encounter an error about quota limitations during the migration process, [contact our Support team](https://console.scaleway.com/support/tickets/create) for assistance. + + + + To ensure continued access to managing your volumes, you must convert your **unified volumes and snapshots** into either **local** or **Block volumes** before the **end-of-life date of June 2nd, 2025**. After this date, unified volumes and snapshots will no longer be supported by any API. + + #### Key migration deadlines: + - April 30th, 2025: + - Creation of new unified volumes via the Instance API will be disabled. + - Unified volumes will no longer be supported by the Instance API. + - June 2nd, 2025: + - Unified volumes and snapshots can no longer be managed via any API. Existing unified resources must be converted by this date to avoid loss of manageability. + + +## Migrating using the Instance API/CLI migration endpoint (Plan and Apply): + + + During migration, unified snapshots will be converted into [Block Storage](/block-storage/) snapshots and removed from Compute. If a unified snapshot is part of an image, it will be replaced by the corresponding Block Storage snapshot. + + +### Migrating an existing Block Storage volume to Scaleway Block Storage management + + + This process applies only to Block SSD (`b_ssd`) volumes. + + + + + + When you migrate a volume, the volume and any snapshots created from it will be migrated as well. + + 1. Use the following command to list your Block Storage volumes and retrieve the ID of the volume you wish to migrate: + ``` + $ scw instance volume list + ID STATE SERVER ID SERVER NAME + 369feb53-165f-437d-875e-188725df462b available + ``` + 2. Plan the volume migration using the `scw instance volume plan-migration ` command. This command returns the volume and its snapshots that will be migrated, along with a unique `ValidationKey` required to start the migration. + ``` + $ scw instance volume plan-migration 369feb53-165f-437d-875e-188725df462b + Volume.ID 369feb53-165f-437d-875e-188725df462b + Volume.Name vol-peaceful-davinci + Volume.Size 25 GB + Volume.VolumeType b_ssd + Volume.CreationDate 2 weeks ago + Volume.ModificationDate 2 weeks ago + Volume.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 + Volume.Project 4a2e00bf-5126-43ce-9b09-be943c619139 + Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c + Volume.Server.Name scw-naughty-robinson + Volume.State available + Volume.Zone fr-par-1 + Snapshots.0.ID a377afe5-a9a3-4706-b8c2-8d1c247a620f + Snapshots.0.Name image-scw-quirky-torvalds_snap_0 + Snapshots.0.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 + Snapshots.0.Project 4a2e00bf-5126-43ce-9b09-be943c619139 + Snapshots.0.VolumeType b_ssd + Snapshots.0.Size 10 GB + Snapshots.0.State available + Snapshots.0.CreationDate 2 weeks ago + Snapshots.0.ModificationDate 5 days ago + Snapshots.0.Zone fr-par-1 + Snapshots.1.ID 384799c2-c4dd-40ab-bd65-ed95cd7b4d5c + Snapshots.1.Name snap-eloquent-edison + Snapshots.1.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 + Snapshots.1.Project 4a2e00bf-5126-43ce-9b09-be943c619139 + Snapshots.1.VolumeType b_ssd + Snapshots.1.Size 10 GB + Snapshots.1.State available + Snapshots.1.CreationDate 2 weeks ago + Snapshots.1.ModificationDate 5 days ago + Snapshots.1.Zone fr-par-1 + ValidationKey 30d129ca895c4cd59f4c429e12dab300 + ``` + 3. Execute the migration using the `scw instance volume apply-migration validation-key= zone=` command. + ``` + $ scw instance volume apply-migration 369feb53-165f-437d-875e-188725df462b validation-key=30d129ca895c4cd59f4c429e12dab300 zone=fr-par-1 + ✅ Success + ``` + The volume migration is complete. You can now manage the migrated volume from the [Block Storage volumes section](https://console.scaleway.com/block-storage/volumes) in the Scaleway console. + + + + When you migrate a volume using the API, the volume and any snapshots created from the volume will be migrated. + + + 1. Plan the migration by sending a `POST` request to the Scaleway API: + + ```bash + curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/plan" \ + --header "Content-Type: application/json" \ + --header "X-Auth-Token: $SCW_SECRET_KEY" \ + --data "{ + \"volume_id\": \"$SCW_VOLUME_ID\" + }" + ``` + + This request returns the volume and its snapshots that will be migrated, along with a unique `ValidationKey` required to start the migration. + + 2. Confirm and execute the migration by sending another `POST` request: + + ```bash + curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/apply" \ + --header "Content-Type: application/json" \ + --header "X-Auth-Token: $SCW_SECRET_KEY" \ + --data "{ + \"volume_id\": \"$SCW_VOLUME_ID\", + \"validation_key\": \"$SCW_VALIDATION_KEY\" + }" + ``` + + + + + 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). + + +### Migrating an existing Block Storage snapshot to Scaleway Block Storage management + + + This process applies to Block SSD (`b_ssd`) or Unified (`unified`) snapshots. + + + + + + When you migrate a snapshot, the source volume of the snapshot and any snapshots created from this volume will also be migrated. + + 1. Use the following command to list your snapshots and retrieve the ID of the snapshot you wish to migrate: + ``` + $ scw instance snapshot list + ID NAME + a377afe5-a9a3-4706-b8c2-8d1c247a620f snap-eloquent-edison + ``` + 2. Plan the snapshot migration using the `scw instance snapshot plan-migration ` command. This command returns the source volume of the snapshot and any related snapshots that will be migrated, along with a unique `ValidationKey`. + ``` + $ scw instance snapshot plan-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f + Volume.ID 369feb53-165f-437d-875e-188725df462b + Volume.Name vol-peaceful-davinci + Volume.Size 25 GB + Volume.VolumeType b_ssd + Volume.CreationDate 2 weeks ago + Volume.ModificationDate 2 weeks ago + Volume.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 + Volume.Project 4a2e00bf-5126-43ce-9b09-be943c619139 + Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c + Volume.Server.Name scw-naughty-robinson + Volume.State available + Volume.Zone fr-par-1 + Snapshots.0.ID a377afe5-a9a3-4706-b8c2-8d1c247a620f + Snapshots.0.Name image-scw-quirky-torvalds_snap_0 + Snapshots.0.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 + Snapshots.0.Project 4a2e00bf-5126-43ce-9b09-be943c619139 + Snapshots.0.VolumeType b_ssd + Snapshots.0.Size 10 GB + Snapshots.0.State available + Snapshots.0.CreationDate 2 weeks ago + Snapshots.0.ModificationDate 5 days ago + Snapshots.0.Zone fr-par-1 + Snapshots.1.ID 384799c2-c4dd-40ab-bd65-ed95cd7b4d5c + Snapshots.1.Name snap-eloquent-edison + Snapshots.1.Organization 4a2e00bf-5126-43ce-9b09-be943c619139 + Snapshots.1.Project 4a2e00bf-5126-43ce-9b09-be943c619139 + Snapshots.1.VolumeType b_ssd + Snapshots.1.Size 10 GB + Snapshots.1.State available + Snapshots.1.CreationDate 2 weeks ago + Snapshots.1.ModificationDate 5 days ago + Snapshots.1.Zone fr-par-1 + ValidationKey 30d129ca895c4cd59f4c429e12dab300 + ``` + 3. Execute the migration using the `scw instance snapshot apply-migration validation-key= zone=` command. + ``` + $ scw instance snapshot apply-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f validation-key=30d129ca895c4cd59f4c429e12dab300 zone=fr-par-1 + ✅ Success. + ``` + The snapshot migration is complete. You can now manage the migrated snapshot from the [Block Storage Snapshot section](https://console.scaleway.com/block-storage/volumes) in the Scaleway console. + + + + When you migrate a snapshot using the API, the source volume of the snapshot and any snapshots created from this volume will also be migrated. + + + 1. Plan the migration by sending a `POST` request to the Scaleway API: + + ```bash + curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/plan" \ + --header "Content-Type: application/json" \ + --header "X-Auth-Token: $SCW_SECRET_KEY" \ + --data "{ + \"snapshot_id\": \"$SCW_SNAPSHOT_ID\" + }" + ``` + + This request returns the source volume and any related snapshots that will be migrated, along with a unique `ValidationKey`. + + 2. Confirm and execute the migration by sending another `POST` request: + + ```bash + curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/apply" \ + --header "Content-Type: application/json" \ + --header "X-Auth-Token: $SCW_SECRET_KEY" \ + --data "{ + \"snapshot_id\": \"$SCW_SNAPSHOT_ID\", + \"validation_key\": \"$SCW_VALIDATION_KEY\" + }" + ``` + + + + + 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). + + +## 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. + + + 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. + + +Follow the procedure below: + +1. [Create a snapshot of your Block Storage legacy volume](/block-storage/how-to/create-a-snapshot/). +2. [Export the snapshot](/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 + +To learn more about managing your migrated Block Storage volumes and snapshots from the Scaleway console, refer to the [Block Storage Quickstart Guide](/block-storage/quickstart/). Additionally, you can explore advanced features using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/). + +If you encounter any issues during migration, contact [Scaleway's Support team](https://console.scaleway.com/support/tickets) for assistance. diff --git a/pages/block-storage/reference-content/advantages-migrating-to-sbs.mdx b/pages/block-storage/reference-content/advantages-migrating-to-sbs.mdx deleted file mode 100644 index d170f8faa6..0000000000 --- a/pages/block-storage/reference-content/advantages-migrating-to-sbs.mdx +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: Advantages of migrating from the Instance API to the Block Storage API for managing block volumes and snapshots -description: 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-09-17 - posted: 2025-01-14 ---- -import BlockStorageNoMigrationForK8s from '@macros/storage/block-storage-no-migration-for-k8s.mdx' - -import BlockStorageVolumeTypes from '@macros/block-storage/block-storage-volume-types.mdx' - -This page explains why **Instance users** should migrate from the Instance API to the Block Storage API to create and manage block volumes and snapshots. - - - -## Transitioning from the Instance API to the Block Storage API for volume and snapshot management - -Scaleway is transitioning the management of all Block Storage volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/). - -This change streamlines how storage resources are managed by consolidating them under the Block Storage API, providing enhanced management features and clearer storage class distinctions. - -Local volumes will remain exclusively supported by the Instance API. - -## What is required from you in the context of the migration? - -If you have created volumes and snapshots via the Instance API, you **must transition to the Block Storage API** to align with the latest management practices. - -This entails [migrating your existing volumes and snapshots to the Block Storage API](/instances/how-to/migrate-volumes-snapshots-to-sbs/), and **switching to using only the Block Storage API for Block Storage volumes and snapshots creation and management**. - - - Unified volume creation and management will no longer be available via the Block Storage API and will no longer be supported by the Instance API at the end of the migration. For this reason, it is also necessary to convert your existing unified volumes and snapshots to either local or block volumes. - - -## What will happen at the end of the migration? - -From **April 30th 2025, it will no longer be possible to create Block volumes through the Instance API**. - -From **June 2nd, 2025, all block volumes and snapshots that you have not migrated manually will be automatically switched behind the Block Storage API**. - -What's more, creating and managing block volumes and snapshots through the Instance API will no longer be possible. The Instance API will only allow you to create and manage local volumes and snapshots. - -Creating and managing block volumes and snapshots will **only be available via the Block Storage API**. - -## Differences between the Instance API and the Block Storage API - -The key differences between the Instance API and the Block Storage API lie in the storage classes they manage, rather than just the APIs themselves. The [Block Storage API](https://www.scaleway.com/en/developers/api/block/) is the only API to use to create and manage all types of volumes, including high performance ones. - -### Storage classes - -The Instance API handles only **BSSD (Block SSD)** volumes. -The Block Storage API supports a broader range of storage classes, including: - - - **BSSD volumes** - - **Scaleway Block Storage (SBS) 5K IOPS volumes** - - **Scaleway Block Storage (SBS) 15K IOPS volumes** - -### Underlying hardware - -**BSSD volumes** (managed by both APIs) are built on **older-generation SSDs**, offering reliable performance but with limitations in speed and latency. - -**Scaleway Block Storage 5K and 15K volumes** (managed only by the Block Storage API) are powered by **modern NVMe (Non-Volatile Memory Express) disks**. They are optimized for **low-latency and high-speed operations**. - -### Performance and latency - -**BSSD volumes**: - - - **Performance**: Limited IOPS and slower data processing speed due to older SSD technology. - - **Latency**: Higher latency, less suitable for applications requiring rapid data retrieval. - -**Scaleway Block Storage 5K and 15K volumes**: - - - **Performance**: Enhanced performance with up to 5K IOPS (SBS 5K) and 15K IOPS (SBS 15K). - - **Latency**: Lower latency, ideal for workloads demanding rapid and reliable data access. - -### Comparison of Block Storage volume types - - - -You can attach a maximum of 16 volumes (including the mandatory boot volume) to a single Instance. - - - Refer to the [dedicated documentation](/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. - - -## Why transition to the Block Storage API? - -By transitioning to the Block Storage API, you align with Scaleway's consolidated storage management approach and gain access to advanced storage features and flexibility. While migrating to the Block Storage API does not inherently change the performance of BSSD volumes, you benefit from: - -- **Unified management**: Simplified volume and snapshot management through a dedicated API. -- **Access to advanced storage classes**: You can create new Scaleway Block Storage 5K or 15K volumes for workloads needing higher performance and lower latency. -- **Ongoing support**: Enhanced support and updates tailored for Block Storage API-managed resources. - -## Impact on volume names in virtual machines - -When transitioning to the Block Storage API, you may notice changes in how volumes are identified in your virtual machines (VMs). For more details on how devices are named and identified, refer to [our documentation on identifying devices on a Scaleway Instance](/instances/reference-content/identify-devices/). - -## 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](/instances/how-to/migrate-volumes-snapshots-to-sbs/). - -- To identify which API manages your volumes and snapshots, refer to the [dedicated documentation](/block-storage/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](/block-storage/faq/#how-can-i-convert-a-block-storage-legacy-volume-into-a-block-storage-low-latency-volume). - ---- - -This transition ensures Scaleway can continue to provide robust, scalable, and high-performance storage solutions tailored to your needs. If you have questions or need assistance, [contact our Support team](https://console.scaleway.com/support/tickets/create). diff --git a/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx b/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx index 5b60f2e083..c4ec595bd5 100644 --- a/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx +++ b/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx @@ -13,6 +13,117 @@ categories: - compute --- -import InstancesBLockBandwidthOverview from '@macros/compute/instances-block-bandwidth-overview.mdx' +This guide provides a complete overview of internet and Block Storage bandwidth for Scaleway Instances. +Understanding these specifications is crucial for optimizing your infrastructure for performance and compatibility. - \ No newline at end of file +### Why bandwidth matters + +Bandwidth impacts how your applications perform and interact with other systems. +- **Internet bandwidth**: Affects how fast your Instance can send or receive data over the internet. +- **Block bandwidth**: Determines the read/write speed to Block Storage, essential for storage-heavy workloads like databases and analytics. + + + Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. + + + + To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth. + + +## COPARM1 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| COPARM1-2C-8G | 200 Mbit/s | 80 MiB/s | +| COPARM1-4C-16G | 400 Mbit/s | 160 MiB/s | +| COPARM1-8C-32G | 800 Mbit/s | 320 MiB/s | +| COPARM1-16C-64G | 1.6 Gbit/s | 640 MiB/s | +| COPARM1-32C-128G | 3.2 Gbit/s | 1.25 GiB/s | + +## DEV1 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| DEV1-S | 200 Mbit/s | 100 MiB/s | +| DEV1-M | 300 Mbit/s | 150 MiB/s | +| DEV1-L | 400 Mbit/s | 200 MiB/s | +| DEV1-XL | 500 Mbit/s | 250 MiB/s | + +## GP1 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| GP1-XS | 500 Mbit/s | 300 MiB/s | +| GP1-S | 800 Mbit/s | 500 MiB/s | +| GP1-M | 1.5 Gbit/s | 800 MiB/s | +| GP1-L | 5 Gbit/s | 1 GiB/s | +| GP1-XL | 10 Gbit/s | 2 GiB/s | + +## PLAY2 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| PLAY2-PICO | 100 Mbit/s | 40 MiB/s | +| PLAY2-NANO | 200 Mbit/s | 80 MiB/s | +| PLAY2-MICRO | 400 Mbit/s | 160 MiB/s | + +## PRO2 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| PRO2-XXS | 350 Mbit/s | 125 MiB/s | +| PRO2-XS | 700 Mbit/s | 250 MiB/s | +| PRO2-S | 1.5 Gbit/s | 500 MiB/s | +| PRO2-M | 3 Gbit/s | 1 GiB/s | +| PRO2-L | 6 Gbit/s | 2 GiB/s | + +## POP2 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-2C-8G | 400 Mbit/s | 400 MiB/s | +| POP2-4C-16G | 800 Mbit/s | 800 MiB/s | +| POP2-8C-32G | 1.6 Gbit/s | 1.56 GiB/s | +| POP2-16C-64G | 3.2 Gbit/s | 3.12 GiB/s | +| POP2-32C-128G | 6.4 Gbit/s | 5.5 GiB/s | +| POP2-64C-256G | 12.8 Gbit/s | 5.5 GiB/s | + +## POP2-WIN range (Windows Server OS) + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-2C-8G-WIN | 400 Mbit/s | 400 MiB/s | +| POP2-4C-16G-WIN | 800 Mbit/s | 800 MiB/s | +| POP2-8C-32G-WIN | 1.6 Gbit/s | 1.56 GiB/s | +| POP2-16C-64G-WIN | 3.2 Gbit/s | 3.12 GiB/s | +| POP2-32C-128G-WIN | 6.4 Gbit/s | 5.5 GiB/s | + +## POP2-HC range (High Compute) + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-HC-2C-4G | 400 Mbit/s | 400 MiB/s | +| POP2-HC-4C-8G | 800 Mbit/s | 800 MiB/s | +| POP2-HC-8C-16G | 1.6 Gbit/s | 1.56 GiB/s | +| POP2-HC-16C-32G | 3.2 Gbit/s | 3.12 GiB/s | +| POP2-HC-32C-64G | 6.4 Gbit/s | 5.5 GiB/s | +| POP2-HC-64C-128G | 12.8 Gbit/s | 5.5 GiB/s | + +## POP2-HM range (High Memory) + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-HM-2C-16G | 400 Mbit/s | 400 MiB/s | +| POP2-HM-4C-32G | 800 Mbit/s | 800 MiB/s | +| POP2-HM-8C-64G | 1.6 Gbit/s | 1.56 GiB/s | +| POP2-HM-16C-128G | 3.2 Gbit/s | 3.12 GiB/s | +| POP2-HM-32C-256G | 6.4 Gbit/s | 5.5 GiB/s | +| POP2-HM-64C-512G | 12.8 Gbit/s | 5.5 GiB/s | + +## POP2-HN range (High Network) + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-HN-3 | 3 Gbit/s | 400 MiB/s | +| POP2-HN-5 | 5 Gbit/s | 800 MiB/s | +| POP2-HN-10 | 10 Gbit/s | 800 MiB/s | \ No newline at end of file diff --git a/pages/block-storage/troubleshooting/index.mdx b/pages/block-storage/troubleshooting/index.mdx index 22ab08767e..b4af4c76f9 100644 --- a/pages/block-storage/troubleshooting/index.mdx +++ b/pages/block-storage/troubleshooting/index.mdx @@ -25,10 +25,4 @@ productIcon: BlockStorageProductIcon url="/block-storage/reference-content/differences-between-5kiops-volumes/" label="See more" /> - diff --git a/pages/instances/reference-content/instances-bandwidth-overview.mdx b/pages/instances/reference-content/instances-bandwidth-overview.mdx index 59db803ce4..f2379a0a26 100644 --- a/pages/instances/reference-content/instances-bandwidth-overview.mdx +++ b/pages/instances/reference-content/instances-bandwidth-overview.mdx @@ -7,7 +7,117 @@ dates: posted: 2024-11-19 --- -import InstancesBLockBandwidthOverview from '@macros/compute/instances-block-bandwidth-overview.mdx' +This guide provides a complete overview of internet and Block Storage bandwidth for Scaleway Instances. +Understanding these specifications is crucial for optimizing your infrastructure for performance and compatibility. - +### Why bandwidth matters +Bandwidth impacts how your applications perform and interact with other systems. +- **Internet bandwidth**: Affects how fast your Instance can send or receive data over the internet. +- **Block bandwidth**: Determines the read/write speed to Block Storage, essential for storage-heavy workloads like databases and analytics. + + + Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. + + + + To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth. + + +## COPARM1 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| COPARM1-2C-8G | 200 Mbit/s | 80 MiB/s | +| COPARM1-4C-16G | 400 Mbit/s | 160 MiB/s | +| COPARM1-8C-32G | 800 Mbit/s | 320 MiB/s | +| COPARM1-16C-64G | 1.6 Gbit/s | 640 MiB/s | +| COPARM1-32C-128G | 3.2 Gbit/s | 1.25 GiB/s | + +## DEV1 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| DEV1-S | 200 Mbit/s | 100 MiB/s | +| DEV1-M | 300 Mbit/s | 150 MiB/s | +| DEV1-L | 400 Mbit/s | 200 MiB/s | +| DEV1-XL | 500 Mbit/s | 250 MiB/s | + +## GP1 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| GP1-XS | 500 Mbit/s | 300 MiB/s | +| GP1-S | 800 Mbit/s | 500 MiB/s | +| GP1-M | 1.5 Gbit/s | 800 MiB/s | +| GP1-L | 5 Gbit/s | 1 GiB/s | +| GP1-XL | 10 Gbit/s | 2 GiB/s | + +## PLAY2 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| PLAY2-PICO | 100 Mbit/s | 40 MiB/s | +| PLAY2-NANO | 200 Mbit/s | 80 MiB/s | +| PLAY2-MICRO | 400 Mbit/s | 160 MiB/s | + +## PRO2 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| PRO2-XXS | 350 Mbit/s | 125 MiB/s | +| PRO2-XS | 700 Mbit/s | 250 MiB/s | +| PRO2-S | 1.5 Gbit/s | 500 MiB/s | +| PRO2-M | 3 Gbit/s | 1 GiB/s | +| PRO2-L | 6 Gbit/s | 2 GiB/s | + +## POP2 range + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-2C-8G | 400 Mbit/s | 400 MiB/s | +| POP2-4C-16G | 800 Mbit/s | 800 MiB/s | +| POP2-8C-32G | 1.6 Gbit/s | 1.56 GiB/s | +| POP2-16C-64G | 3.2 Gbit/s | 3.12 GiB/s | +| POP2-32C-128G | 6.4 Gbit/s | 5.5 GiB/s | +| POP2-64C-256G | 12.8 Gbit/s | 5.5 GiB/s | + +## POP2-WIN range (Windows Server OS) + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-2C-8G-WIN | 400 Mbit/s | 400 MiB/s | +| POP2-4C-16G-WIN | 800 Mbit/s | 800 MiB/s | +| POP2-8C-32G-WIN | 1.6 Gbit/s | 1.56 GiB/s | +| POP2-16C-64G-WIN | 3.2 Gbit/s | 3.12 GiB/s | +| POP2-32C-128G-WIN | 6.4 Gbit/s | 5.5 GiB/s | + +## POP2-HC range (High Compute) + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-HC-2C-4G | 400 Mbit/s | 400 MiB/s | +| POP2-HC-4C-8G | 800 Mbit/s | 800 MiB/s | +| POP2-HC-8C-16G | 1.6 Gbit/s | 1.56 GiB/s | +| POP2-HC-16C-32G | 3.2 Gbit/s | 3.12 GiB/s | +| POP2-HC-32C-64G | 6.4 Gbit/s | 5.5 GiB/s | +| POP2-HC-64C-128G | 12.8 Gbit/s | 5.5 GiB/s | + +## POP2-HM range (High Memory) + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-HM-2C-16G | 400 Mbit/s | 400 MiB/s | +| POP2-HM-4C-32G | 800 Mbit/s | 800 MiB/s | +| POP2-HM-8C-64G | 1.6 Gbit/s | 1.56 GiB/s | +| POP2-HM-16C-128G | 3.2 Gbit/s | 3.12 GiB/s | +| POP2-HM-32C-256G | 6.4 Gbit/s | 5.5 GiB/s | +| POP2-HM-64C-512G | 12.8 Gbit/s | 5.5 GiB/s | + +## POP2-HN range (High Network) + +| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | +|-----------------------|-------------------------|---------------------| +| POP2-HN-3 | 3 Gbit/s | 400 MiB/s | +| POP2-HN-5 | 5 Gbit/s | 800 MiB/s | +| POP2-HN-10 | 10 Gbit/s | 800 MiB/s | \ No newline at end of file