v9.5: Skipping tape media eject because lock failed warning

[mcsmithSOP]

After upgrading to version 9.5, our weekend Full tape jobs started generating the following warning:

Tape library: HP MSL G3 Series 6.40 (server.domain.com)
Used tapes: TAPE# [TAPE#]
Failed to eject some tapes
Skipping tape media TAPE# eject because lock failed

It never occurs during the week during the (much smaller) Incremental jobs. Looking at the job chain, it appears that it's because the Full tape jobs get queued up and the next job in the queue is taking control of the library.

The tapes show all the .vbk being written to them, and the tape size indicates that the files were fully written.

I'm okay with the tape not being ejected from the drive after a job when there's already another job waiting to write to that tape, but version 9.0 always reported success on the weekend full jobs.

[lyapkost]

Hi, Jason. There were some warnings added in 9.5. In case you don't want to receive them (change them to info messages as it was in 9.0) after upgrading to 9.5 update 1, please, set the following registry key:

Host: Veeam B&R Server
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Value: DisableEjectWarning
Type: DWORD
Value : 1

[mcsmithSOP]

Thanks!

[cffit]

Can someone explain what the error means or why we get this? I understand it came as more warnings that were added in 9.5 and it can be turned off with the registry entry, but what does the warning mean and why would it be important enough to add in 9.5?

[DustinBarott26]

I would like to piggy back on cffit's comment....

Are there any repercussions to disabling this registry key. I question disabling a warning that is coded into the program for a reason.