I am getting this error a LOT on one of my backup sets. I dutifully “delete” the offending backup but the problem returns at least once a week, just on this one backup set on one machine.
I don’t believe it is triggered by network communication errors.