You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,12 @@ To facilitate the transition to Scaleway's new Block Storage management, two mai
19
19
20
20
-[Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-instance-apicli-migration-endpoint-plan-and-apply):
21
21
-**Advantage:** Migration can occur without service interruption, as the volume remains attached to the running Instance and fully accessible.
22
-
-**Drawback:** Only the volume's representation is migrated to the SBS API; the data itself doesn't move. This means the migrated volume will not benefit from low latency or higher IOPS, as it retains the original `b_ssd` characteristics.
22
+
-**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.
23
23
24
24
-[Using the snapshot export/import features](#migrating-using-the-snapshot-exportimport-features):
25
25
-**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.
26
-
-**Drawback:** A snapshot must be manually created, exported, and then imported and attached to the Instance which may require downtime.
27
-
26
+
-**Drawback:** A snapshot must be manually created, exported, and imported. After importing, the snapshot must be converted into a volume, which then needs to be attached to the instance. This process may require downtime.
27
+
28
28
Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/storage/block/quickstart/) instead of Compute.
29
29
30
30
## Comparison of migration methods
@@ -263,7 +263,7 @@ To convert your unified volumes and snapshots you can use the snapshot export/im
263
263
264
264
Steps:
265
265
1.[Export a snapshot of your unified volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots).
266
-
2.[Import the snapshot into a new local or Block volume](/compute/instances/api-cli/snapshot-import-export-feature/#importing-snapshots).
266
+
2.[Import the snapshot into a new local or Block volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket).
0 commit comments