How to migrate existing volumes and snapshots to Scaleway's new Block Storage management

Reviewed on 15 November 2024 • Published on 07 August 2024

To enhance performance and reliability, Scaleway is transitioning the management of Block Storage volumes and snapshots from Compute to Storage.

The migration process ensures that the characteristics of your volumes and snapshots remain unchanged, even for volumes attached to running Instances.

After migration, these resources will be managed under Storage instead of Compute.

During migration, unified snapshots will be converted into Block Storage Low Latency snapshots and removed from Compute. If a unified snapshot is part of an image, it will be replaced by the corresponding Block Storage Low Latency snapshot.

This guide offers step-by-step instructions to migrate your volumes and snapshots using either the Scaleway Command Line Interface (CLI) tool (recommended) or the Instances API.

Tip

The easiest way to migrate your Block Storage volumes and snapshots is by using the Scaleway Command Line Interface (CLI) tool.

Before you start

To complete the actions presented below, you must have:

A Scaleway account logged into the console
An Instance using Block Storage volumes

Migrating an existing Block Storage volume to Scaleway Block Storage management

Important

This process applies only to Block SSD (b_ssd) volumes.

Note

When you migrate a volume, the volume and any snapshots created from it will be migrated as well.

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

Plan the volume migration using the scw instance volume plan-migration <VOLUME_ID> 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

Execute the migration using the scw instance volume apply-migration <VOLUME_ID> validation-key=<VALIDATION_KEY> zone=<VOLUME_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 in the Scaleway console.

Note

When you migrate a volume using the API, the volume and any snapshots created from the volume will be migrated.

Plan the migration by sending a POST request to the Scaleway API:

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.

Confirm and execute the migration by sending another POST request:

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\"
}"

Migrating an existing Block Storage snapshot to Scaleway Block Storage management

Important

This process applies to Block SSD (b_ssd) or Unified (unified) snapshots.

Note

When you migrate a snapshot, the source volume of the snapshot and any snapshots created from this volume will also be migrated.

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

Plan the snapshot migration using the scw instance snapshot plan-migration <SNAPSHOT_ID> 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

Execute the migration using the scw instance snapshot apply-migration <SNAPSHOT_ID> validation-key=<VALIDATION_KEY> zone=<SNAPSHOT_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 in the Scaleway console.

Note

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.

Plan the migration by sending a POST request to the Scaleway API:

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.

Confirm and execute the migration by sending another POST request:

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\"
}"

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. Additionally, you can explore advanced features using the Scaleway Block Storage API.

If you encounter any issues during migration, contact Scaleway’s support team for assistance.