Hardware encryption doesn't work on tape operations after update to 9.5 Patch 4b

Veeam Backup & Replication
Last Modified:


After you update to patch 4b (, you may face the following encryption-related issues during the backup and restore procedures.
Restore from tape backups made in the previous product versions with enabled hardware encryption may fail with the following error message:

[11.07.2019 20:07:56] <  5652> mt |   Drive encryption status:
[11.07.2019 20:07:56] <  5652> mt |   Encryption Mode: Disabled
[11.07.2019 20:07:56] <  5652> mt |   Decryption Mode: Disabled
[11.07.2019 20:07:56] <  5652> mt |   Raw Decryption Mode Disabled (RDMD): Disabled
[11.07.2019 20:07:56] <  5652> mt |   Volume Contains Encrypted Logical Blocks (VCELB): Disabled
[11.07.2019 20:07:56] <  5652> mt |   Logical Block encryption parameters: Application Managed
[11.07.2019 20:07:56] <  5652> mt |   Hardware encryption is available
[11.07.2019 20:07:56] <  5652> mt | ERR | [MT]SCSI PASS THROUGH DIRECT ended with Scsi Error Fixed format, current;  Sense key: Illegal Request. Additional sense: Invalid field in command information unit
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to enable hardware encryption, tapeHandle: 0x00000000000006a4
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to create TapeReader.
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to create TapeFileReader, setPba: 614675, localFla: 136589546, restFileSize: 4621392384
[11.07.2019 20:07:56] <  5652> mt | >>  |An exception was thrown from thread [5652].
Tape backups will finish without any visible errors. However, the tape job statistics may show that the software encryption was used instead of the hardware one.

This issue occurs under the following conditions:
  1. The tape library is hardware.
  2. Encryption is enabled in the target media pool settings (https://helpcenter.veeam.com/docs/backup/vsphere/add_media_pool_encryption.html?ver=95u4).
  3. In the tape library settings, the encryption is set to Application managed (this setting is configured on the vendor side).


To solve the issue, apply the hotfix:

  1. Download the hotfix. It contains the agents both for x64 and x86 agents.
  2. Check the current version of Veeam Backup & Replication. It must be
  3. Make sure that no jobs are running, close the console, and stop all Veeam services.
  4. Stop Veeam services on the tape server.
  5. Go installation folder C:\Program Files (x86)\Veeam\Backup Transport\x86 on the tape server.
  6. Rename VeeamAgent.exe to VeeamAgent.exe_original.
  7. Copy VeeamAgent.exe from the Win32 hotfix folder to the installation folder.
  8. Go installation folder C:\Program Files (x86)\Veeam\Backup Transport\x64 on the tape server.
  9. Rename VeeamAgent.exe to VeeamAgent.exe_original.
  10. Copy VeeamAgent.exe from the x64 hotfix folder to the installation folder.
  11. Start Veeam services.

More Information

[[DOWNLOAD|DOWNLOAD PRIVATE FIX|https://www.veeam.com/download_add_packs/vmware-esx-backup/kb2981/]]
MD5: f41067805093c1081d2a52e8140ad4eb
SHA1: 54dff302b1aa0b77da2b8649315248b1ee5d6a53

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
4.1 out of 5 based on 5 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: