We help IT Professionals succeed at work.

Backup Exec 2010 - The directory or file was not found, or could not be accessed.

slipy120
slipy120 asked
on
Hi all,

I am getting an error Backup Exec 2010 - The directory or file was not found, or could not be accessed when trying to perform backups.

Server log only reiterates the above error. The job log does not tell me what server or file is causing the issue. The only error I get is "Final error: 0xe00084af - The directory or file was not found, or could not be accessed."

Backing up a total of 8 servers, mix of server 2003 and server 2008. Any help would be appreciated.
Comment
Watch Question

IT/EE Solution Guide
Commented:
Increase the job log level to log the files and folders it is not able to locate or access.Re-run the job and post the error please as there can be different reasons for the specified error.

Default job log options
http://www.symantec.com/docs/HOWTO22361

Author

Commented:
Increase the job log level to log the files and folders it is not able to locate or access.Re-run the job and post the error please as there can be different reasons for the specified error.


Ok, I have done that. Will not be able to see results for 24 hours. I will post them then.
It may just be that a file or folder explicitly selected in the backup specification no longer exists.  The logs will tell.

Author

Commented:
Had an issue with the media for the backup overnight, cannot do manual during operation hours. Will do tonight and post results.

Author

Commented:
Made the changes and attempted backup last night, still the error does not specify what directory or file was not found. Error is as reads below:

Job ended: Thursday, March 26, 2015 at 6:36:16 AM
Completed status: Failed
Final error: 0xe00084af - The directory or file was not found, or could not be accessed.
Final error category: Job Errors

For additional information regarding this error refer to link V-79-57344-33967
Iamthecreator OMIT/EE Solution Guide

Commented:
Could you please attach the job history and the job logs here.

Author

Commented:
Ok, before I do that I noticed in exceptions a warning.

WARNING: "EC-DB1\ECMSQLSVR\ECOEHRTEST" is a corrupt file. This file cannot verify

Would that have thrown off the backup? It did not show as an error, but under exceptions.

Edit: Looking at back logs, the last successful backup did not show the warning where the first failed backup did.
I wouldn't expect a corrupt file to give the error you cited in your original post, but then again, it wouldn't be the first time that an error message was poorly crafted.

So the file is something to do with SQLServer.  Do you have agents for SQL backups licensed in Backup Exec?  If not, do you quiesce the database before running a backup? (if you don't either have the SQLServer Database agents or quiesce the database engine, you may get a backup, but odds are you won't be able to get a successful restore)
Iamthecreator OMIT/EE Solution Guide

Commented:
When it reports an error it does not mean that it failed to backup up any of the data.Uncheck the corrupt files in the selection list and that should fix the issue if it persists create a new selection list.In the job logs it also reports the amount of data that has been backed up.

Author

Commented:
It was just a test database,  we removed it and will see what happens with the full backup over the weekend. I am fairly confident that this may have been the issue as the backups only started failing once this error was thrown out by backup exec.

Author

Commented:
Ok, over the weekend the job failed with the following error: "Saturday Full -- The job failed with the following error: Corrupt data encountered. See the job log for details". The log file is too large to view after I have increased job log level. Will wait for differential backup to view log.
1) Have you run chkdsk on the volume?
2) Do you have correct agents licensed and installed for Backup Exec to backup live databases?

Author

Commented:
1) Have not recently run chkdsk
2) Yes, all agents are the correct type

After an unsuccessful Full backup, the daily differential backups are going through and the error about corrupt data is gone. I think I am going to mark this as fixed.