Veeam just released Backup 3.0 with ESXi(including the Free version) support:
In addition to the ESXi backup through VCB that was introduced with version 2.0, Veeam Backup 3.0 now supports ESXi backup without VCB. Veeam Backup is the only VMware backup solution that lets you backup and restore virtual machines running on all existing editions of ESXi, including ESXi free.
Now head over to Veeam and download your trial and start doing full VM backups. Veaam Backup also provides you with a file level restore:
Veeam’s fast file-level recovery feature allows you to restore individual files from your image-level backups and replicas in seconds, without having to extract the full VM image to your local drive.
Just a tip, I would suggest to do a “zero-out” before running the full VM backup!
Matt says
The Veeam Backup 3.0 states the following:
Veeam Backup 3.0 offers full support of ESXi. It uses VI API to access ESXi and enable backup directly to ESXi servers and restore from ESXi servers. You may select to perform backup of ESXi both with and without the VCB proxy. Yet ESXi servers still cannot be used to accommodate backup (VMware limitation).
Doesn’t the last sentence contradict the rest?
Duncan Epping says
I think they mean that you can’t write the data to ESXi?
Matt says
Got me. The first part says you can “backup directly to ESXi servers and restore from ESXi servers.” Yet the last sentence makes it seem like you can’t.
Maybe it’s just worded incorrectly?
ag says
Matt, where did you find that statement? I am not seeing it anywhere on VEEAM web-site or release documentation. Can you give a link?
Jason Boche says
Some wording to work through here to be perfectly clear as to what’s supported and what’s not (and workflow).
Matt says
Click on User Guide at the following link:
http://www.veeam.com/vmware-esx-backup.html
Page 15 of the PDF.
Matt Carpenter says
ESXi is fully supported for VM backups and restores using the Veeam API method. When using Veeam Backup in conjunction with VCB an ESXi host can only be a source. So if your using VCB with Veeam that method is the limitation on the ESXi restore as per vmware. When using Veeam Backup without the VCB connection ESXi is fully supported. Please let @veeam or @matt_carpenter know if there are any further questions.
Matt says
If the limitation is the restore, why does the user guide say “Yet ESXi servers still cannot be used to accommodate backup (VMware limitation)”? That makes it sound like it’s a problem with backup, not restore.
Either way, maybe some clarification of that statement in the user guide is a good idea.
William says
I don’t use this tool, but I assume that ESXi is only supported if it’s running ESXi 3.5u3 as the API has both read/write access (for the moment)? Once this has been fully patched/fixed, then you’ll be required to purchase a license that supports both read/write operations using the VI API?
Matt Carpenter says
After looking at the question again. I do have a clarification on the topic. “ESXi hosts cannot be used as a backup target.” So when you create a backup job that job’s target cannot be an ESXi host. What is supported is a ESX host as a backup target. Sorry for the confusion.
Matt Carpenter says
We are not using the “bug” capabilities to support ESXi. Once that is fully patched/ fixed our product will continue to work since we are not exploiting that “bug” to provide full ESXi support.
Matt Carpenter says
Also our product does not require putting an ESXi host into a “unsupported” mode and enabling extra console services, which presents significant security risk and is not supported by VMware.
William says
Hi Matt,
That means ESXi is only supported if it’s licensed and not the free version of ESXi? As far as I’m aware of the VI API is supposed to be readonly, so for user’s of the free ESXi release should only have read access to the API, something like a backup I assume would be deemed as a write operation?
I primarily work with the full license set of standard ESX and I know ESXi is offered currently as a free hypervisor but that does not include write operations using the VI API. It’s stated ESXi is supported w/o VCB and utilizes the VI API, just trying to get a handle on how this is being handled.
PS – I do agree with not utilizing the unsupported SSH console.
Thanks
–William
ag says
I think you are confusing VI API with RCLI. It is RCLI that is limited to read-only access for the free version of VMware ESXi. RCLI is what got accidentally “unlocked” in update 3.
William says
ag,
So to clear things up, the VI API through the exposed WSDL can be used to call both read/write operations on the free version of ESXi? I was under the assumption this was a feature that was only provided through paying customers? The RCLI uses VI API through VI Perl Toolkit which was accidentally unlocked through an internal API fix.
I would have thought the API in general is readonly unless you’re paying for that? Correct me if I’m wrong, it’s been something I’ve tried to get my head around on what you’re officially allowed to do using the various API/SDK and toolkits with the free version of ESXi
Carter Shanklin says
The API on free ESXi in general is intended to be read-only. That goes for RCLI, VI Toolkit, VI Perl Toolkit, VI SDK and the rest.
ag says
William, sorry but I am unable to answer your question – it is too technical for me, I am one of those who gets scared to hear words like WSDL. 🙂
Frankly I am not quite sure which APIs are read-only on free ESXi and which are not – but brief internet research showed that only RCLI is mentioned to be locked as read-only.
But it is clear that not all existing APIs are read-only in free ESXi, since VIC datastore browser is still able to both download and upload files from/to free ESXi servers. Meaning you can still potentially do backup and restore from/to free ESXi using the API datastore browser uses.
William says
ag,
Per Carter’s comment and further questioning, As already stated, the API on free ESXi is generally read-only. You’re right in the fact that you can still upload/download through the datastore browser which seems to make use of the file management access (also available via POST command), but it’s limited to just upload/download.
I can see where ESXi can be supported to both download/upload non-running VM(s) VMDK and just manually registering with the VIC… but in terms of live running VM(s), you would need to take a snapshot. I’m just trying to figure out how this is being handled or is the support limited to the license you’re using.
Perhaps will get some clarifications in abit
–William
Doug Hazelman (vmdoug) says
Just to clarify (again) on what Matt Carpenter and AG have said.
Veeam Backup 3.0 does not require putting ESXi into support mode and does not rely on the RCLI or even VI API as you know it.
The exact method being used to read from (backup) and write to (recovery) for both ESXi and ESXi Free are Veeam proprietary methods that have been discussed with ESXi product management.
I believe the initial confusion was as Matt Carpenter pointed out, you can not use ESXi as a target to STORE your backups. Veeam Backup has always allowed using an ESX host or Linux host as a target for storing the backup files and even utilizes FastSCP as the transfer mechanism when the console agent is used (ESX source, no VCB).
As of today, all Veeam products support ESXi and ESXi Free editions.
We truly appreciate all the interested and if you have further questions please let Veeam know via Support/Sales/Twitter.
My email is firstname DOT lastname AT veeam DOT com
Thanks,
-doug
Doug Hazelman
Veeam Software
Director, Global Systems Engineer Group
ag says
William – I have a few free ESXi servers and I can assure you that snapshots work just fine there, so snapshotting for backup should not be a problem. Because obviously if VIC is able to issue API call to create snapshot, then any other application can do the same thing as well.
Hope this helps!
AusNetIT says
HI,
Can we backup free ESXI Servers?
Thanks,
AusNetIT
Http;//www.ausnetit.com.au