Job Failure for specific VM's (2)

[singy2002]

Hi,
I have a new backup job for a customer who has 26 VM's, I configred the backup as a single job and the initial run seemed to be fine.

Since the initial run the job has failed on 2 of the VM's, the error is below.

HFGSRVIS2.domain.net Error 12/11/2010 00:13:05 12/11/2010 00:28:16 380.00 GB 120.00 GB 135 MB/s 0:15:10
Backing up object "[esx-shared] hfgsrvis2/HFGSRVIS2.domain.net.vmdk"
BackupTextTrad failed
Client error: The specified item was already backed up or backup was not completed.
Failed to backup text locally. Backup: [Prev. backups: "veeamfs:6:dc7dc32a-6184-4456-88d7-e2101a5ace39 (vm-412)\HFGSRVIS2.domain.net-flat.vmdk@E:\Veeam\Backups\Daily Backup2010-11-10T200046.vbk".Inc. backup: veeamfs:6:dc7dc32a-6184-4456-88d7-e2101a5ace39 (vm-412)\HFGSRVIS2.domain.net.vmdk@E:\Veeam\Backups\Daily Backup2010-11-11T200033.vib].

Server error: End of file


MKDSRV07.domain.co.uk Error 12/11/2010 00:28:16 12/11/2010 01:01:38 453.91 GB 333.91 GB 171 MB/s 0:33:21
Backing up object "[esx-shared] MkdSrv07.domain.co.uk/MKDSRV07.domain.co.uk.vmdk"
BackupTextTrad failed
Client error: The specified item was already backed up or backup was not completed.
Failed to backup text locally. Backup: [Prev. backups: "veeamfs:6:dc7dc32a-6184-4456-88d7-e2101a5ace39 (vm-315)\MKDSRV07.domain.co.uk-flat.vmdk@E:\Veeam\Backups\Daily Backup2010-11-10T200046.vbk".Inc. backup: veeamfs:6:dc7dc32a-6184-4456-88d7-e2101a5ace39 (vm-315)\MKDSRV07.domain.co.uk.vmdk@E:\Veeam\Backups\Daily Backup2010-11-11T200033.vib].

Server error: End of file

I have done a search of the some of the key info and cannot find any similar posts.
Regards
Andy

[Vitaliy S.]

Hello Andy, for any technical issues please open support case directly with our support, as explained when you click New Topic. Thank you.

[Dannebrog]

Hello Andy, Did you get this problem solved ? We have same problem and reported to Support last week but no solution received yet.
Thanks
Jens

[Vitaliy S.]

Hello Jens,

Could you please tell if you have the same error for all your VMs or for some of them? Are those VMs located on the same LUN? Do you see this issue confirming?

I've just checked your ticket status, our support engineer is still investigating the log files, we will update you with possible resolution shortly! Thanks!

[Dannebrog]

Hello Vitaliy,

The error was for one VM with 4 virtual disks in differet LUNs. The problem was that the diskfiles on the different LUNs had the same name "server1.vmdk". After renaming the diskfiles using http://kb.vmware.com/selfservice/micros ... Id=1002491 the problem was solved.

I know that technical issues can be solved by opening support cases, but if Andy had stated the same solution here, I could have solved my problem faster and saved you guys some work. Now anyone with this problem can search in the forum and find one reason - equally named disks - and check that before reporting to Veeam technical support.

Brgds
Jens

[Vitaliy S.]

Hi Jens, yes - updating topic with a resolution is most welcome! So thank you for having enough time to post the solution that worked for you, much appreciated.

[Dude]

Hello Andy, for any technical issues please open support case directly with our support, as explained when you click New Topic. Thank you.

Like many other users I feel that this limitation of the forums is counterproductive. I can see how Veeam wants to keep technical problems from being posted as to limit the amount of negative publicity, but it is doing users a disservice since the community as a whole can often solve an issue significantly faster than tech support can (due to business hours etc.).

In addition, I came across this post because I experience the same issue, and possibly my issue will now be solved without that I need to submit a ticket and wait for someone to reply to it. I wish you would reconsider and let users post technical problems rather than try to hide those from the public.

[Vitaliy S.]

Hello Peter,

I understand your concerns, but please have a look at this topic to see the reasons why we've introduced these rules. Thanks.