Skip to content

Commit ba7a83d

Browse files
bene2k1bene2k1
committed
fix(ins): migration sbs
1 parent 0e76499 commit ba7a83d

File tree

1 file changed

+56
-23
lines changed

1 file changed

+56
-23
lines changed

‎compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx‎

Lines changed: 56 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -7,14 +7,15 @@ content:
77
paragraph: This guide provides step-by-step instructions to help you migrate your existing Block Storage volumes and snapshots to Scaleway's new Block Storage management system.
88
tags: instance snapshot volume b_ssd sbs
99
dates:
10-
validation: 2024-10-10
10+
validation: 2024-11-15
1111
posted: 2024-08-07
1212
categories:
1313
- compute
1414
---
1515

16-
Scaleway is transitioning the management of Block Storage volumes and snapshots from compute teams to storage teams to enhance performance and reliability.
17-
While the characteristics of your migrated volumes and snapshots will remain unchanged, Scaleway's new storage management system will now manage them.
16+
Scaleway is transitioning the management of Block Storage volumes and snapshots from Compute teams to Storage teams to enhance performance and reliability.
17+
The characteristics of your migrated volumes and snapshots will remain unchanged, it is seamless even for a volume attached to a running instance, these resources will be managed from Compute to [Storage](https://www.scaleway.com/en/docs/storage/block/quickstart/).
18+
The unified snapshot migration will result in a snapshot in Block Storage and the deletion of the unified snapshot in Compute. If the unified snapshot is part of an image, it's replaced by the snapshot of Block Storage.
1819
This guide provides the steps needed to migrate your volumes and snapshots using either the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool (recommended) or via the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-volumes-migrate-a-volume-andor-snapshots-to-sbs-scaleway-block-storage).
1920

