Backup fails with error E00084AF
Backup fails with this error "The directory or file was not found, or could not ba accessed" This is happening for multiple directories. Directories exist and are accessible via Windows Explorer an...
Forum Discussion
It could be that your volume is corrupt.
Do a "chkdsk /f" on the volume to correct any errors.
Hi pkh, thanks for your reply.
The volume contains CAD-specific data which is being accessed on a daily basis and none of the relevant users are reporting problems of any sort so it's doubtful the volume is the cause of the problem.
Also, when the job fails, there are always differing directories which are reported as being the problem. I have run this job both in office hours and in the middle of the night to rule out file locks although the job is confgured to use VSS to avoid this regardless of the time it is run.
I have also tried using modified time vs archive bit and LTO tape vs disk storage, all with the same results. Other applications have no problems accessing the directories or the data they contain so this points to the problem lying with Backup Exec.
0xE00084AF The directory or file was not found, or could not be accessed.
You most likely have VSS problems.
Check the Application and System Logs right around the time you see the job log starting skipping files. Compare job log to Event Logs on the system being backed up.
Specifically VolSnap or VSS events.
Hi Steve, thanks for you reply.
I have searched the Event Viewer as you have suggested but have found no entries in the Application or System logs for VolSnap or VSS during the times of the job (screenshot attached - unfortunately I seem to only be able to upload one screenshot). Other jobs backing up from the same volume using VSS are having no problems so I would think it doubtful VSS is the cause.
I have run the job again and this time the error is different: 0x000fe36 - Corrupt data encountered.
Again, I must reiterate that we are as certain as we can be that there is no corrupt data in this volume. Users accessing this data on a daily basis have reported no problems and the data is accessible through Windows Explorer and the Backup Exec selection window in the job definition.
All evidence so far is pointing to Backup Exec I'm afraid.
