The latest version of the migration script can be downloaded from:
The script will work for SolusVM installations using LVM storage, at this stage it will not support any other method of storage for virtual machines. The script will only migrate servers that have a single primary disk (plus a swap disk on Linux). If you need to migrate a virtual machine then all additional disks must be consolidated to a single partition before you can perform the migration.
As part of the '-o migrate' option you must specify an OnApp template id for the virtual machine you are migrating, its very important that this template is the closest match to the OS distribution that you are migrating over, you can find a list of OnApp template id's using the command below.
bash#> sh solusexport.sh -o templates -H demo.onapp.com -u admin -p xxxx
Once you have your template id you can run a migration, the script must be ran from the SolusVM hypervisor:
Fetch a list of running VMs:
bash#> sh solusexport.sh -o list
Listing all virtual machines
- Name ID
- vm102 86
Once you have identified the VM you want to migrate you can begin:
bash#> sh solusexport.sh -o migrate -H demo.onapp.com -u admin -p xxxx -t 12 -v 86 -d lin
To show the help menu with additional configurable options you can run:
bash#> sh solusexport.sh -o help
Note that the virtual machine you want to migrate must be running on the SolusVM hypervisor to start a migration. Once the migration is started the VM will be shutdown and must not be started until the migration is complete, possible data corruption could occur if the VM is started during a migration.
You must have ssh keys on all of the OnApp hypervisors to allow root@solusVM-HV to SSH to root@OnApp-HV. The script will fail if the SSH keys have not been configured before the migration is started. This is an important step.
Also note that this script is simply designed to migrate the virtual machine, there is a good chance that once the virtual machine is migrated it will fail to boot due to differences in the virtualisation configs at both ends, if the virtual machine fails to boot you will need to boot it into rescue mode in OnApp and make the necessary changes to the /boot/grub.conf, /etc/fstab and /etc/inittab files. On Windows VMs its possible that virtualisation and device drivers will need to be updated.
* Please note that this script was developed against OnApp 2.x and has not been through an official OnApp QA process. If you use this please post your feedback in our forums at https://forum.onapp.com/index.php?forums/migration-tools.19/
Please sign in to leave a comment.