Skip to content

Commit 80dda56

Browse files
committed
feat(ins): fix anchor
1 parent a2820ae commit 80dda56

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ To enhance performance and reliability, Scaleway is transitioning the management
1717

1818
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:
1919

20-
- [Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-migration-endpoint-of-the-instances-api-cli):
20+
- [Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-instance-apicli-migration-endpoint-plan-and-apply):
2121
- **Advantage:** Migration can occur without service interruption, as the volume remains attached to the running Instance and fully accessible.
2222
- **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.
2323

@@ -253,7 +253,7 @@ Alternatively, you can use the [snapshot export/import feature](/compute/instanc
253253
</TabsTab>
254254
</Tabs>
255255

256-
## Migrating using the snapshot import/export features
256+
## Migrating using the snapshot export/import features
257257

258258
To convert your unified volumes and snapshots you can use the snapshot export/import feature as an alternative solution to transition a Block Storage legacy volume into a Block Storage Low Latency volume.
259259

0 commit comments

Comments
 (0)