04-30-2008 07:48 AM
04-30-2008 11:13 AM
04-30-2008 12:23 PM
05-01-2008 06:47 AM
05-16-2008 08:07 AM
Dell PowerVault TL4000 (2 Full height LTO4 SAS drives)
Symantec Backup Exec 12 Rev. 1364 (SP1 & Hot Fix 300831 Installed)
When it was working I would get alot of these errors in the App log:
Event Type: Error
Event Source: Backup Exec
Event Category: Devices
Event ID: 33152
Date: 4/22/2008
Time: 1:06:22 AM
User: N/A
Computer: FACBK
Description:
Adamm Mover Error: Read Failure!
Error = 0xE0008121
Drive = "Tape Drive 2"
{AFA6C4F5-4F47-49C3-B630-C1C86CFF4C07}
Media = "000018L4"
{BDD3DF5D-01C7-41AA-B6B6-472AA763253B}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
--------
Bill
07-31-2008 03:49 PM
11-25-2008 06:40 AM
bump
I am having the same errors described here - and this was the only search result that came up in Google. I have almost exactly the same setup too - Dell PE 2950 server attached to a Dell ML6020 tape library with 4 SAS LTO4 tape drives. I am running the most current versions of everything - I updated firmware in the library and drives, updated drivers, etc on my BE environment.
But as soon as I turn on hardware encryption, I start to get the 33152 errors. My jobs complete OK. But - since turning on encryption - the job engine crashes on my weekend jobs several hours into the backups. The only way to recover everything is to stop ALL BE services, power cycle the tape drives, then restart the BE services.
I'm quite sure this is all related - if I turn off encryption, then everything runs smoothly. I ran into this same problem about 2 months ago and when I turned off encryption, everything has run perfectly fine. The first time this happened, I discovered that if the tape drives are not reset - then they fail to recognize the tapes properly (the Media ID read from the tape doesn't match what BE has in its database), and tapes are moved into Retired Media - and I lose all ability to use that tape. Resetting the tape drives resolves the issue.
I opened a support issue with Symantec and they told me that there was no way the encryption had anything to do with this condition.
So despite the 33152 errors I am fortunately able to get successful backups and restores, and after the job engine crashes as long as I reset the tape drives, then I'm OK - but it is very annoying to have this condition and having to nurse my jobs constantly to make sure they all restart OK after each job engine failure. Disabling encryption is not an option as we are required by our clients to encrypt ALL tapes. Hoping for a fix soon!