Error: Failed to call RPC function 'LoadMedium': Incorrect function. Failed to move tape.

[TedLaurent]

I've got a ticket open for this issue but thought I'd post to the forum in case someone might have additional recommendations.

Currently the tape backup job to the fiber channel connected MSL 2024 fails with the error message listed in the subject line.

I've rebooted the tape library and rescanned it as suggested but no change.

Anyone seen this error?

[TedLaurent]

Addendum: GFS Media pool was set to automatically get tapes. Loading tapes manually into the pool allows tape backup job to complete normally.
HPE Command View MSL shows automatic. Anyone seen this happen before?

[TedLaurent]

For reference: Case # 07138096

[sroberts6362]

Hello, I am wondering if you were ever able to resolve this error and what your solution was. Thank you.

[HBSR]

Even the same issue error and messages: can find any good respons / solution / hint in the forums.

[DAHKIS]

Hello, i was wondering if you Initialised the media in the Webui of the Tapeloader before trying to run a Tape Backup?

[Vodochnik]

I had this and similar errors on defective tape drive. Reflash/reboots/rescans/reconnects helped just for a short period of time.
The solution was to replace a drive.
I have seen this error on incompatible SAS HBA too (Proliant, HP recommended controller), the solution was to replace the HBA with HBA from another vendor.

But first of all I would try to run a drive cleaning 2-3 times manually (I mean from web interface of the library).

[jimpey]

For anyone that's having a similar issue I found how to solve this, at least in my case with a brand new MSL 2024 and LTO 9 tape drive.

For Tape Drives using LTO 9 cartridges it is important to initialize the cartridges from the RMI first.
After initializing the cartridges Veeam could scan the inventory and complete jobs again.
I also reflashed the firmware on the MSL 2024 however I don't think this helped.

[david.domask]

Hi jimpey, welcome to the forums!

Thank you for sharing your solution; indeed, this is known behavior specific to HPE and LTO9 tapes; we have that documented in this KB: https://www.veeam.com/kb4396

In summary, certain HPE Tape Library models will not allow backup applications to move uninitialized tapes to the drive until the initialization tool has been run from the tape library itself; this will present in Veeam with the error from the topic's subject, but keep in mind that error may appear for many other reasons (it is generic response from library that it could not perform the move operation, not limited to uninitialized tapes)