Strange issue with a large file-server restore from tape straight to into a VMware environment.
Given it's large size (17TB) , we knew the VM would take a long time to restore. When the process to restore the individual disk reached the 24 hour mark it timed out and the restore job ended.
[27.11.2019 19:04:33] <28> Info [AP] Waiting for completion. Id: [0x2490860], Time: 23:59:59.6854531
[27.11.2019 19:04:38] <127> Info [AP] (df51) output: <VCPCommandResult result="false" exception="Timed out to wait for traffic control event.
--tr:Receive retry thread has failed.
Unable to retrieve next block transmission command. Number of already processed blocks: [0].
--tr:Next asynchronous read request cannot be processed.
--tr:Asynchronous data reader has failed.
--tr:Failed to process conveyored task.
Failed to download disk.
--tr:Disk download failed.
Agent failed to process method {DataTransfer.SyncDisk}." />
[27.11.2019 19:04:38] <12> Info [AP] (df51) output: >
[27.11.2019 19:04:38] <28> Error Timed out to wait for traffic control event. (Veeam.Backup.Common.CCppComponentException)
[27.11.2019 19:04:38] <28> Error in c++: Receive retry thread has failed.
[27.11.2019 19:04:38] <28> Error Unable to retrieve next block transmission command. Number of already processed blocks: [0]. (Veeam.Backup.Common.CCppComponentException)
[27.11.2019 19:04:38] <28> Error in c++: Next asynchronous read request cannot be processed.
[27.11.2019 19:04:38] <28> Error in c++: Asynchronous data reader has failed.
[27.11.2019 19:04:38] <28> Error in c++: Failed to process conveyored task.
[27.11.2019 19:04:38] <28> Error Failed to download disk. (Veeam.Backup.Common.CCppComponentException)
[27.11.2019 19:04:38] <28> Error in c++: Disk download failed.
We can't find any network errors that would have caused this and I find it mighty suspicious that it times out at exactly 24 hours.
Hi Tom. We've just reviewed your case with developers. There's a network time-out of 24 hours in VBR, it seems that one of the VM disks' data is fully located at the end of the tape and this disk restore doesn't start within 24h. Very rare case but the time-out can be changed with a regestry key. Please ask your support engineer to provide the key.
Do you face the same situation with Tapes? Please consider to open a support case as well whenever you got an error. The key may have helped in tohhmas case. That doesn't mean it solve your situation as well.
The key shared back in 2019 was the following one: