Skip to content

Feat migration between region #8160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 5 commits into
base: develop
Choose a base branch
from
Draft

Feat migration between region #8160

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a0d4bbd
feat(instance): new guide about migration between regions
OvhValentin Jul 11, 2025
8977148
update
OvhValentin Jul 11, 2025
3bea97e
add primary
OvhValentin Jul 17, 2025
0cf2843
update
OvhValentin Oct 6, 2025
b6953a7
add api
OvhValentin Oct 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions pages/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -692,6 +692,7 @@
+ [Resizing the file system in FreeBSD 12](public_cloud/compute/resize_freebsd_file_system_after_install)
+ [Forensics: How to deal with Public Cloud instances](public_cloud/compute/forensics)
+ [Local Zone VPN-as-a-Service (VPNaaS) with Tailscale Integration](public_cloud/compute/local-zones-vpn-tailscale-integration)
+ [Migration of instances between different regions](public_cloud/compute/migration_between_regions)
+ [Storage and Backup](products/public-cloud-storage)
+ [Object Storage](products/public-cloud-storage-object-storage)
+ [General information](public-cloud-storage-object-storage-general-information)
Expand Down
212 changes: 161 additions & 51 deletions ...blic_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-gb.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,60 +23,170 @@ You can make use of these instance backups for two basic purposes:

### Creating an instance from a backup

Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. Then click `Instance backup`{.action} under the **Compute** section.

![public-cloud-instance-backup](images/restorebackup01.png){.thumbnail}

Click on the `...`{.action} button in the row of the relevant backup, then select `Create an instance`{.action}.

You will see a shortened version of the instance creation page where you can decide on some options.

![public-cloud-instance-backup](images/restorebackup02.png){.thumbnail}

Some elements are pre-defined:

- **Region**: Your instance will be created in the same data centre as your backup.
- **Image**: The image will correspond to your backup.
- **Model**: Only the models that are compatible with your image are available, depending on your quota.

![public-cloud-instance-backup](images/restorebackup03.png){.thumbnail}

Choose the new instance's name, SSH key, vRack and billing period, then click on the `Create the instance`{.action} button.

For further information on creating an instance, please refer to [this guide](/pages/public_cloud/compute/public-cloud-first-steps).

> [!primary]
>
> In order to create the instance in a different data centre, you will first need to transfer the backup to the appropriate region. Please refer to our guide to [transferring an instance backup](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another).
>
> [!tabs]
> Via the OVHcloud Control Panel
>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. Then click `Instance backup`{.action} under the **Compute** section.
>>
>> ![public-cloud-instance-backup](images/restorebackup01.png){.thumbnail}
>>
>> Click on the `...`{.action} button in the row of the relevant backup, then select `Create an instance`{.action}.
>>
>> You will see a shortened version of the instance creation page where you can decide on some options.
>>
>> ![public-cloud-instance-backup](images/restorebackup02.png){.thumbnail}
>>
>> Some elements are pre-defined:
>>
>> - **Region**: Your instance will be created in the same data centre as your backup.
>> - **Image**: The image will correspond to your backup.
>> - **Model**: Only the models that are compatible with your image are available, depending on your quota.
>>
>> ![public-cloud-instance-backup](images/restorebackup03.png){.thumbnail}
>>
>> Choose the new instance's name, SSH key, vRack and billing period, then click on the `Create the instance`{.action} button.
>>
>> For further information on creating an instance, please refer to [this guide](/pages/public_cloud/compute/public-cloud-first-steps).
>>
>> > [!primary]
>> >
>> > In order to create the instance in a different data centre, you will first need to transfer the backup to the appropriate region. Please refer to our guide to [transferring an instance backup](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another).
>> >
>>
> Via the Openstack CLI <a name="createinstanceviaopenstack"></a>
>> > [!warning]
>> >
>> > If your instance is a Windows server, you must select a flavor of type win-xx-xx (for example, win-b2-15) and have a public interface on the Ext-Net network. Without these conditions, authentication with the OVHcloud KMS will not be possible, and your server will remain with an [unactivated licence](/pages/public_cloud/compute/activate-windows-license-private-mode). This could lead to limitations, including the absence of updates. Please note that it is not possible to resize a Linux instance (such as b2-15) to a Windows instance (such as win-b2-15). To make this transition, you need to recreate a new instance.
>> >
>>
>> To create an instance from your backup, use the backup ID as the image with this command:
>>
>> ```bash
>> $ openstack server create --key-name SSHKEY --flavor 98c1e679-5f2c-4069-b4da-4a4f7179b758 --image 0a3f5901-2314-438a-a7af-ae984dcbce5c Server1_from_snap
>> ```
>>
> Via Horizon <a name="createinstanceviahorizon"></a>
>> In the Horizon interface, click on `Compute`{.action} in the left-hand menu, then on `Images`{.action}. Find the desired image and click on the `Launch`{.action} button to the right of your image line.
>>
>> ![public-cloud-instance-backup-horizon](images/restorebackuphorizon1.png){.thumbnail}
>>
>> Name your instance in the dedicated field and determine the number of instances to create. Then click on the `Flavor`{.action} tab.
>>
>> ![public-cloud-instance-backup-horizon-2](images/restorebackuphorizon2.png){.thumbnail}
>>
>> Choose the desired instance model, then click on the `Networks`{.action} tab.
>>
>> > [!warning]
>> >
>> > If your instance is a Windows server, you must select a flavor of type win-xx-xx (for example, win-b2-15) and have a public interface on the Ext-Net network. Without these conditions, authentication to the OVHcloud KMS will not be possible, and your server will remain with a [license not activated](/pages/public_cloud/compute/activate-windows-license-private-mode). This could lead to limitations, including the absence of updates. Please note that it is not possible to resize a Linux instance (e.g. b2-15) to a Windows instance (e.g. win-b2-15). To make this transition, you need to recreate a new instance.
>> >
>>
>> ![public-cloud-instance-backup-horizon-3](images/restorebackuphorizon3.png){.thumbnail}
>>
>> Choose the network you wish to assign to it, then click on the `Launch Instance`{.action} button.
>>
>> [public-cloud-instance-backup-horizon-4](images/restorebackuphorizon4.png){.thumbnail}
>>
>> You can find the status of your new instance in `Compute`{.action} in the left-hand menu, then on `Instances`{.action}.
>>
>> ![public-cloud-instance-backup-horizon-5](images/restorebackuphorizon5.png){.thumbnail}
>>
> Via the OVHcloud API <a name="createinstanceviaapi"></a>
>> > [!api]
>> >
>> > @api {v1} /cloud POST /cloud/project/{serviceName}/region/{regionName}/instance
>> >
>>
>> Parameters:
>>
>> > **serviceName** *
>> >
>> >> The OVHcloud project ID.
>>
>> > **regionName** *
>> >
>> >> The region name where the instance will be located
>>
>> Example of the request body:
>>
>> ```json
>> {
>> "billingPeriod": "hourly",
>> "bootFrom": {
>> "imageId": "5cb8ea68-****-****-****-820be8346***"
>> },
>> "flavor": {
>> "id": "e81b46f8-****-****-****-cad655e65***"
>> },
>> "name": "newInstance",
>> "network": {
>> "public": true
>> },
>> "sshKey": {
>> "name": "MySSHKey"
>> }
>> }
>> ```
>>

