We implemented BE 2010 R3 (fully patched) on W2K8R2 in combination with VMware 3.5u4, Hitachi AMS500 FC SAN.
Policy is backup2disk2tape (lto5)
We use the SAN based transport mode for our VM backup.
All works fine, but randomly for some VM's we receive the error message for a particular disk:
Transport mode 'san' was used for the disk 'NLLISDB03_6.vmdk'
Transport mode 'san' was used for the disk 'NLLISDB03_4.vmdk'
Error writing file data
Transport mode 'san' was used for the disk 'NLLISDB03_3.vmdk'
Transport mode 'san' was used for the disk 'NLLISDB03_1.vmdk'
Transport mode 'san' was used for the disk 'NLLISDB03.vmdk'
Backup Exec has discovered and protected 'C:' on virtual machine '\\NLLISDB03.bakkernet.biz'.
Backup Exec has discovered and protected 'D:' on virtual machine '\\NLLISDB03.bakkernet.biz'.
Backup Exec has discovered and protected 'E:' on virtual machine '\\NLLISDB03.bakkernet.biz'.
Backup Exec has discovered and protected 'P:' on virtual machine '\\NLLISDB03.bakkernet.biz'.
Backup Exec has discovered and protected 'Q:' on virtual machine '\\NLLISDB03.bakkernet.biz'.
Backup Exec has discovered and protected Microsoft SQL Server data on virtual machine '\\NLLISDB03.bakkernet.biz'.
At the Job Completion Status it says:
Final Error: 0x2000fe07 - FS_NO_MORE
Strange thing is that all the 5 disk seem to be protected...?
For a couple of days it concerns the same VM, same disk that has an error.
Then suddenly one server does not give the error message, but a few servers remain with the error.
I tried to find the solution at the SAN/LUN/VMFS level, but I don't see a link when I compare all the failed vmdk's..
Anyone that can put me in the right direction?
