Well, finally after days of endless backup jobs failing, I opened a support call this morning. After about 2 hours and getting my call to second level support still nothing. Symantec is blaming Microsoft Volume Shadow Copy Service. But I disagree because with the remote agent turned off, I am able to perform an NTBackup on the system (which I believe is a good test because NTBackup uses VSS).
If I do a vssadmin list writers prior to BackupExec 11 D running - all writers show it a stable state.
Then I run the vssadmin list writers AFTER I try a BackupExec 11 D job, some of the writers are showing in a failed state.
At this point, I had to open up another call with Microsoft to prove that VSS is not the issue.
This is getting to the point, that I think I am done with Symantec BackupExec 11 D because it just does not work in my environment. I am hoping that Microsoft and Symantec will find the cause.
I will keep everyone posted in my journey.
Maybe Version 12 will resolve this issue?