Veeam Support Knowledge Base
All tape write operations fail for MHVTL if the block size on drives differs from 65 KB

All tape write operations fail for MHVTL if the block size on drives differs from 65 KB

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

By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please try again later.

Challenge

All tape write operations fail for MHVTL if the block size on drives differs from 65 KB

Cause

Veeam Backup & Replication v9 has a new algorithm of choosing the block size. Now Veeam automatically detects the highest available block size and runs jobs according to this value. Currently this option is available for all supported devices except MHVTL.

Solution

Manually change the block size in this dialog box:

User-added image

More Information

Please see Data Block Size section here

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Verify your email to continue your product download

We've sent a verification code to:

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

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.