• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 687
  • Last Modified:

Backup Exec 12.5 very slow to tape after OS re-install

I had to re-install windows 2008 32bit on my server to fix iSCSI issues I was having. I then re-installed Backup Exec 12.5, Sp3 and all patches. Disk backups work fine, but the weekly tape that picks up from disk has dropped from 1,500mb/min to 5mb/min! Symantec support has been useless...we've re-installed the Adaptec Ultra 320 drivers, tried both the updated symantec and HP drivers for the tape drive...nothing seems to help...very frustrating. Fix one issue and break something else. It has to be a driver issue or software setting since none of the hardware has changed. Robotic library is an Arcvault 24 LTO4. Connected via SCSI cable, running backups locally on the media server where our disk backups are stored, so no network involvement.
0
nocalerts
Asked:
nocalerts
  • 2
  • 2
1 Solution
 
dovidmichelCommented:
ck to see if the Adaptec controller is sharing an IRQ with something else.
if there is anything else on the Adaptec remove it and try it again.
verify the Adaptec bus is still properly terminated.
0
 
nocalertsAuthor Commented:
Not seeing any conflicts, maybe I'll remove the SCSI card and re-add it just to see what happens.
0
 
dovidmichelCommented:
I'm sure you have tried different tapes.

I'm an expert with tape but not with BE itself, so I can't tell you where to look but I'm assuming that either under the database device info or reports it is possible to check for soft or recovered errors. These are failures to write data which after retrying it works. Because it eventually wrote the data the job does not fail, but each time it happens throughput suffers. LTO should not have any of these, so if there are time to ck with hardware support.

Don't bother cleaning the drive, LTO drives should be cleaned only when the drive requests.

Start the job and monitor it to see if the throughput starts out high and then goes down and down.

Try a backup to tape but of different data, different data local to this system and also data residing on another system. Could be the problem is related to moving data off the source volume.

Speaking of which the % of free space and fragmentation on the source volume.
0
 
nocalertsAuthor Commented:
Threatened Symantec and got a 2nd tier support engineer that helped me fix the issue, removing all devices and drivers and then installing fresh did the trick.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now