?
Solved

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

Posted on 2010-08-20
3
Medium Priority
?
1,012 Views
Last Modified: 2013-12-01
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
Comment
Question by:Knowledgeable
3 Comments
 
LVL 11

Expert Comment

by:Stephen Croft
ID: 33486722
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
 
LVL 5

Expert Comment

by:Dunedan79
ID: 33513499
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
 

Accepted Solution

by:
Knowledgeable earned 0 total points
ID: 33547343
Resolved the issue by removing WSUS from the backup job list and by enabling Advanced Open File Option.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
Suggested Courses

569 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question