Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Hot migration - the migration of virtual servers between compute resources that share common data stores (or data store zones)
  • Cold migration - the migration the migration of virtual servers and disks between compute resources with local storage or across compute zones

Anchor
1
1
Hot migration between compute resources

...

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you want to migrate.
  3. Click the Tools button and press the Migrate Virtual Server link.
  4. In the window that appears, choose migration type - Hypervisor.Compute resource
  5. Choose the target compute resource from the drop-down menu.
  6. Move the Cold-migrate when hot-migration fails slider to the right if you want to apply cold migration in case of hot migration failure.
  7. Click the Start Migration button.

...

  • The virtual server should be shut down to perform migration.
  • The current and the target compute resources and data stores should be in the same location. Migration between locations is not possible.

  • Networks must be the same across the zones. That means that compute zones should have the same network attached.

  • The bandwidth from compute resource to compute resource should be sufficient enough to allow transferring of virtual servers.

  • This feature is applicable suitable for disks VSs with local storage. Be aware, that migration will take much more time, if you want to perform it between shared data stores.
  • Be aware, that disk migration is better than full VS migration in case you want to migrate the disks within the same compute zone and if the advanced backup scheme is used. Such scenario is applicable only for the shared data stores within the same compute zone.

 


To cold migrate a virtual server:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you want to migrate.
  3. Click the Tools button and press click the Migrate Virtual Server link.
  4. In the window that appears, choose migration type - Hypervisor and Compute resource and Storage (Cold only).
  5. Choose the target compute zone and compute resource from the drop-down menu.  The The list will include the other zones that you have access to within the same network (i.e. KVM to KVM migration but not KVM to XEN migration). 
  6. Also you can see each see each disk associated to the virtual server with a drop-down menu. Choose target the data stores for where you wish to move each disk from the drop-down menu.  The The list will include available data stores associated with the compute zone and compute resource, selected in the previous step.
  7. Click the Start Migration button.
Note
  • Cold migration is not applicable for federated VSs, which are built on compute zones submitted to the Marketplace.

  • If you have local backups on source compute resource, please move them manually to a target compute resource or backup server.

  • If you change the compute resource or data store zone, the billing will be changed according to the prices set for that new zone in the billing plan.

  • Go to Control Panel's Settings menu > ConfigurationDefaults tab > Migration options if you want to set migration rate limit and limit of transactions which can be run simultaneously on the target compute resource when migrating a VS.
  • The following disk migration scenarios are applicable: from LVM data store to LVM data store; from LVM data store to Integrated Storage data store; from Integrated from Integrated Storage data store to LVM to LVM data store. This feature is not applicable for SolidFire storage.
  • Disks, migrated from one LVM data store to another, will be renamed at source data store. In case of Integrated Storage, disks will remain with the same name at source data store and will be marked as offline zombie disks. You need to delete them manually, otherwise you will get an error during backward migration.

OnApp administrators can control user access over virtual server migration. Using OnApp permissions, you can allow/forbid users to perform migration of all virtual servers, or their own servers only. This is handled via the Control Panel's Roles menu.