A backup that re-creates the bundle instead of blaming the transfer
A backup run that could not find the bundle it had written was reporting a transfer failure; it now re-creates the bundle and says which of the two actually happened.
When a book’s machine cycled, the bundle it had been writing went with it, and the next backup run reported a transfer failure. The transfer was fine. The thing being transferred no longer existed.
The fix re-creates the bundle when it is missing, and the run now says which of the two actually happened. A backup that reports the wrong cause is worse than one that fails loudly, because it sends you to look at the network.