Migrate VMs from ESXi 6.0 to ESXi 8.0

[enex122]

Hello Guys

I am really hoping someone can help me. So I have I problem I need to migrate 5 VMS from an ESXi host 6.0.0 (Build 3620759) to a completely new ESXi host 8.0 Update 2.  I need to migrate the vms from the old Server to the new one. It has to be remote I can't be physically there for example to copy them on a drive or something. 

As a backup application I am using Veeam backup and replication 9.5 

I already saw this post in the form but based on what I read on the Website of Veeam ESXi 8.0 is not supported by Veeam backup and replication 9.5 

https://www.veeam.com/kb2443

https://communities.vmware.com/t5/ESXi-Discussions/Migration-of-VM-from-esxi-6-to-esxi-8/m-p/2948694...

So before I start I have a other question in theory the vms should run fine on the esxi host 8.0 right? Because the Hardware versions of the Virtual Machines are upwards compatible (The VM with the oldest HW Version has Version 7: ESX/ESXi 4.0 and later (VM-Version 7)) 

Now my first question: I would really like to use Veeam to migrate the VMs so is it officially not supported but could still work? 

My second& third question: I did some research and unfortunately there is no way for me to update Veeam to the newest version from the one I am currently on. If the license I have for my veeam version is currently valid is it also valid for the newest version of veeam?

So to summe it up I would have to completely rebuild my veeam which I have to do anyway but is the newest version of veeam backup and replication (Version : 12.0.0.1420 P20230718) compatible with the really new version from ESXi 8 (Update 2 from the 09/21/2023) or do they have to make a new version?

Now my last question:  Do you guys know a other way for me to migrate the vms from the old host to the new one? Because I don't have much experience with vmware and veeam. 

Here you can find some information that I thought could might be of use:

Old Host:

esxi version 6.0.0 Update 2 (Build 3620759) not connected to any vcenter

License VMware vSphere 6 Essentials

VMs stored locally 

Amount of VMs: 5

Space used from VMs ~1.8 TB

vMotion not supported 

New Host:

esxi version 8.0 Update 2 (09/21/2023)

License VMware vCenter Server 8 Essentials for vSphere 8,  VMware vSphere 8 Essentials 

VMs will be stored locally 

Backup solution :

Veeam backup and replication 9.5.0.1536

License Veeam Data Platform Essentials Standard

Backups are stored on two NAS one internal and one outside of the network

Thank you for reading this post and giving me advice I really appreciate it.

[kenobi79]

hi

take a look at vmware converter
Check compatibility.
With this tool it is possible to move a vm from one environment to another and possibly update and/or resize the virtual HW

Obviously you have to consider a downtime of the VMs

Check the documentation

https://docs.vmware.com/en/vCenter-Converter-Standalone/index.html 

[enex122]

Thank you for the Reply and advice I appreciate it. 

I just checked the documentation and I have two questions. I did not read the entire document but I recognized two points that could be a problem if I understood it right  

First: When reading document I noticed that there is a website to check the interoperability (Page 21 bottom) I am not sure if I used the website right but if I understood it correctly then there is a problem because the ESXi host 6.0 needs the converter version 6.2.0 but this one is not compatible with ESXi 8.0 they need the converter version 6.4.0 or am I understanding something wrong?

Second question: Also on page 21 there is a table with supported Operating systems now I have a Windows Server 2008 SBS vm that has to be migrated which is not in the table. But on the other side there is a example on page 33 where Windows Server 2008 is mentioned. So my question is the table regarding the supported operating systems on page  21 only for non vmware virtual/physical machines?

Sorry if I am bothering you with to many questions but I have to know an exact plan when migrating the VMs no time for errors

[VRO123]

Hope the below article helps you, You can try Vembu is a backup tool it support 8.x env, in the free version you use up to 10 VM's 
What’s New in BDRSuite v5.5.0 covers vSphere 8.0 Backup – VMwareGuruZ

[battybishop]

Other option could be to use the OVFTool and export the VM from 6.0 host and then import into 8.0 host, I'd always use the command line as it seems more reliable.

[a_p_]

I second @battybishop 's suggestion regarding the OVFTool.

Not sure if the same OVFTool version will work between ESXi 6.0 and 8.0, but https://williamlam.com/2012/06/how-to-copy-vms-directly-between-esxi.html may at least be worth a try.

Regarding your Veeam upgrade question. You can upgrade/reinstall Veeam B&R to the latest version for free, if you have an active subscription. However, please note that ESXi 8.0 Update 2 is not supported yet! (see https://www.veeam.com/kb2443)

André

[kenobi79]

Yes, there is actually a version compatibility problem with ESXI.

you should check if it is possible to upgrade ESXI to version 7, but I imagine you have "old" hardware

A further alternative to the one proposed by colleagues in the community could be the "trivial" one of a Backup & Restore, but you have to check the compatibility of Veeam 9.5 with ESXi8 (if I remember correctly you couldn't use more recent versions of Veeam)

I'll give you some steps on how I do it in your situation (be careful, it's not an official procedure! Check each step carefully!)

• Node upgrade (check compatibility at https://www.vmware.com/resources/compatibility/search.php and https://interopmatrix.vmware.com/Upgrade?productId=1 ).
  • It may take a few steps
• If I can get at least to ESXi7 I proceed with VMware Converter 6.4
• I check if the Veeam 9.5 version has the Quick Migration function and if all compatibility with ESXi version 8 is positive
• Once I have made sure that Veeam 9.5 is compatible (for the Restore part) with ESXi8 I would proceed with a Backup & Restore

Last alternative: export to OVF of the VM and import the OVF into the new node (https://kb.vmware.com/s/article/2007240 and VMware Compatibility Guide - Guest/Host Search )

Note: Regarding VMware Converter and Veeam Quick Migration, migration can occur without downtime

For other solutions you must allow for downtime in production

I hope I have clarified and, I repeat, this is my opinion. Always check!
Thank you all

[enex122]

Hello Thank you for the good answer and explenation.

Sorry for the late reply I was on holidays.

Unfortunately this sounds really time consuming and the license I have for esxi 7.0 I don't have.

A downtime would not be a problem.

Now my question: What if I would use scp to copy the VM folders from the old esxi host to the new one after turning them off? Could this work?

And does anybody know what I have to watch out for regarding compatibility when doing so,, because I did much research online and I only found to points to watch out for:

The first one is that the CPU of the old and new hopst both have to be the same architcture (INTEL or AMD). Which they are both intel just one really old one and a new one  (old:  Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz) ) (New one: Intel Xeon Silver 4215 (2.50 GHz, 8-core, 11 MB) )

And the second thing is the VM Hardware combability which is upwards compatible according to this article from vmware

https://kb.vmware.com/s/article/2007240

Is there anything else I have to watch out for 

Regards Enea 

[michaeldaly]

I moved a datastore from ESXi 4 to ESxi  6 some 8 years ago

I've attached my documentation...YMMV

i have to do what you're trying to do so would be interested in how it goes...

[kenobi79]

hi Enea

for licensing if esxi 7 there is the evaluation time that is 60 days

If you don't have donwtime problems, you can proceed with and export ovf and import ovf

I'd perform in this mode:

• poweroff of the "old" VM
• export ovf of the VM
• import ovf on the new environment
• upgrade all HW compatibility 
• Poweron of the "new" VM
• test new VM
• Delete the old VM after some days

The best way is with the tools of migration and with all upgrade processes of environments.

with SCP is dangerous because we have much variables regards the compatibility