Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1018
  • Last Modified:

Symantec Backup Exec 2010 backups keep failing (refer to the attached job logs and support webpages). What can be done to fix this?

Symantec Backup Exec 2010 backups keep failing (refer to the attached job logs and support webpages). What can be done to fix this?

I have changed the backup destinations from being an internal tape backup drive to two different USB hard drives and then to an internal hard drive (drive F:) but the backup jobs keep failing with this exact same error.

Also, this server previously had Symantec Backup Exec 12.5 installed and I would always get these same sort of backup failing messages. Then I upgraded to Symantec Backup Exec 2010, and the backups still continue to fail in the exact same ways.

I believe that the Symantec Backup Exec backup jobs are failing not because of the destination to where the backup data is being written, but rather because the data source is itself corrupted or unable to be read.

Every time that the backups take place, they always backup up to a certain point (there are usually 30 or so 2GB Symantec Backup Exec backup files that are created) and then the backups completely halt with these error messages.

The problem is that the backup job reports and logs are so vague and difficult for me to interpret that I don't know exactly what needs to be done in order to fix these backup problems so that the  Symantec Backup Exec backup jobs will complete without any problems.

What can be done to fix this?
The-device-cannot-be-found.png
Job-Log-BEX-LUCAS01-01473-xml.mht
Job-Log-BEX-LUCAS01-01474-xml.mht
The-error-message-0xe000fe1f---T.mht
Enterprise-Support-Advanced-Know.mht
0
IT Guy
Asked:
IT Guy
1 Solution
 
Stephen CroftTechnical ArchitectCommented:
ok - start from the beginning.

Backup a single folder of about 200mb to a Backup To Disk folder that is newly created.

Does that work?
0
 
Dunedan79Commented:
I would suggest 2 things.

As your error notice suggested, disable AOFO for the Exchange backup. If necessary split out the Exchange backup to a separate job.

Try selecting the WSUS share it keeps failing on through the administrative share and drill down, as in from the C: drive or such. That takes possible share-level permissions out of the equation.
0
 
IT GuyNetwork EngineerAuthor Commented:
Resolved the issue by removing WSUS from the backup job list and by enabling Advanced Open File Option.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now