So I have this weird issue.
All the tapes are barcoded (and Veeam seems to recognize that).
but Veeam still issues this warning during inventory...
Am I missing something or ...?
ps. Do I have to re-add tapes to media pool? as they seem to be in unrecognized media-set (and the old ones they replaced in offline). how do match them together?
I am glad you finally get your tapes labeled Yes in order to read the meta data you need to perform a tape catalogue operation (inventory reads the header only). The confusing error might be a result of switching existing written media from blind mode to labeled. Any issues apart from the confusing warning?
Well, I can't tell you for sure now. So after cataloging I had to delete all the old offline tapes, veeam didn't match old and new tapes, just put new ones in the old media pool.
ps. I assume if I have only 1 media pool I can use only 1 drive? So to utilize 2 drives I need 2 media pools or more?
Just adding my penny-worth as a long-term MSL4048 and Veeam user...
Firstly, those alerts you were getting look like they were originating from the MSL rather than Veeam. Glad you got it sorted though.
Secondly, you are correct that to use multiple drives simultaneously with Veeam, you need multiple media pools/tape jobs. I believe that Veeam have this on their roadmap to address, but don't know when yet. Such an enhancement would be very welcome.
So for some reason barcode error went away. no idea. I did nothing. Just inventory (the error was there) then I started cataloging which didn't tell me that it failed to read barcode. go figure.
erm, so I guess my joy was preemptive... Now all the tapes are allocated to this media set, but they contain no backups. I tried cataloging them again, nothing changed...
every single tape looks like this.
It does recognize sequence number, but doesn't seem to recognize backups on the tape... and for some reason it is stuck on cataloging one tape for over an hour. it did catalog all the other tapes just fine.
It's high time to let support engineer take a look at your infrastructure as well as logs. It might be tricky to find out the root cause through the forum correspondence. Thanks.
So if anyone is wondering - the issue is a bit more complex then I initially stated. So I reinstalled Veeam to a new (this time physical) box. That was my plan regardless. So I installed update 2b. I tried inventorying\cataloging tapes. Some of them did catalog without issues, some of them took 20+ hours to catalog. I was told (by the support staff) that this issue (extremely long tape processing time) is known and there's a fix underway. So if anyone is wondering, I guess you have to wait for a fix. I will update the thread when\if I get it.