Hi,
I have one IBM TS3200 Tape Library previously configured for Backup Exec. We replace backup exec with Veeam 7. When I try to run "Iventory Library" function it loads its first tape to tape drive and starts Invetoring the tape. However it fails to load subseqent tapes and spits out error saying "Failed to Inventory Tape xxxx(BarCode) Error: Cannot find tape drive[address: 0]. If I try to inventory individual tapes job comples successuflly. Also when I schedule backups spanning more than one tape.. job completes successfully. Bit confused with this error. Please help.!!!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 13, 2013 7:45 am
- Full Name: Sam Alwus
- Contact:
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: IBM 3200 Tape Library Invenroty Problem
Hello Sam,
Could your error be related to tape library drivers, like it was in this very thread? Anyway, have you already opened a support case with our technical team for further investigation and logs review?
Thank you!
Could your error be related to tape library drivers, like it was in this very thread? Anyway, have you already opened a support case with our technical team for further investigation and logs review?
Thank you!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 13, 2013 7:45 am
- Full Name: Sam Alwus
- Contact:
Re: IBM 3200 Tape Library Invenroty Problem
Hi Vitaliy,
Thank you very much for the quick response. I also installed "exclusive driver" as specified in the thread. First I will try chanding this driver to Non Exclusive and give it another go. This migh fix my issue. So far I have not opend up a support case because I was under the impression that this error pops up due to a misconfiguration... If it still does not work after installing the "Non Exluisive Driver" I will open a support case.
Once again thank you very much.
Sam
Thank you very much for the quick response. I also installed "exclusive driver" as specified in the thread. First I will try chanding this driver to Non Exclusive and give it another go. This migh fix my issue. So far I have not opend up a support case because I was under the impression that this error pops up due to a misconfiguration... If it still does not work after installing the "Non Exluisive Driver" I will open a support case.
Once again thank you very much.
Sam
Who is online
Users browsing this forum: No registered users and 8 guests