What's interesting is that the status of E(xpired) is logged. By default, the copy engine will stop copying a file after 24 hours. In this case, it seems to have been configured for a shorter duration. You can check the current value (if there's one) in the registry node HKLM\Software\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name>\COPYTO:ExpiryIntervalInMinutes. The value is in minutes.
From the results you posted, it seems that the file was placed in the copy queue on 2014-07-19 23:53. The copy engine only managed to process the file on 2014-07-20 13:32, by which time it flagged the copy task as having expired, and hence aborted any attempts to copy the file.
What might have happened is that older files in the queue took a longer than expected time to get copied over to their respective destinations. The copy process only managed to process the file in question some 13 1/2 hours later, at which time the configuration flagged the file as having expired and need not be copied any more.
From the results you posted, it seems that the file was placed in the copy queue on 2014-07-19 23:53. The copy engine only managed to process the file on 2014-07-20 13:32, by which time it flagged the copy task as having expired, and hence aborted any attempts to copy the file.
What might have happened is that older files in the queue took a longer than expected time to get copied over to their respective destinations. The copy process only managed to process the file in question some 13 1/2 hours later, at which time the configuration flagged the file as having expired and need not be copied any more.