Backup Exec failing friday Full backup

[woreilly]

I am having some issues with Backup Exec 12.5 backing up to my school's NAS device. The schedule has a Full Friday backup with a Differential running Monday to Thursday. It keeps failing the weekly friday backup and Backup Exec is being very helpful giving me the following error:

 

E00084f4 - An unknown error has occurred. For additional information regarding this error refer to link [insert generic link here]

 

Backup exec is a horrible piece of software to use, especially on Server 2003 (the school's head isn't a fan of spending large amounts of money so it was a struggle to move them away from a tape drive, let alone spending money on a better piece of software). I was wondering what people's experience was with the BUE error and what they have done to combat it and if anyone has any general ideas as to what might cause it or give me ideas on what i can check?

 

It works perfectly fine doing the differentials Monday to Thursday. Am I better off using NTBackup to go to a NAS device?

FYI, it is a 6TB QNAP mapped by iSCSI to the server which as mentioned earlier is 2003 with 32-bit Windows 7 clients.

[hallb15]

Backup Exec has gone through many versions, some were great, but most had so many quirks and issues that I stopped using it several years ago.

 

Most of the problems I encountered were due to permissions and the various agents that had to be installed on each server to be backed up.

What account are you running the backup jobs under? Even though it works for other backup jobs, you could try creating a new domain admin account and using that to run the backup job that is currently failing.

[woreilly]

Backup Exec has gone through many versions, some were great, but most had so many quirks and issues that I stopped using it several years ago.

 

Most of the problems I encountered were due to permissions and the various agents that had to be installed on each server to be backed up.

What account are you running the backup jobs under? Even though it works for other backup jobs, you could try creating a new domain admin account and using that to run the backup job that is currently failing.

 

I am using good old administrator

[hallb15]

I am using good old administrator

Local admin or domain admin? Gotta be domain admin.

Are you backing up more than one server using agents? These were often the cause of my issues with Backup Exec.

 

For a full backup to NAS, Windows Server Backup does a pretty decent job and would at least give you some peace of mind that you had a backup in place whilst you sort out your Backup Exec issues out. It can take ages though, so make sure you schedule it for a quiet time when no other backups or important tasks are scheduled...

[woreilly]

Local admin or domain admin? Gotta be domain admin.

Are you backing up more than one server using agents? These were often the cause of my issues with Backup Exec.

 

For a full backup to NAS, Windows Server Backup does a pretty decent job and would at least give you some peace of mind that you had a backup in place whilst you sort out your Backup Exec issues out. It can take ages though, so make sure you schedule it for a quiet time when no other backups or important tasks are scheduled...

 

I'm using domain administrator. It is a tiny primary school so they only have 1 server which is nearly 4.5yrs old (due for replacement in Summer 2015) and running 2003. My limited experience tells me WSB is not available on '03 - NT Backup being the MS solution.

 

I am just trying to backup the essential folders of data/documents and system state.

[woreilly]

Is it possible that an NTBackup schedule can interfere with Backup Exec therefore causing the backup to fail?

[bossman]

@woreilly:

 

Have you tried the usual suspects: http://www.symantec.com/business/support/index?page=content&id=TECH38608

 

BE 12.5 SBS Premium - Jobs fail with E00084F4 Unknown Error | Symantec Connect

 

Backup Exec 2010 Weekly job failure, error code: E00084F4

 

Hope you find it amongst this lot

 

BE 12.5 has been one of the more stabler versions, I too get the odd problem with the full weekly backup but not this error mine has to do with the Autoloader a I still haven't resolved yet which is most annoying but as it completes the backup to disk function first I still have a respective backup.

 

Good Luck