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

Veeam Backup & Replication
Last Modified:


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.


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


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.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
3.8 out of 5 based on 12 ratings

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: