-
- Novice
- Posts: 6
- Liked: never
- Joined: Nov 10, 2016 3:37 pm
- Full Name: Casey
- Contact:
Tape fatal error
Hello,
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.
Our setup:
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.
Thanks!
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.
Our setup:
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.
Thanks!
-
- Product Manager
- Posts: 14732
- Liked: 1708 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Tape fatal error
Hi Casey,
What VBR version are you using?
What VBR version are you using?
Have you tried to delete (or at least to disable the application), to ensure that it's not interfering with Veeam tape jobs?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.
-
- Novice
- Posts: 6
- Liked: never
- Joined: Nov 10, 2016 3:37 pm
- Full Name: Casey
- Contact:
Re: Tape fatal error
9.0.0.1715 - I am about 95% sure these errors started after updating to this version.
Yes I have uninstalled Backup Exec from the server.
Thanks
Yes I have uninstalled Backup Exec from the server.
Thanks
-
- Expert
- Posts: 221
- Liked: 48 times
- Joined: Nov 27, 2015 2:26 pm
- Full Name: Konstantin
- Location: Saint Petersburg
- Contact:
Re: Tape fatal error
Hi, Casey. Just in case. Maybe your tape drives require cleaning? Dirty tape heads may be the cause of such errors.
-
- Novice
- Posts: 6
- Liked: never
- Joined: Nov 10, 2016 3:37 pm
- Full Name: Casey
- Contact:
Re: Tape fatal error
We have cleaned the drives and the errors still exist
-
- Product Manager
- Posts: 20423
- Liked: 2306 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Tape fatal error
Then, kindly, keep working with our support team. Deep logs investigation should shed some light on the root cause of this problem. Thanks.
-
- Influencer
- Posts: 18
- Liked: never
- Joined: Oct 01, 2013 11:46 am
- Full Name: hakimbhungra
- Contact:
[MERGED] Backup to tape failed
Dear Support,
One of our backup failed with below error.
Veeam Backup & Replication 9.0
Regards,
Hakim. B
One of our backup failed with below error.
Code: Select all
BackupSrvFileToTape failed Tape fatal error. The system cannot find the path specified. Tape write error Exception from server: Shared memory connection was closed. Tape fatal error.
Regards,
Hakim. B
-
- Product Manager
- Posts: 20423
- Liked: 2306 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Tape fatal error
Hi, Hakim,
As stated, these are not support forums. So, it might be worth reach actual support engineer to get assistance.
As the first investigation step, though, it stands to reason to update backup server to the latest product version and check whether it's time to clean drives.
Thanks.
As stated, these are not support forums. So, it might be worth reach actual support engineer to get assistance.
As the first investigation step, though, it stands to reason to update backup server to the latest product version and check whether it's time to clean drives.
Thanks.
Who is online
Users browsing this forum: No registered users and 8 guests