The drive hardware is offline€ Backup failed

[anakonda]

Hardware Description:

HP Proliant DL 380G5
HP MSL 2024 (Tape device)
HP MSA 60 RAID 5 HP Smart Array p800

The Smart Array P800 was defect.
The array was replaced by HP

After this repair fail all backups except 1

Job Description:
There are 6 jobs 3 duplicates and 3 jobs to MSA and MSL

The first job (185 GB to MSA) completed successful.

After this job starts another job which backups the entire servers to MSA.

During backup the job stops by counting of 45 GB and display a message Device is offline.

I have followed the following support documents from Symantec:

http://seer.entsupport.symantec.com/docs/252381.htm

http://seer.entsupport.symantec.com/docs/191158.htm

http://seer.entsupport.symantec.com/docs/252385.htm

http://seer.entsupport.symantec.com/docs/255501.htm


But the backup still fails

[anakonda]

after the server restarts I get this message:

bengine.exe hanging.
There was an error in Backup Exec Job Engine.

[DarrenW]

A few things spring to mind.

Are the SCSI id's the same since the controller was replaced?
Are the Backup To Disc folders online and working? And can you backup anything to them using, say, a brand new test job?

What does the eventlog say about the bengine.exe errors?

[thegoolsby]

The 4 technotes you mention deal with troubleshooting tape drives, but you mention the MSA is failing? Are the failing jobs running to the MSA or MSL?

If the MSL has the hardware errors, did you perform Step #4 from http://support.veritas.com/docs/255501 ?  It so, did you see any noticible errors in the hardware trace? For more information on tracer see http://support.veritas.com/docs/285630

If it is the MSA that is reporting the 'device is offline,' have you checked to see if you are getting any errors in the event logs regard write failures or timeouts when writing to the disks? If the MSA is attached locally to the Media Server, have you tried enabling write back caching on the disks?

Can you try to backup to a volume other than this MSA to see if the problem is with this device or not?

Do all of the jobs also fail at the same 45 GB mark every time?

Also, make sure that the Backup Exec services as well as System Logon Account are all set to use a full administrator account.

-Collin