Direkt zum Inhalt

LTO Tape Inventory bug NOT fixed in latest release versions.

Thread needs solution

Hi there,

Previously I had an open case with support (02719436), which lead to Acronis developers being advised of a bug with ABR not running inventory when a tape was inserted (in Tandberg LTO5 standalone drive).

Over the course of a month I worked with Acronis to get the issue resolved, and I was advised of a pre release 11.7.44422 which claimed to fix the issue.

We did not update to this and remained on 11.7.44421 due to concerns of reliability.

Then there was 11.7.50058 released which claimed to have fixed the issue.

Following closely after that was 11.7.50214 which states under Fixed:

Tapes

  • [ABR-105906] After upgrading Acronis Backup to version 11.7, it is required to inventory every tape loaded into a standalone tape drive even if this tape was used by Acronis Backup before.

So after upgrading to 50214 I was looking forward to not having to manually inventory the drive again when the tape is inserted.

BUT THE ISSUE IS NOT FIXED!!!!!!

So three versions now this has meant to be resolved and it is not. This occurs on both of our backup servers and NEEDS fixing once and for all.

Can someone please assist with this, as it seems I'm not the only person with this problem (https://forum.acronis.com/forum/127238).

With staff working in satellite offices over Christmas, we NEED a solution to work as we cannot have them accessing servers and running inventories on the tapes. The only option is to issue a command line parameter from another computer (not the backup server).

 

Thanks for any assistance.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 250
Kommentare: 7092

Hello Mitch,

Thank you for your posting! I've checked the status of ABR-105906 in our internal sources - the fix has been verified on the latest builds. If the issue still persists on your environment, please raise a support ticket, so that our engineers can look into the situation.

Thank you,