TapeMediumSortByUsageStatistics not working in V12

[snakeyes1000]

The registry value TapeMediumSortByUsageStatistics=0 no longer seems to work in V12.... It keeps pulling the highest barcode numbered tape instead of the lowest. I.E. I want it to pull tape 76L9 first, but it pulls 85L9 instead. Sometimes it might pull 76L9 (slot1) first, but then it will pull 85L9 (the highest alphanumeric from slot 7) when it needs the next tape, instead of 77L9 (slot2). Is there a way to force it to pulling from Slot number order instead?

Anyone else having this problem!? It is driving me nuts!

[david.domask]

Hi @snakeyes1000, I'm afraid I cannot reproduce in my lab. While I am sure that it took the tapes in the order you listed, I'm not sure it's due to the registry value itself.

Can I ask you to export logs for the affected job using https://veeam.com/kb1832 (use the 1st option, select the tape job) and note which date/time the tape job took the tapes in unexpected order?

> Is there a way to force it to pulling from Slot number order instead?

Not at this time, no.

[vgisit]

Hi,

I also have been dealing with this issue for some time and have had an open case with Veeam support for some months now. I too have been tearing my hair out !
In our situation what we have found the order of the media set # will override the tape barcode order.
It was fine initially when we used a monthly cycle of new tapes and ascending barcode numbers corresponded to ascending media set numbers, but once this order was messed up by someone erasing some tapes in the cycle it stopped working as one would expect.

@snakeyes1000, were you able to get any firm conclusions here ?
Regards,

Vic

[david.domask]

Hi vgisit, welcome to the forums.

Sorry to hear about the challenges -- the topic creator didn't share a case number, and while I've heard concerns on this before, turns out there were other reasons the tape selection differed from expectations.

Please open a Support Case and let Veeam Support review the debug logs to understand what happened during that event. Be sure to include logs from the affected job for Support to review. (Use the 1st radio button to export from jobs, select the job(s) that had unexpected behavior for export)

Please share the case number once created. Thanks!