https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxODEyIiwiaGFzaCI6IjhlZGQ0YzU5LWRmZGItNDE2Mi04MzA4LTRjYTQyM2YyN2U1YSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Missing Tape Device

Challenge

Tape Device is not present within backup infrastructure.

Cause

A missing tape drive can stem from a few issues described below.

Solution



1. Device Specific, vendor supplied OEM driver for Windows must be installed.
    a. Devices appearing in Windows Device Manager as Unknown or Generic are not supported.

 
User-added image


2. No other backup server must be interacting with the tape device.

3. Tape device drives must be fully up to date (Tape Devices, Auto loader, etc.).

If all devices are fully up to date, but the tape is still not present, a reboot of the Veeam server may be necessary.

More information

If any other management software interacts with the tape device (in an unsupported configuration), you must stop all services and restart the Veeam services to allow communication to the tape devices.
 
KB ID:
1812
Product:
Veeam Backup & Replication
Version:
7.x, 8.x
Published:
2013-08-28
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.