Skip to content

Commit babe876

Browse files
committed
feat(ins): add faq for migration
1 parent 175db45 commit babe876

File tree

1 file changed

+69
-0
lines changed

1 file changed

+69
-0
lines changed

faq/blockstorage-migration.mdx

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
meta:
3+
title: Block Storage Migration FAQ
4+
description: Explore Scaleway Block Storage with our comprehensive FAQ covering performance, persistence, and more. Learn how Block Storage compares to Local Storage and its compatibility with Scaleway resources.
5+
content:
6+
h1: Block Storage Migration
7+
dates:
8+
validation: 2025-01-07
9+
category: storage
10+
productIcon: BlockStorageProductIcon
11+
---
12+
13+
Scaleway is transitioning the management of Block Storage volumes and snapshots from the **Instance API** to the **Block Storage API**. This migration enhances performance, scalability, and provides access to new features. Below are the most frequently asked questions regarding this transition.
14+
15+
## What is changing with the migration?
16+
17+
The management of Block Storage **volumes and snapshots** is moving from the Instance API to the Block Storage API. After the migration:
18+
19+
* All your **volumes and snapshots** will be fully managed through the Block Storage API.
20+
* **New features** and improvements will be available for your volumes, such as resizing and enhanced performance.
21+
* The existing **Instance API** will no longer handle volume and snapshot operations.
22+
23+
## How do I migrate my existing volumes or snapshots?
24+
25+
For a step-by-step guide, visit [How to migrate volumes and snapshots](/instances/how-to/migrate-volumes-snapshots-to-sbs/).
26+
27+
## What happens if I do not migrate my unified volumes or snapshots?
28+
29+
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.
30+
31+
### Key migration deadlines:
32+
33+
* April 30th, 2025:
34+
+ Creation of new unified volumes via the Instance API will be disabled.
35+
+ Unified volumes will no longer be supported by the Instance API.
36+
* June 2nd, 2025:
37+
+ 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.
38+
39+
## Will there be any downtime during the migration?
40+
41+
There will be no downtime if you migrate your existing volumes to the Block Storage API, however only the volume's representation is migrated to the SBS API; the data itself does not move.
42+
43+
<Message type="note">
44+
This means the migrated volume will not benefit from low latency or higher IOPS, as it **retains the original `b_ssd` characteristics**.
45+
</Message>
46+
47+
To convert an existing volume to the new Block Storage Low Latency, you can use the [snapshot export/import feature](/instances/how-to/migrate-volumes-snapshots-to-sbs/#migrating-using-the-snapshot-exportimport-features), however this manual process may result in downtime during the volume replacement.
48+
49+
## Will migration affect my billing?
50+
51+
The migration itself is **free**, but after migrating, your volumes will be billed according to the [Block Storage pricing](https://www.scaleway.com/en/docs/block-storage/pricing/).
52+
53+
## How can I convert a Block Storage legacy volume into a Block Storage Low Latency volume?
54+
55+
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.
56+
57+
<Message type="important">
58+
The process below requires manual intervention and **does not preserve the original volume's ID**.
59+
</Message>
60+
61+
While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround.
62+
63+
1. [Create a snapshot of your Block Storage legacy volume](/instances/how-to/create-a-snapshot/).
64+
2. [Export the snapshot](/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots).
65+
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).
66+
67+
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.
68+
69+
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.

0 commit comments

Comments
 (0)