BackupExec failing after 3-5 Minutes with error code E00084F4

Question

Environment

• Server: HP ProLiant DL320s G1 (System ROM: W04)
• O/S: Windows 2003 R2 x64 SP2
• Autoloader: HP 1x8 G2 AUTOLDR (Firmware: 2.50 / 2.00n)
• Drive: Ultrium 3-SCSI (Firmware: D22W)
• SCSI HBA: HP SC11Xe (Firmware: 01033900)
• BackupExec: 12 SP3 Single Media Server

There is approximatly 500GB of direct attatched storage that is backed up in full every night off this server; 1 box solution files and BEWS on same server. No databases or exchange just files on a NTFS partition, the backup was working flawlessly every night for about a year, then it stopped working and fails with the following information.

Job ended: 30 July 2009 at 19:03:43
Completed status: Failed
Final error: 0xe00084f4 - An unknown error has occurred.
Final error category: System Errors

Backup- D: DataStorage device "HP Drive" reported an error on a request to write data to media.
Error reported:
A device attached to the system is not functioning.
V-79-57344-34036 - An unknown error has occurred.

Following the links in the job log fail to provide any steps that haven't been tried before. Support personel from both HP and Symantec have remoted in to have a look and try various different things, we have replaced the HBA, SCSI Cable (HP RMA), Internal Drive (which was reporting numerous soft failures - HP RMA) and the SCSI terminator (HP RMA).

I have tried the following recently:

1. Install the latest ProLiant support pack which includes the upgrade to HP Managment Agents.
2. Install the latest tape drives from Symantec.
3. Checked the login account, is Domain Admin, is specific to BackupExec, is not locked out.
4. Tried starting the job from BEWS using the BackupExec account
5. Installed latest StorPort driver from Microsoft

I am at my wits end, not sure what to try next, beyond asking HP to RMA the whole AutoLoader.

Solution

Check to see if http://seer.entsupport.symantec.com/docs/305233.htm (and seer.entsupport.symantec.com/docs/312076.htm) solves your issues.

I just installed a server with Backup Exec, and fought this problem for some days before finding the above. Ended up removing all HP software from the server (except L&TT for testing). Overkill for sure, but when I again have a full current backup I will try reinstalling some of the software to find the cause.

I have since found forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1249042181937+28353475&threadId=1213970 and forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1158447 that seems to describe this issue.

Regards,

Kaj

Comments

[Richard Slater]

I updated the firmware 6 weeks back, I am going over everything again see if there has been another update. BackupExec full is installed on the box. Media set is displayed, the problem is not specific to BEWS; a similar failure (with a different message) occured when HP installed their own software.

[Admin]

"a similar failure (with a different message) occured when HP installed their own software" and they didn't offer to RMA the whole unit right there? Surprising. The software they installed, did it bypass all other HP software then? Talked directly to the autoloader?

[Richard Slater]

It was Data Protector Express: h18006.www1.hp.com/products/storage/software/datapexp They RMAed the drive (customer replacable unit), the SCSI cable and the SCSI terminator. Technically the Auto-Loader is a seperate device only responsible for identifying and loading a tape into the drive, so failures after the drive has been loaded are unlikely to be anythign to do with the Auto-loader itself.

[Richard Slater]

I am not sure I quite believe it but, that seems to have done it. I have had three successful backups after installing the WMI provider. Thanks.