We moved to Veeam back in July from Backup Exec. Everything was going along smoothly, running jobs to disk, and dup to tape until September when all of the sudden we started getting Tape Errors on random jobs. The error is:
BackupSrvFileToTape failed Tape fatal error. Data error (cyclic redundancy check). Tape write error Exception from server: Shared memory connection was closed. Tape fatal error.
Setup as follows:
Veeam server, Win 2012 R2
Overland Library 400s
3 LTO 6 IBM tape drives connected to the Veeam server via fiber
Data is being moved from our repository that also hangs off our Veeam server via fiber
We have tried new tapes, old tapes that were used with Backup Exec, long erasing, short erasing but at least once a week we get the above error on a random tape job. If we start the job again with a different tape 9 out of 10 times it will finish. But now, we have one job, 3.1 TB in size of vbk file on disk that I have tired 3 times over the last 3 days and it fails approx. in the same spot in the job each time. 1.8 to the 2.0 TB mark each time with the same error above. The job will be cruising along at over 100 mb/s, then it will hit that magic mark of 1.8 to 2.0 tb, drop down to 2ish mb/s and will eventually fail. Overland marks the tape as bad and then Veeam spits out the failed email. Again, tried old tapes, new tapes, long erase, short erase same result.
Firmware for the library and drives are up to date. I have tried the latest non-exclusive drivers from IBM and as well as the drivers Veeam support recommended.
I have a case open with Support (01972124) but so far the only suggestions have been remove Backup Exec from the server (had it installed and services shut off in case we needed to restore something from tape pre-Veeam) and reboot your server.
Any suggestions or thoughts would be greatly appreciated.