D2D2T - Unknown Error Writing to Tape
I have a Iomega NAS 450R with a HP Ultrium 3 960 tape drive connected to it. When running backups from the NAS using BE 11D it works fine to disk. It also works fine to tape ever once in awhile. But then somedays my jobs all fail when writing to tape saying "An unknown error occurred on device "HP 1" V-79-57344-34029 - A hardware error occurred."
The only thing it says to do is update the device driver. I have tried the latest and second latest from Symantec. I have tried the last two releases from HP. Nothing Makes a difference. My jobs do not fail to disk and when they do write to tape I have tested the tapes and they are good. The only thing that I can think of is that BE gets confused if multiple jobs are waiting for the tape drive.
My backup jobs process as Job1 starts the d2d, and about half way throught that Job2 starts D2D. When job1 completes the duplicate job starts writing to tape while job2 is still going to disk. Depending on the timing job2 might be waiting for job1 to finish to tape and be sitting in a "Ready; no idle devices" Status. Again sometimes this goes without a hitch and sometimes Job1 will run and then Job2 will fail with the Unknown Error. Or Job1 will fail with Unknown Error and same with Job 2. Once I get the Unknown Error I have to restart the server and things seem to work fine for awhile. It is esecially frustrating when the job is 98% complete writing to tape then it errors out with an Unknown Error and I have to start the whole 4 hour job over again. I have flashed the tape drive to so it is current firmware and ran diagnostics on it and it passes.
I don't have much hair left as it is and this is making the little bit left disapear quicker.
Jeff H.
Comments
This is the BE Error I get:
Job ended: Thursday, February 28, 2008 at 8:20:49 AM
Completed status: Failed
Final error: 0xe00084ed - A hardware error occurred.
Final error category: Backup Device Errors
For additional information regarding this error refer to link V-79-57344-34029
This is the Event Log that I get:
Event ID: 33152
Adamm Mover Error: Write Failure!
Error = ERROR_IO_DEVICE
Drive = "HP 1"
{13E190B5-8F48-43C6-8AB6-0139201C4126}
Media = "LTO000004"
{B767777C-7A0F-4824-8643-0C3A8BA6D8B0}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
Event ID: 33152
Adamm Mover Error: Write Not Ready Failure!
Error = ERROR_IO_DEVICE
Drive = "HP 1"
{13E190B5-8F48-43C6-8AB6-0139201C4126}
Media = "LTO000004"
{B767777C-7A0F-4824-8643-0C3A8BA6D8B0}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
Jeff, have you received a resolution to your problem yet? I'm having the exact same problem with the exact same error messages. Just hoping that you've found a resolution. Thanks for any help.
Hi Jeff,
I'm having the exact same error message. The error only occurs during a duplicate job.
An unknown error occurred on device "HP 1".
V-79-57344-34029 - A hardware error occurred.
I have a Sun StorEdge C2 - which in fact is a Quantum Autoloader with an HP LTO drive.
The duplicate job runs with ~3700 MB/Min and after 80 to 110 GB the job suddenly stops and gives the above error message. After this the tapes are marked with several hard write errors. With the first tape I thought the tape is defect but this happened with every single tape we used. So I thought the tape drive itself was broken and we let SUN change the type drive twice! But this did not help either.
Then we tried another SCSI controller - without any difference.
The strange think is, that a backup job targeted to tape with 200 GB (just selecting 200 1 GB B2D files) runs without any problems. But this backup job does only run with ~ 2000 GB/Min. So the error might only occur with a higher transfer rate.
So I installed a second server from scratch and attached the tape autoloader to this server and tried the same job constellation with D2D2T. With this server the jobs where running without problems.
So I checked the original backup server and tried to find any differences. I downgraded the FC HBA for the disk drivers to an older state. I reinstalled the latest HP support pack and firmware (both are version 8.0.0). I already updated the drivers and firmware prior to the problems, but did not associate this with the backup problems.
So after 2 weeks of try and error I found the following posting with a comment about the HP insight agents: https://forums.symantec.com/syment/board/message?board.id=103&message.id=14331. So I decided to stop all the HP services and agents and then tried the duplicate again. And voila the job is running without errors. So it looks like that the current HP Insight Management Agents do cause some serious trouble during a duplicate job.
This might be helpful to you to.
Frank
Would you like to reply?
Login or Register to post your comment.