### Restoring an instance from a backup

Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. Click on `Instances`{.action} in the left-hand sidebar.

![public-cloud-instance-backup](images/restorebackup04.png){.thumbnail}

Click on the `...`{.action} button in the row of the relevant instance, then select `Edit`{.action}.

This opens the page for editing an instance where you can change:

- the instance's name
- the instance's image
- the instance's model
- the instance's billing mode (from `hourly` to `monthly` only)

Make your changes if necessary and switch to the `Backups`{.action} tab of the **Image** section.

![public-cloud-instance-backup](images/restorebackup05.png){.thumbnail}

Select from the list of available backups. Click on `Modify image`{.action} if you are certain that you want to overwrite the current image with the backup.

The instance will have the status `Re-installation` until the process is completed. It might be necessary to refresh the page in the browser in order to see the current status.

> [!warning]
>
> As stated in the warning message, any data added after the backup creation will be lost.
>
> [!tabs]
> Via the OVHcloud Control Panel
>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. Click on `Instances`{.action} in the left-hand sidebar.
>>
>> ![public-cloud-instance-backup](images/restorebackup04.png){.thumbnail}
>>
>> Click on the `...`{.action} button in the row of the relevant instance, then select `Edit`{.action}.
>>
>> This opens the page for editing an instance where you can change:
>>
>> - the instance's name
>> - the instance's image
>> - the instance's model
>> - the instance's billing mode (from `hourly` to `monthly` only)
>>
>> Make your changes if necessary and switch to the `Backups`{.action} tab of the **Image** section.
>>
>> ![public-cloud-instance-backup](images/restorebackup05.png){.thumbnail}
>>
>> Select from the list of available backups. Click on `Modify image`{.action} if you are certain that you want to overwrite the current image with the backup.
>>
>> The instance will have the status `Re-installation` until the process is completed. It might be necessary to refresh the page in the browser in order to see the current status.
>>
>> > [!warning]
>> >
>> > As stated in the warning message, any data added after the backup creation will be lost.
>> >
>>
> Via the OVHcloud API
>> > [!api]
>> >
>> > @api {v1} /cloud POST /cloud/project/{serviceName}/region/{regionName}/instance/{instanceId}/reinstall
>> >
>>
>> Parameters:
>>
>> > **serviceName** *
>> >
>> >> The OVHcloud project ID.
>>
>> > **regionName** *
>> >
>> >> The region name where the source instance is located.
>>
>> > **instanceId** *
>> >
>> >> The unique instance ID.
>>
>> Example of the request body:
>>
>> ```json
>> {
>> "imageId": "5cb8ea68-****-****-****-820be8346***",
>> "imageRegionName": "GRA11"
>> }
>> ```
>>

## Go further

Expand Down
Loading