I have the same issue. In fact, it's not the only issue i've had. I had to erase all my backups a few days back as well.
The specs:
- All vm's were created using vsphere client and are version 7
- We are talking 2 ESX hosts, SAN and a seperate backup server (that also hosts the vcenter server/vsphere client)
- we're running vsphere with the advanced license.
I've been using the product for about 10 days now, after I had read the entire administrators manual.
What I did was setup a single cifs share on our backup server and configured vmdr to use that. Also note that at first it failed to create the share because my password was too long? (i'm thinking the password must have been about 20 chars). in any case, it should prompt a message that it failed for that reason.
Then i created a single backup job, that included 7 VM's. Some are Centos 5.4, others are Windows Server 2003 (both 32 and 64 bit enterprise/Standard versions).
Most VM's have a single 15 GB C:\ drive, and optionally a additional data drive of usually 15/20 GB (always round numbers). I also have a database server running with a 200 GB data drive and a 20 GB c:\ drive.
Problem 1:
Integrity check : 8 execution errors.
Destination "/.../vmdr/" will be locked until the restore point with errors are deleted and integrity check succeeds.
I then marked the failed restore points for delete and ran integrity check again, without success, as it seemed to hang. (I've let it run overnight, but it never got passed 70% or so if i remember correctly. So i logged in and stopped the datarecovery service (which didnt respond). Then I killed it, deleted all the backups and went on with my new way of storing data.
I created, 7 cifs shares on the backup machine (for each VM one share), but all on the same server. This would allow for smaller indexes and problem seperation if it occurred. I also have 7 different backup schedules.
All went fine for 2 days. 2 restore points were created, but then last night I'm getting the same error as the OP. On one virtual machine. We'll name the VM 'tic'.
Tic has currently 2 restore points, while all others have 3. In the first restore point, there is only a single disk c:\ with 15 GB. I then added an extra data disk of 20 GB with thin provisioning on a different lun. This seemed to work fine in the second restore point. it shows the added disk of 20 GB. I thought all fine.
However, last night (where it would have created the 3rd restore point), it failed with the following error:
- Tic : Task incomplete
Job tic incomplete
trouble writing to destination volume, error -105 (unexpected end of data)
Nothing new was written to the newly added volume, perhaps its looking for changes, but not finding anything. The destination is still mounted properly and can be viewed from the date recovery console.
Any news on 1.2 releasing anytime soon? :).
