Network backup gives CRC error

[cjkenworthy]

I have been looking at previous posts here to fix my problem and still can't. I am getting the ever popular:

Error reported:
Data error (cyclic redundancy check)

^ ^ ^ ^ ^

So I have tried all suggestions including drive cleaning, new tapes, even a new drive, re-installing Veritas Backup Exec itself. When backing up our 6 servers across the LAN I recieve this error. *HOWEVER* - if I ONLY backup the media server (that the drive resides on itself) then it works perfectly - it is only when I add the other servers on the LAN to the backup.

Also the drive passes all of Compaq's diagnostics perfectly, and Microsoft Backup uses the drive fine aswell. Have reinstalled drives, updated firmware and Veritas's own drivers. Have tried doing backups with Veritas drivers, then with the drives own drivers. Still recieve error.

Specs:
- Backup Exec version 8.6 for Windows NT/2000 servers
- OFO and Remote agents on all servers
- NT4 (Sp6a) domain
- Compaq servers with AIT 50 Sony SDX 500 SCSI drive

 

[packdragon]

That's a lot of work you've gone through! Very frustrating indeed. The only thing I can think of to check is the network card. Verify that updated and accurate drivers are installed for it, and if that doesn't help, try a different NIC that is known to be functioning correctly.

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[cjkenworthy]

Surely if the NIC was not working, then I would see this in other applications other than Veritas - as this server is also a file server.

 

[packdragon]

If you say so. It's just one of the things Veritas tells you to check, and you've checked everything else, right? That you can back up the local drive just fine and get the error when you try to back up across the network seems to indicate the possibility of some sort of network problem. Besides, Backup Exec is a lot more complex piece of functionality than file serving. But anyway, you do what you want. It was just a suggestion.

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[suprecky]

have you tried doing it without OFO turned on.

Also are they servers on the same segment ? DNS working ok ? add remote servers to host file.

update to latest build.

Push the remote agent install to the servers again...

run c:\pf\veritas\bkupexec\nt\sgmon.exe and select bserver and bengine and capture to file, it will give more information on why its failing.

hope this helps.

 

[AustinPowers]

Hi,

I have same problem, but running Version 9.0. I've tried pushing the remote agent again, but always failed for whatever reason. I had to manually install RANT32 on the servers after updating to latest build 4454.

I also try HOTFIX2, but failed everytime with installation program complaining process was interrupted before finishing and reverting back to 4454. I thought Veritas BE is very flaky. Updating procedure is mediocre.

In my situation, backup mostly ran for a couple of Gig before returning with CRC. Support says drive could be contaminated (is this typical with DLT VS80?)! I wonder what else can be done besides cleaning drive? howabout demagnetize? Air Blow?

TIA,
AP

 

[cjkenworthy]

A compaq engineer came out and gave us a third new drive, but he had a tinker with all of the cables and looked at the contacts and terminators.

We ran a backup and it passed.

I am going to run 3 or 4 over the next few days and really hammer it to test whether or not the CRC errors return.

things to try are:

-SCSI card transfer speed
-Driver/firmware updates
-Drive manufacturers own diagnostic tools
-Reinstall veritas
-Silent/manuial reinstall agents on servers themselves
-Run isolated backups on local server vs remote servers
-Check all cables and connectors
-With Veritas, it is rarely the tape that is the problem