I'd like to add my voice to getting the missing barcode issue looked at in an upcoming patch, rather than waiting for a full release.
We're just completing a full POC for using Veeam and archiving to AWS (as a replacement for Symantec BE and tapes). It's been a long assessment and has included waiting for the new V8 Veeam servers and test build for both AWS storage gateways (Volume gateway and VTL gateway). The later giving us greater control over large media sets and archival control into Glacier.
Everything was looking fantastic - right up until the end when I've gone to recover a tape and realised there was no way to identify "Tape x" with the barcode on the archived tape.
Your suggested workaround is NOT a viable option; I have for example 5 tapes needed per month, but there is no way to identify which ones are which. It limits the creation to 1 tape at a time, which then need to be imported and manually renamed. Whilst I could created fewer (but larger tapes), to ease this overhead, it goes against the benefits of granularity in storage and recovery.
- Is there a better way to create and rename multiple tapes?
- Perhaps there is an alternative/updated driver that can be used? Blaming the limitations on your channel partners (that you've chosen) is not really good enough.
- Perhaps you could provide a patch?
We are 99% satisfied with our POC, but the 1% is a massive failure.