Writing to Smartdisk and the NetVault log reports Transfer to the device has stalled.
When the Plugin on the client is unable to send network traffic to SmartDisk for a period of 15 seconds, the message "Transfer to the device has stalled" is logged.
At the point when communication is restored, the message "Transfer to the device is no longer stalled" is logged. The 15 second timeout is not configurable
There is a delay sending data to SmartDisk and the cause can be network congestion or SmartDisk free space.
1 - Ensure that there are no disk space issues with the SmartDisk staging area. Backups targeting SmartDisk will stall if the SmartDisk staging area volume becomes full. The backup will un-stall when space becomes available.
2 - Check network performance between the SmartDisk server and the client, the most common cause of this issue is network delays. For example, a network connection configured to 10Mbps, but there may be no stalls at 100Mbps and at 1G. The timeout can not be adjusted; 15 seconds is a long time for a network to stall.
3 - Adjusting the packet size on certain networks can help the client stream data to SmartDisk more effectively, reducing the number of times the device need to stall and stopping the message channel from dropping. For example, to increase the block transfer size from default 32KB to at least 256KB
smartdisk.bat config --update --webdav 37453 --block-size 262144