While I was looking into various ways to restore an ESXi config backup I came across a bug.
If you read VMware’s documentation about how to restore an ESXi config backup (you can find that here) you will see that it is full of references saying the build numbers must match.
The bug is that you can restore an ESXi config backup even if the build numbers don’t match. Which according to the VMware documentation should not be possible.
Even though it is possible to restore an ESXi config backup when the build numbers don’t match, I do not recommend doing this as there has to be a reason why VMware says that the build numbers must match.
In my testing I was able to replicate the bug in ESXi 7 and ESXi 8. I even went all the way back to ESXi 6.7 which had some interesting findings. I didn’t fully test everything in ESXi 6.7 as general support has ended on that version.
Here are my findings and how to replicate the bug.
Generating Backup Files
In order to test everything as much as possible I wanted to have a few ESXi config backup files. This is how I generated the ESXi config backup files that I used in my testing.
- Fresh install of ESXi 7 Update 2e Build Number 19290878.
- Took an ESXi config backup from ESXi 7 Update 2e Build Number 19290878.
- Fresh install of ESXi 7 Update 3d Build Number 19482537.
- Took an ESXi config backup from ESXi 7 Update 3d Build Number 19482537.
- Fresh install ESXi 7 Update 3k Build Number 21313628.
- Took an ESXi config backup from ESXi 7 Update 3k Build Number 21313628.
Restoring from ESXi 7 Update 3d to ESXi 7 Update 3k
Once ESXi 7 Update 3k Build Number 21313628 was installed I tried to restore an ESXi config backup that was taken from ESXi 7 Update 3d Build Number 19482537.
When I do the restore using the vim-cmd hostsvc/firmware/restore_config
method it works.
Due to the fact that the restore worked I then reinstalled ESXi 7 Update 3k Build Number 21313628 again.
…