Backup Exec 12.5 - Varying errors causing failures

[jackylad]

Backup Exec 12.5 - Varying errors causing failures

Hi

I'm experiencing various issues when backing up a local server's data partition. 

This is a scheduled backup job that is set to run on a daily basis.  We have two jobs running; one backs up <dataserver> (which has the BE software installed on it) and the data on <mailserver>, and the second (which is working fine) backs up the mailstores on <mailserver>.  These jobs run in sequence.

The errors from the last 5 days are listed below:

Error             : e000e020 - The job was scheduled to run, but the availability window closed before the job could start. There may not have been any destination devices available during the window, or the job may have been submitted to run when the window was closed.

Error             : e000fe36 - Corrupt data encountered. See the job log for details.For additional information regarding this error refer to link V-79-57344-65078

Note: The backup is skipping over all of the data shares on <dataserver> and logging one corrupt file (this varies from backup to backup and isnt actually corrupt), and failing as a result.  AOFO is installed and configured to "automatically select open file technology" and "never" is set for the "open file backup when Advanced Open File Option is not used" setting as recommended in one of the suggested resolutions.

Error                  : e00084af - The directory or file was not found, or could not be accessed.

The file in question is c:\windows\system32\drivers\halfinch.sys

There doesnt seem to be any rhyme or reason for these failures which vary from day to day.  The tape drive has been replaced, and the backup jobs have been recreated various times to no avail.  Can anyone shed any light on this?

Cheers

[AmolB · Accepted solution]

For the 1st error check if there are any alerts in the alerts tab, the job may be requesting for a 

media and if there is no response then it may be failing with the above error.

For the 2nd error, Instead of "automatically select best technology" you can select 

the Microsoft VSS and snapshot provider as "System- Microsoft snapshot provider"

For the 3rd error check if that sys file exists at the given location

[jackylad]

Hi Amol, thanks for the quick reply.

The first error shouldn't be media related - the second job kicked off after that one and ran successfully on the same media that was to be used for the first.  I've changed the settings for the second error message.  I'll see how it goes tonight and post back with results.

Thanks again