How to restore from tapes with “Invalid block size”
Greetings from Veeam Support and welcome to the next episode of our troubleshooting series!
In this article, we will review how to resolve an issue that might be caused by a mismatch between the block size set in your Veeam tape drive properties and the one actually supported by the tape device itself. You will learn why block size can be different and how to fix it.
And even if you’ve never come across such a problem, you may also find this post useful, as under certain circumstances changing the block size can help you increase the processing rate. This is because when you have a higher block size, the drive is supposed to write data more quickly.
Invalid block size backstory
Something bad happened with your HBA controller and you had to replace it. Meanwhile, your Veeam Server stays the same (i.e. the OS and the application were not re-installed), and the tape library and the drive were not changed as well.
You set up everything and your boss asked you to restore a VM from some old tapes written a day before the HBA controller replacement. You see an “Error: Invalid block size” alert.
Read the entire article here, How to restore from tapes with “Invalid block size”
Via the fine folks at Veeam.