VSS error e000fe36 - data is corrupt

[TennIT]

I have upgraded to BE version 12 because of numerous errors using version 10 and 11d.  The continuing error are random VSS errors.  They don't occur every day.  I may run the same job today and it complete fine, but tomorrow it will get VSS error.  The link V-79-5733-65078 says its because Advanced Open File option isn't installed, but obviously, if it works 4 days in a row, that isn't the problem.  It only occurs on my file server (not on exchange or blackberry) and it does not matter where I am writing the backup to (sometimes I backup to NAS, sometimes to a local device).  I can't seem to find any other information on how to get this corrected.  Any help is appreciated.

[Dev_T]

Hi,

http://support.veritas.com/docs/258696

http://support.veritas.com/docs/289559

Regards

Dev T

[SteveGill]

Hello,

I get a similar problem  - have just upgraded our backup server to win2k8 and installed BE12 with an upgraded BE11d database (so same jobs and settings). BE12 insists on using VSS even though it is told to "never" (i.e. skip) inuse files and AOFO is turned off on the jobs.

Once the job reaches the so called corrupt file and then all files and directories (in alphabetical order) afterwards are skipped (Access denied) because they could not be found. Our BESR backup jobs to this backup server are running continuously and it seems to happen when one of these in-use files is found.

The errors in my log include (all from same job log)

WARNING: "E:\mehsl1\MEHSL1_E_Drive056.v2i" is a corrupt file.
This file cannot verify.
The item E:\mehsl1\MEHSL1_E_Drive056_i007.iv2i in use - skipped.
V-79-57344-33928 - Access is denied.
Access denied to directory mehsl2\.
Directory E:\mehsms was not found, or could not be accessed.
None of the files or subdirectories contained within will be backed up.
Directory E:\mehsmscomp was not found, or could not be accessed.
None of the files or subdirectories contained within will be backed up.
V-79-57344-33928 - Access is denied.

V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes ...

Can post complete log if required.

Thanks,

Steve