I have already posted (several times) about:
- NO ONE SHOULD USE THIS IN PRODUCTION
- THE VDR PRODUCT IS FAULTY AND SHOULD BE RECALLED
- VMWARE SHOULD TAKE ACCOUNTABILITY AND WARN CLIENTS THAT THIS IS NOT A RELIABLE PRODUCT (YET)
So, I completely agree with you. After a couple of SRs, I had to give up. I don't get paid to troubleshoot "experimental" software. We paid good money for the VMWare product...it is a shame they ARE NOT LISTENING to their customers.
Has anyone heard anything from VMware regarding the possibility of fixes for these issues (or a 1.0.3 release)? I find that I have to either reboot my VDR VM every day or, at least, restart /etc/init.d/datarecovery in order for the VDR vClient plug-in to actually be able to connect to the VM.
I heard late December something was supposed to be released from vmware concerning VDR
While fixing something in vSphere I was told by a VMware support Eng that by late November VMware would release vSphere U1 and probably also an update to VDR
I suggest, you STOP using VDR as a primary backup solution for production systems. There are enough problems in the forums to indicate the product has serious flaws and is highly unreliable.
STOP USING IT unless you are "testing VDR" as non-primary backup solution. If you are "testing VDR", then let me say "Thanks" - because I can't spend the time it takes to beta test it and deal with the headaches of it not working.
We have just implemented vSphere 4.0, and very happy that VMware had incoporated a backup product VMware Data Recovery. The implementation was installed 8 weeks ago, VDR has been running perfect with no issues, until the weekend. The backups just hang, integrity and recatalog no longer work, it states the store is locked and we need to remove damaged restores, but no restores are marked as damaged, we have error -2240.
We raised an SR today, and the VMware Support Repesentitive told me VDR was SHIT! (his words), and we should use another third party product e.g. Veeam or Vizioncore vRanger. He told me Support Engineers view VDR as experimental, but management view it as production.
I'll be trying to speak to my Sales/Account Manager tomorrow to try and get a handle on this, because we have no money to purchase Vizioncore/Veeam product, and don't won't to use third party addons, when we've paid-up for Enterprise, and we cannot use the backup application.
Comments, anyone know how I can cure the -2240 error?
Sorry dude...the. Engineer was right. VDR is crap.
Chief Information Officer
Lexington Memorial Hospital
Lexington, NC 27293
Well it looks like we'll be speaking to VMware tomorrow, and finding out what's the situation, and trying to get some money out of them, for a third patry product to backup up our environment!!!
Go Go Go Einstein !
Let us know the outcome, as a vSphere Essentials Plus user, there is USD $ 2000 price difference with the lowest vSphere Essentials license which is for HA and VDR features.
Good luck...they "owe" all of us. At the very least, they should recall the product and provide some tangible service (i.e., extra months of support, extra license, etc...)
Just heard from vmware support that VMware vpshere 4 Update 1 will be out on the 19/11/2009 6:00pm PST he didnt know if it will have a update to vmware VDR
Thanks for the heads up regarding the release.
I'm surprised the tech couldn't read/review the release notes to let you know if VDR was being updated.
Around the 20th of November VDR 1.1 will be released.
This release will fix a lot of problems and increase
performance drastically on certain operations.
I will send you another mail with the direct link once it
I managed to get going again, by stopping datarecovery service, removing *.lck files in the store, and restarting datarecovery. Now I need to workout why one VM backup stops at 73%
I wait with baited breath and hope this is the release we have all been waiting for!