Recovery from errors without the backup job failing (Error 4103)
Aomei Backupper is fast enough when performing backups that it has revealed a previously hidden flaw in my laptop. After extended periods of time transmitting at maximum throughput, as is the case when I am backing up the PC to my remote share via wireless, my wifi card appears to be overheating and dropping the connection momentarily (although it still shows as associated with the AP). That much is not Aomei's fault; I LIKE that it is fast enough to max out the bandwidth when no other backup program I've tried can. I am in the process of troubleshooting the issue and I will fix it. I can (and usually do) use ethernet for this; it was happenstance that I was connected wirelessly when the backup task started and it eventually triggered the dropout.
The problem as far as Backupper is concerned is that when my wifi drops during a backup task and the share is no longer accessible, Backupper simply gives up with information code 4103. It would be much better if Backupper would pop up a message that informed me that the target drive is no longer accessible and ask me if I want to retry or cancel the operation rather than just cancelling it automatically.