VMware migration is basically possible only with vMotion license which is included with Essentials Plus and higher VMware licensing. This allows to migrate a VM and to have no downtime with loosing connectivity to a VM and the end users not even noticing that the VM has migrated to another host. But how about users willing to migrate VMware VMs without vMotion license? What if there was an easy option to migrate VMware VMs with little downtime – for free…
This article is here to help folks starting with VMware virtualization, not for experienced VMware admins, but even if this article is not your interest you can share to your followers as it might just be their interest. Small shops without budget usually gets the lowest possible packaging called VMware Essentials (if they don't go for Free Hyper-V) which does not offer vMotion functionality, but still provides centralized management up to 3 hosts with up to 2 physical CPU each. No limit on physical RAM, but also not real data protection or possibility to proceed with an upgrade of hardware without perhaps some significant downtime.
How those businesses can migrate a VM(s) to another host? Usually VMs has lots of data to shift elsewhere so manual copy of the VM isn't an option. The VM is usually located on DAS (direct attached storage), on SAN or on more economical NAS device perhaps. So which third party free tool would help in this situation to do the migration with no or small downtime? Free Veeam Backup and Replication can do the job – with VM(s) running (or not).
First I outline what is possible to achieve:
- Migrate VMs between hosts – it's possible to migrate VMs from one host to another (with small downtime).
- Migrate running VMs – Migrate a running VMs from one type datastore to another (if storage vMotion is not available).
- Several VMs at once – you can migrate several VMs at once
The steps:
1. Download and Install Veeam Backup and Replication Free Version – too easy to shoot screenshots for this. Basically any Windows system can be used > next > next…
2. Register the source and destination host or if you're using vCenter, you can register vCenter
3. Right Click a VM that you want to migrate
4. Pick up a destination host and datastore
You can pass the proxy specification as you have only the Free version of Veeam, and specify if you want to delete the source VM after migration.
And just sit and watch the process to migrate. The result is below…
In my example I'm demoing of migration of VM from 10.10.5.12 to 10.10.5.10. And if we look at the details of the job by clicking the W2003 VM we can actually see what's been happening under the covers… Note that Veeam waits for the heartbeat before deleting the source VM…
You can see the most time was spend on the copying of VM files, but this has been done while the original VM was still running so no impact on production! Then only the VM has been powered Off > the delta files were copied over > the VM has been reconfigured, registered on a host, snapshot removed and VM was powered On.
As you can see the tasks after the initial copy are fairly quick so your production gets impacted, but not during the initial copy of VMDK files.
Veeam Backup and Replication v8 has been released recently and the product has (again) improved over previous release.
But Veeam Backup and Replication v8 Free Version has also some cool built in explorers. There are 4 of them:
Veeam Explorer for AD – see How-to restore computer account with Veeam Backup and Replication Free version And Track Changes On AD Objects. Also there are Veeam Explorer for SQL, SharePoint or Exchange Server. You can download the free version of Veeam from this link.
david says
I have a feeling this free tool doesn’t work with the free version of ESXi. Has anyone tried it in anger?
Vladan SEGET says
That’s correct. The free version of VMware hypervisor has its APIs locked. See details here: http://www.vladan.fr/esxi-5-free-whats-the-limitations/
Alexey says
Extrasphere solution supports free ESXi.
Trevor says
You can always put the free version of ESXi in “evaluation” licence mode (assuming you haven’t already run out the 30 day trial period) to achieve this, but it’s obviously a time-limited solution.
Dedik says
good article…
i am very interest about cloud server especially using vmware
can i get complete tutorial starting installation till application cloud server
thanks
regards
Dedik Kurniawan
Daniel says
I downloaded and installed the latest Veeam Backup and Replication 9.0
I am now stuck at step 2. Which program do I open? After installation, I have under Veeam Tools in start menu now:
*Configuration Databas Connection Settings
*Configuration Restore
*VBK Extract.
None of those seem like the right option…
Daniel says
Nevermind – when installing, there are multiple options – I needed to install the console. This worked.
Tom says
Hello, does this method still work with paid Veeam and vSphere Essentials Plus??
Researching very occasional svMotion and vMotion between two servers with local storage only.
Thank you, Tom
Jack says
This only works free with:
ESXi 3.5u2
ESXi 3.5u3
Where the API was unlocked by accident. Otherwise, only ghettoVCB works No budget, and works perfectly if your VMs are not too large.
Labsy says
Excellent tutorial, thank you!
I’ve just managed to migrate VMs from old free ESXi 5.0 and 5.5 to newer free ESXi 6.5. As mentioned, all hosts need to be put in evaluation full VMWare licence mode for the time of migration, because Free ESXi licence does not allow some needed services to run on host.
I struggled with Veeam B&R 9.5 instalation quite a bit. 1st install failed after chewing my PC for almost an hour. 2nd install did not even get to the end, waited 3 hours, then I rebooted. Ran 3rd install and got error “Cannot start some XY Veeam service”. Rebooted and went for 4th install, which finally succeeded.
I dunno what bothered the install process, PC is fairly equipped, 16GB RAM, i7 and 256GB SSD + 4TB SATA for backup storage. Anyways, due to the fact I’ve got different errors after each install I finally managed to install Veeam B&R 9.5 and got it running.
From there on it was a breeze – PC connected to old and new ESX hosts direcly, migrated 90GB VM in 35 minutes with downtime of 1-2 minutes top. That’s way way better than I ever dreamed of.
NOTE: To stay on the safe side, I dod NOT check “Delete source VM after migration”.
Vladan SEGET says
Thanks for sharing Andrej. Usefull.