VMWare ESXi Virtualized Hardware Differences

I work for a small company that recently started to work with VMWare ESXi.  We currently have a single ESXi box that we've been running 4 guests on for a few months now with great results.  We're thinking of buying a second server for ESXi, and I'd like to be able to restore guests between ESXi host servers in case of a hardware failure (the second server would run testing/demo servers, which would be shut down if we need to restore guests from the primary server).  

Since we don't have access to shared storage, I know my options are limited.  I've read about using vConverter and FastSCP to transfer a guest from one machine to another over a network, but I've also heard that the transfer rates can be painfully slow.  I'm thinking we could just restore from windows backup (.bkf) files instead.  I've restored a .bkf to a fresh Windows 2003 install on the same VMWare host successfully.  My concern is that we might run into problems if the physical server hardware isn't identical.

Will the same version of ESXi always present identical hardware to guests, assuming the guest configurations match, regardless of the physical hardware the ESXi host is installed on?  Or can there be differences?

Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Yes, ESXi will always present identical hardware to guests, regardless of physical hardware in the host. But remember AMD and Intel processors in the host will also be different in the guests.

This is why it's such a great infrasturture for Disaster Recovery to Bare Metal because the Guest VMs are always the same.

The transfer rate will be dependant on how fast your network is. You could use Veeam Backup and Replication or vizioncore Vranger Pro to backup to CIFS (Windows share), and restore to different ESXi host.

I've down this on small sites, an averahe VM (12GB) takes about 30 mins to backup, and 30 mins to restore, I think that's a good DR window. If you backup the whole VM, backup and restore is easier, and less to go wrong.

with your example, backing up using Windows Backup, and resoring to a Windows 2003 machine is not exaclty the same as backup and restoring the VM.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
but whatever works for your organisation....
If you have big enough storage on the new server to store the vms locally, you can copy them via scp.


VMware is basically stripped down Linux.  You can use the instructions above to get to a console.  Then you can change to the directory of the vms /vmfs/storage  then you can use the scp command to copy to the IP Address of the other server.

This can be scripted to run on a daily basis.  
rvivek_2002Connect With a Mentor Commented:
I would like to add few points.

1. Yes VMs totally hardware independent (that is virtualization)
2. If your first esx hardware fails, you may not be able to copy the files using any tools (if the hard disk is intact you can try mounting that on a different server), hence just having two server is not a a bckup plan.
3. If you back up the entire virtual machine folder, it is good. However you will have to stop(shutdown) your VM during backup window.  (unless you are using a VMware aware backup software)

4. Restoring from Windows backup is fine. If you uitilize your ESX host more (if you have many VMs and the resource utilization is high), then you should configure your VM back up at different times, to avoid the ESX server getting loaded because all the VMS run backup at the same time.
Eric_PSUAuthor Commented:
Thanks all for the feedback.  It's reassuring to know that .bkf restores should work fine between ESXi servers, in case I end up going with that method for backup and restore.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.