Initializing LTO9 tapes behavior

[marieelieg]

Hope everyone is having a good time zone.

I have a question regarding the initialization step for LTO9 tapes.

We have successfully initialized all new LTO9 tapes prior to the backup. However, now we are facing an issue where the daily tape backup generates the following error every time it runs:
[<vm_name>] Loading tape <tape_name> from Slot 1 to Drive 1 (Server: <server_ip>, Library: HP 1x8 G2 AUTOLDR 6.00, Drive ID: Tape0) Error: Failed to call RPC function 'LoadMediumByScsi': Fixed format, current; Sense key: Illegal Request. ASC = 0x0000000000000044, ASCQ = 0x0000000000000081 (vendor specific). Failed to perform scsi command. CDB: a5 00 00 00 03 e9 00 01 00 00 00 00.

We have to manually initialize the LTO9 tape within the HPE 1/8 G2 Autoloader prior to each tape job run, otherwise it will fail with the aforementioned error.

Is this behavior normal?
As far as I know, and based on HPE documentation (New Media Initialization Wizard), the LTO9 tape initialization is for new tapes only and not for ones that have been initialized already.

Thanking you in advance

[david.domask]

Hi marieelieg,

The behavior is not expected; your research is correct, with HPE tape environments and LTO9, tapes must be initialized by the tape library itself before the library will allow backup applications to move tapes from slot to drive.

This should be a one-time process however, so definitely not expected. Please open a Support Case and allow Veeam Support to review the situation. Please export logs for one of the jobs that was affected by this behavior for Support to review. (use the 1st radio option to export from jobs, select one of the jobs affected by this for export)

Please share your case number here once created. Thanks!

[RobTurk]

Perhaps a wild guess, but the listed SCSI command tells the library to move a cartridge from Tape slot 2 to the drive. The library response (ASC/ASCQ 44/81) means "Source is not ready".
So the library doesn't find a tape that it expects in Slot 2, or can't grab it.

Could it be that the tape magazine isn't installed properly, or the import/export door isn't closed?
Another thing to check is rescan and re-inventory the library to ensure all tapes that VBR thinks are in certain slots, are actually there.

[fgw]

hi guys,

unfortunately i have to post to this old thread!

running into the same issue here:
using HPE MSL2024 autoloader (library) with LTO9 drives
initialized all media before using them
whenever such a media is reused (in my case its the weekly tapes) i need to reinit the media on the library again!

so this looks like writing a backup to tape somehow "destroys" the initialization information on the media which requires it to be reinitialized before every single use!

this is somehow annoying and for sure not intended behavior!

looks like there needs something to be fixed in compatibility between HPE LTO9 tape drives and VBR?

btw. backups including backup to tape works without issues! its just the requirement to reinit media every time thats very annoying!

[david.domask]

Hi fgw,

That indeed does not sound correct, so please open a Support case and allow Support to review the behavior. Be sure to include Logs for Support to review. It would be best if you could capture the situation where an already initialized tape is unusable in a job (I'm guessing there's an error in the job or the tape is never selected) so that Support can see why there is a challenge with the already initialized tape. So please reproduce the issue where an already initialized tape cannot be used by a job, export logs for that job, and let Support review.

Please share you case number once created. Thanks!

[doriangrey]

Dear fgw, did you ever manage to solve your issue?
I am facing the same behaviour with an HPE 1/8 G2 Tape Autoloader.
Everything was working fine until I replaced the faulty LTO-9 Ultrium 45000 Drive within warranty from HPE.
With the new drive, I have to re-initialize the media before each use. I also noticed that rebooting the autoloader upon inserting the tapes removes the unitiliazed status and the media can be used without initialization.

[david.domask]

Hi doriangrey, welcome to the forums.

The user never shared a case number so not sure what the result of their issue was.

For your issue, sounds like this is happening in the tape library itself? (tapes showing as uninitialized?)

Probably best to show the behavior to your tape vendor, as to my understanding once the tape is initialized it shouldn't need to continue to be re-initialized, and definitely not due to a library reboot.

[marieelieg]

Hello, just an update from our side. The customer never replied back to us regarding opening a case so not sure what exactly happened there.

[fgw]

hi guys,

sorry just forgot to report back!

so here we go: case # 07817379

there was not much veeam could do here anyway. at the end i also opened a case with HPE and after some messing around with HPE first level support i got a phone call from a higher support level:

• this is a known issue with the library. removing and inserting media through the mail slot results in the requirement to initialize the media again when it is inserted back into the library!

• I have not tested this, but regarding to HPE, removing and inserting media through a magazine does not require reinitialization but still may require to inventory the library.

• there also exists a workaround, where after inserting media a inventory the library may make the media recognized.

as it seems easier to me to just initialize the media after inserting them, i just continue to do so...

HPE is aware of this issue and already had several customers complaining about it. there is a new firmware expected by the end of the year or beginning next year which may (or may not) also address this issue. (may or may not - YES this was the info i got from HPE)