By clicking or navigating this website site, you agree to allow our collection of information on Scaleway to offer you an optimal user experience and to keep track of statistics through cookies. Learn more about our Cookie Policy.

How to migrate from one instance to another

Overview

The Scaleway platform makes it very easy to upscale your node to a more powerful one when your requirements grow. In this tutorial we will upgrade a DEV1-S instance to a GP1-XS instance using the backup feature.

Migrating from the management console

Backing up the Instance

1 . Enter the instance information page by clicking on Instances followed by clicking on …, then More Info next to the instance that shall be migrated:

2 . On the instance information page, scroll down to the backup section. Click on Backup Instance:

Important: On virtual cloud instances, hot backups are available. BareMetal cloud instances must be archived before launching the backup process.

3 . Enter a name for the new backup of the instance and click on Backup instance:

Creating a new Instance from the Backup

1 . Click on the Backups & Images tab to view the list of backups.

2 . Click on …, followed by clicking on Create instance from backup:

3 . Choose the desired region and instance type as well as optional values like tags to organize instances:

4 . Scroll down to Configure Advanced Options and untick the box Flexible IP. This creates the new instance without allocated flexible IP.

5 . Click on Create a new instance to launch the new server.

Moving the flexible IP to the new instance

1 . Click on the Flexible IPs tab.

2 . Click on … next to the IP to detach. In the pop-up menu click on Detach to detach the IP.

3 . Once the IP has been detached, click on … > Change Instance:

4 . Select the new instance in the drop down list and click on Attach this flexible IP

The new instance is now reachable via the previous instances flexible IP.

Migrating via the API

It is possible to automatize the migration process by using the API.

To migrate a server via the API, the instance ID, a valid API token and the users organization key are required.

1 . Start by making a backup of your instance. Replace <REGION> with the region of your server, either fr-par-1 for instances located in Paris, France or nl-ams-1 for instances located in Amsterdam, The Netherlands.