Migrating an Instance with Legacy Flavours

The following procedure can be used if your existing m1 or m2 instance has an ephemeral file system, AND you need to keep the data in it.

Further contextual information can be found on the Nectar Support site.


  1. Back up your files. You should already have a procedure for making regular backups of your valuable files held on your instances and attached storage. Before you start the migration, make sure that your backups are up to date.

  2. Take your instance out of normal service. You are in the best position to know what this will entail.

  3. Unmount and detach any volumes from the instance. These will need to be migrated separately; see “Migrating a volume”.

  4. Shut down the instance.

  5. Snapshot the instance. You should verify that the snapshot has been successfully uploaded to the Image catalog.

  6. Launch new instance from snapshot in target Availability Zone. If you run into the “No valid hosts found” issue, you could try using a smaller flavor for the new instance, either temporarily (and resize later) or permanently. Alternatively raise a support ticket.

  7. If you have decided that you need a volume to replace the ephemeral file system:

  8. Restart the old instance, but do not restart user-facing services.

  9. Use rsync to copy the files from the old instance’s ephemeral file system to the new instance. The target location for the copied files on the new instance is up to you. Depending on the circumstances, you could copy some or all of the files into the new instance’s root file system.

  10. Shutdown the old instance once more.

  11. Attach any other migrated volumes. After attaching the volumes, you should verify that the device names (“vdb”, “vdc”, etcetera) for the volumes are as expected and then mount the volumes’ file systems.

  12. Verify the correct operation of the new instance. You are in the best position to know what this will entail.

  13. Restore the instance to service. You are in the best position to know what this will entail.

  14. Wait. It is advisable to keep the old volume for a few days in case it is needed to roll back the migration.

  15. Delete the old instance