Knowledge base

1000 FAQs, 500 tutorials and instructional videos. Here, there are only solutions!

Transfer an instance to another physical machine

Update 07/03/2026

This guide explains how to transfer an instance to another physical machine within the Infomaniak Public Cloud.

 

Preamble

  • This operation can be performed at any time and offers several advantages:
    • anticipate or avoid scheduled maintenance;
    • distribute the load among multiple hosts;
    • improve the stability or performance of an instance.

 

Migrate the instance to another physical machine…

 

… from Horizon

  1. Click here to access the management of your product on the Infomaniak Manager (need help?).
  2. Click directly on the name assigned to the product concerned:
  3. Click on the shortcut Horizon to connect:
  4. In the Instances menu, click on the action menu located to the right of the instance to be transferred.
  5. Click on Transfer an instance (Migrate):
  6. Confirm the transfer:
  7. Check the current status and wait a few minutes:
  8. Confirm the migration:
  9. Wait for the operation to complete before restarting or modifying the instance.

 

… via command line (CLI)

  1. List your available instances:
    openstack server list
  2. Identify the ID of the instance to be transferred (column ID).
  3. Start the migration to another physical host:
    openstack server migrate <instance_ID>
    This command triggers the movement of the instance to a new host within the cluster.
  4. Check the status of the migration:
    openstack server show <instance_ID>
    The instance then goes into the RESIZED state when the migration is complete but not yet confirmed.
  5. Once the migration is complete and validated, confirm the transfer:
    openstack server resize --confirm <instance_ID>
    or, depending on the version of the OpenStack client:
    openstack server migration confirm <instance_ID>
     
    • If the server migration confirm command displays a warning indicating that it is deprecated, the process is nevertheless executed in the background and the confirmation is taken into account.
    • If you get an error of type:
      Cannot 'confirmResize' instance ... while it is in vm_state active (HTTP 409)
      this means that the migration has already been confirmed (manually or automatically).
  6. You can also cancel the migration if a problem is detected before confirmation:
    openstack server resize --revert <instance_ID>
    or:
    openstack server migration revert <instance_ID>
  7. If no manual action is taken, the migration is automatically confirmed after 24 hours. The instance state then returns to ACTIVE.

 

The transfer is transparent to the operating system and instance data. A brief interruption may occur during the migration.


Has this FAQ been helpful?