cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec 2012 Backup Fail Due to (File was not found, or could not be accessed)

Sharath_Shashid
Level 4

Hi All,

Am new to this form

We are using Backup Exec 2012 to take Monthly incremental backup of laptops & Servers. The problem is in some laptops the backup fails due to the following error.

Final error: 0xe00084af - The directory or file was not found, or could not be accessed.
Final error category: Job Errors

Some Doucuments present in laptop are password protected. & the whole laptop HDD is encrypted with True-crypt.

Is their any way to skip the files which are in accessable/locked/encrypted.

The laptops are running on windows XP & 7. The backup is failing only on XP laptops.

Plz help me out on this cause lot of backups are Failed.

1 ACCEPTED SOLUTION

Accepted Solutions

pkh
Moderator
Moderator
   VIP    Certified

Edit the job and make sure that AOF is turned on.

If, even with AOF on, these files are inaccessible, then you would have to manually exclude them from the backup.  There is no way for BE to automatically exclude such files.

View solution in original post

4 REPLIES 4

pkh
Moderator
Moderator
   VIP    Certified

Edit the job and make sure that AOF is turned on.

If, even with AOF on, these files are inaccessible, then you would have to manually exclude them from the backup.  There is no way for BE to automatically exclude such files.

Sharath_Shashid
Level 4

Thanks for the fast responce..

As am new to backup. where is the AOF option. can u post a screan shot or post a full procedure. it would really help.

Sharath_Shashid
Level 4

I found AOF option it's enabled. will try to exculde the whole folder & check.

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

If that error message appares in the SWystem State part of the backup it may be nothing to do with encryption and also will not be solved with AOFO settings. You shouldd expand the section in the job log more fully to confirm which section of the backup errored.

There are times when software on the system registers stuff as part of the system state and at a later point in time the file related to that registration is removed withouth removing the registration.

 

Here is the Microsoft KB describing the same problem

http://support.microsoft.com/kb/955078

 

and a couple of KBs from us for similar issues

http://www.symantec.com/docs/TECH126412

http://www.symantec.com/docs/TECH60207

 

Please note that depending on the exact version of Backup Exec and the operating system being backed up, the exact error message may not always be the same. What is common is a failure during the system state part of the backup and the failure message (either in the job log or the debug log) references a file that no longer exists on the system.