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

Standalone Tape Fails All Operations

KB ID: 2142
Product: Veeam Backup & Replication
Version: 9.x
Published: 2016-07-12
Last Modified: 2020-08-13

Challenge

Tape fails inventory, erase (short or long), or any backups.

Cause

Standalone tape drive reports Empty MTF, or unable to read header on tapes that are brand new, or even when they are erased using native vendor tools.

Solution

The block size being used for the tape drive needs to be set to 65536 within Veeam:
 
  1. Go to Tape Infrastructure within the Veeam GUI.
  2. Expand the tree to display the tape drive(s).
  3. Right-click the drive, click Properties.
  4. In the drop-down box for Block size, choose 65536.
 
Test tape operations after to confirm resolved.
KB ID: 2142
Product: Veeam Backup & Replication
Version: 9.x
Published: 2016-07-12
Last Modified: 2020-08-13

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.