Prevent Veeam from locking tape drives

Veeam Backup & Replication
Last Modified:
KB Languages:


Veeam periodically rescans the tape drives. This locks the drives and prevents other tape software from writing to them. 


The refresh rate on the automatic rescan is too frequent if using third party tape backup software. 


The registry keys below prevent Veeam Backup & Replication from scanning for changes to the tape systems that are attached to the server. If the tape drives/library are already showing up in the Veeam console under backup infrastructure, and you would like to remove them in addition to Veeam not scanning for them, you will have to follow the additional steps below.
This registry entry is for versions greater than
(Please check to make sure you are on the most recent patch.)
HKLM\SOFTWARE\VeeaM\Veeam Backup and Replication
DWORD: DisableTapeSubsystem
Value: 1 (decimal)
How to remove the tape library and/or tape drive from console and disable rescan:
1.    Disconnect tape hardware from server (disabling drivers may be sufficient).
2.    Wait until the library moves to offline in the Veeam console.
3.    Remove Library from the Veeam console.
4.    Add the registry entry as documented above.
5.    Close console and restart Veeam Backup service.
6.    Connect tape hardware to server.
7.    Open the Veeam console to verify the tape library is no longer present in the backup infrastructure.


More Information

If you ever decide to uninstall the other software and use Veeam for tape backups, you will need to delete this DWORD.  

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: 
3.9 out of 5 based on 20 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: