I had a customer open a case with Tier 1 Support recently, Case 01857771, and he was configuring his AWS Gateway as well as a VTL, and the suggestion to delete the drivers and use the Native SCSI Command Setting didn't fix the barcode issue for him.
He ended up re-installing the driver and then also enabling the Native SCSI Command setting and this allowed the barcode to show, but not all characters. It shows 8 characters but it should show 10 characters. He also has a prefix for the barcodes set and I suggested removing characters from this prefix so the total characters is 8 instead of 10, but I'm not sure if this is his only option to get the barcode to show correctly.
Has anyone using AWS as a VTL seen this issue or if you use the barcode prefix at all without issue of that showing correctly in Veeam?