2021
<Message type="tip">
@@ -43,22 +44,42 @@ This guide provides the steps needed to migrate your volumes and snapshots using
4344
ID STATE SERVER ID SERVER NAME
4445
369feb53-165f-437d-875e-188725df462b available
4546
```
46-
2. Plan the volume migration with the `scw instance volume plan-migration <VOLUME_ID>` command. This command provides the state of the volume and a unique `ValidationKey`, which is needed to start the migration.
47+
2. Plan the volume migration with the `scw instance volume plan-migration <VOLUME_ID>` command. It returns the volume and its snapshots that will be migrated. It also returns an unique `ValidationKey`, which is needed to start the migration.
4748
```
4849
$ scw instance volume plan-migration 369feb53-165f-437d-875e-188725df462b
49-
Volume.ID 369feb53-165f-437d-875e-188725df462b
50-
Volume.Name vol-peaceful-davinci
51-
Volume.Size 25 GB
52-
Volume.VolumeType b_ssd
53-
Volume.CreationDate 3 minutes ago
54-
Volume.ModificationDate 3 minutes ago
55-
Volume.Organization 27e53d15-cc73-440e-956c-40560076e3d7
56-
Volume.Project 27e53d15-cc73-440e-956c-40560076e3d7
57-
Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c
58-
Volume.Server.Name scw-naughty-robinson
59-
Volume.State available
60-
Volume.Zone fr-par-1
61-
ValidationKey 30d129ca895c4cd59f4c429e12dab300
50+
Volume.ID 369feb53-165f-437d-875e-188725df462b
51+
Volume.Name vol-peaceful-davinci
52+
Volume.Size 25 GB
53+
Volume.VolumeType b_ssd
54+
Volume.CreationDate 2 weeks ago
55+
Volume.ModificationDate 2 weeks ago
56+
Volume.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
57+
Volume.Project 4a2e00bf-5126-43ce-9b09-be943c619139
58+
Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c
59+
Volume.Server.Name scw-naughty-robinson
60+
Volume.State available
61+
Volume.Zone fr-par-1
62+
Snapshots.0.ID a377afe5-a9a3-4706-b8c2-8d1c247a620f
63+
Snapshots.0.Name image-scw-quirky-torvalds_snap_0
64+
Snapshots.0.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
65+
Snapshots.0.Project 4a2e00bf-5126-43ce-9b09-be943c619139
66+
Snapshots.0.VolumeType b_ssd
67+
Snapshots.0.Size 10 GB
68+
Snapshots.0.State available
69+
Snapshots.0.CreationDate 2 weeks ago
70+
Snapshots.0.ModificationDate 5 days ago
71+
Snapshots.0.Zone fr-par-1
72+
Snapshots.1.ID 384799c2-c4dd-40ab-bd65-ed95cd7b4d5c
73+
Snapshots.1.Name snap-eloquent-edison
74+
Snapshots.1.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
75+
Snapshots.1.Project 4a2e00bf-5126-43ce-9b09-be943c619139
76+
Snapshots.1.VolumeType b_ssd
77+
Snapshots.1.Size 10 GB
78+
Snapshots.1.State available
79+
Snapshots.1.CreationDate 2 weeks ago
80+
Snapshots.1.ModificationDate 5 days ago
81+
Snapshots.1.Zone fr-par-1
82+
ValidationKey 30d129ca895c4cd59f4c429e12dab300
6283
```
6384
3. Execute the migration using the `scw instance volume apply-migration <VOLUME_ID> validation-key=<VALIDATION_KEY> zone=<VOLUME_ZONE>` command.
6485
```
@@ -84,7 +105,7 @@ This guide provides the steps needed to migrate your volumes and snapshots using
84105
}"
85106
```
86107

87-
The response includes the volume and any snapshots created from the volume that will be migrated. It also returns a `validation_key`.
108+
It returns the volume and its snapshots that will be migrated. It also returns an unique `ValidationKey`, which is needed to start the migration.
88109

89110
2. Confirm the migration by using the following `curl` command:
90111

@@ -117,9 +138,21 @@ This guide provides the steps needed to migrate your volumes and snapshots using
117138
ID NAME
118139
a377afe5-a9a3-4706-b8c2-8d1c247a620f snap-eloquent-edison
119140
```
120-
2. Plan the migration with the `scw instance snapshot plan-migration <SNAPSHOT_ID>` command. This command returns the state of the snapshot and a unique `ValidationKey`, which is necessary to start the migration.
141+
2. Plan the migration with the `scw instance snapshot plan-migration <SNAPSHOT_ID>` command. It returns the source volume of the snapshot and the volume snapshots that will be migrated. It also returns an unique `ValidationKey`, which is needed to start the migration.
121142
```
122143
$ scw instance snapshot plan-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f
144+
Volume.ID 369feb53-165f-437d-875e-188725df462b
145+
Volume.Name vol-peaceful-davinci
146+
Volume.Size 25 GB
147+
Volume.VolumeType b_ssd
148+
Volume.CreationDate 2 weeks ago
149+
Volume.ModificationDate 2 weeks ago
150+
Volume.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
151+
Volume.Project 4a2e00bf-5126-43ce-9b09-be943c619139
152+
Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c
153+
Volume.Server.Name scw-naughty-robinson
154+
Volume.State available
155+
Volume.Zone fr-par-1
123156
Snapshots.0.ID a377afe5-a9a3-4706-b8c2-8d1c247a620f
124157
Snapshots.0.Name image-scw-quirky-torvalds_snap_0
125158
Snapshots.0.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
@@ -140,11 +173,11 @@ This guide provides the steps needed to migrate your volumes and snapshots using
140173
Snapshots.1.CreationDate 2 weeks ago
141174
Snapshots.1.ModificationDate 5 days ago
142175
Snapshots.1.Zone fr-par-1
143-
ValidationKey b36f7bcc21d344d783d4cbb27536bfad
176+
ValidationKey 30d129ca895c4cd59f4c429e12dab300
144177
```
145178
3. Execute the migration using the `scw instance snapshot apply-migration <SNAPSHOT_ID> validation-key=<VALIDATION_KEY> zone=<SNAPSHOT_ZONE>` command.
146179
```
147-
$ scw instance snapshot apply-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f validation-key=b36f7bcc21d344d783d4cbb27536bfad zone=fr-par-1
180+
$ scw instance snapshot apply-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f validation-key=30d129ca895c4cd59f4c429e12dab300 zone=fr-par-1
148181
✅ Success.
149182
```
150183
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.
@@ -165,7 +198,7 @@ This guide provides the steps needed to migrate your volumes and snapshots using
165198
}"
166199
```
167200

168-
The response includes the source volume of the snapshot and any snapshots created from this volume, including the `snapshot_id` provided by the user. It also returns a `validation_key`.
201+
It returns the source volume of the snapshot and the volume snapshots that will be migrated. It also returns an unique `ValidationKey`, which is needed to start the migration.
169202

170203
2. Confirm the migration using the following `curl` command:
171204

@@ -183,4 +216,4 @@ This guide provides the steps needed to migrate your volumes and snapshots using
183216

184217
## Going further
185218

186-
To learn more about managing your migrated Block Storage volumes from the Scaleway console, refer to the [Block Storage - Console documentation](/storage/block/quickstart/). Additionally, you can manage your Block Storage volumes using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/).
219+
To learn more about managing your migrated Block Storage volumes from the Scaleway console, refer to the [Block Storage - Console documentation](/storage/block/quickstart/). Additionally, you can manage your Block Storage volumes using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/).

0 commit comments

Comments
 (0)