Unable to retrieve next block transmission command when backing up to tape from a Linux repository

KB ID: 1872
Product: Veeam Backup & Replication
Version: 7.x
Published: 2014-04-21
Last Modified: 2020-08-13
Get weekly article updates
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

error icon

Oops! Something went wrong.

Please try again later.

Challenge

When backing up to tape from a Linux repository, the following error may appear:

Unable to retrieve next block transmission command. Number of already processed blocks: [number of blocks].

The log file contains the following information:

cli| WARN|[Tape] Default EOM Warning (2147483648)! Initial free space: 5251268608, Written (this tape): 3104833536, Total written: 3104833536
     ERR |Asynchronous data reader has failed.
     ERR |End of file
     >>  |--tr:Cannot read data from the socket. Requested data size: [952531].
     >>  |--tr:Failed to unserialize buffer with data.
     >>  |--tr:Failed to unserialize data block.
     >>  |--tr:Failed to unserialize FIB block.
     >>  |Unable to retrieve next block transmission command. Number of already processed blocks: [4944].
     >>  |--tr:Next asynchronous read request cannot be processed.

Cause

By default, most SSH servers have set a timeout to disconnect idle clients. After idling for some time, your connection is dropped.
 

Solution

To make the keep alive settings available for all connecting clients, it is recommended to configure the settings in server side.

Modify the /etc/ssh/sshd_config and add the following lines :

ClientAliveInterval 30
TCPKeepAlive yes
ClientAliveCountMax 99999

After setting this, you have to restart the SSH server by issuing this command :

sudo service ssh restart

Note that restarting SSH server will not disconnect existing connecting clients via SSH.

More Information

Keep in mind that these changes will affect all SSH connections.
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

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

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

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:
  • 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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.