1-800-691-1991 | 9am - 8pm ET
EN

Tape library and drives are shown as separate devices

KB ID: 1842
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5
Published: 2013-12-05
Last Modified: 2021-08-05

Challenge

Tape library and drives are shown as separate devices in console or loading tape into TapeDrive0 moves the tape into TapeDrive1 etc.
tape library with no drives
Shown here, the Tape Library has no Tape Drive listed
Tape drive seperate shown acting as if it is a tape library with its own tape drive
Shown here, the Tape Drive is separate from the Tape Library.

Cause

  • The tape library is not reporting the tape drive serial number.
  • The tape library has one or more unpopulated tape drive bays.

Solution

The following registry value may be used to manually map the tape drive(s) to the tape library.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: TapeDevices
Value Type: Multi-String Value (REG_MULTI_SZ)
Value Data: 
TapeServerName
Changer#=Tape#:ElementAddress

Collecting Information to populate Value Data:

The Value data consists of two lines. The first declares which tape server should be affected, and the second declares the identifier for the Tape Library and associated Tape Drive(s).

Line 1:

Use the tape server's name shown in the Veeam Backup & Replication Console under Tape Infrastructure > Servers.

tape server name
Line 2:
  1. Connect to the Tape Server where the Tape Library and Drives are attached.
  2. Open an Administrative Command Prompt
  3. Change directory to a temporary folder (e.g., cd C:\Temp\)
  4. Run the following command to dump information from the Veeam Tape Service.
    The command will complete silently, leaving in the folder a file named "dumpinformation.xml"
"C:\Program Files (x86)\Veeam\Backup Tape\VeeamTapeSvc.exe" -dump
  1. Open "dumpinformation.xml" in an XML editor. (alternatively, open the file in a web browser)
  2. Using the info at the end of the file,  identify the following information:
    • DeviceName for the changer
    • DeviceName of the drive(s)
    • Respective ElementAddress of the drive(s) associated with the Changer
      Use the SerialNumber value(s) to correlate the ElementAddress

    See the example below:
Example of relating serial numbers to element ID
Note how Tape1 has a SerialNumber of DF50A00001 and a drive can be seen associated with the changer that has the same SerialNumber.
Below the tape drive SerialNumber in the Changer section is shown the ElementAddress.
Using the examples above, the resulting "Value data" would be: 

 

VeeamTapeServer
Changer0=Tape1:0,Tape2:1
Screenshot of example in registry editor
KB ID: 1842
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5
Published: 2013-12-05
Last Modified: 2021-08-05

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

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.