Hello All,
We have some log shipping jobs that are randomly failing during the restore step because of error 3266, which is damaged and unusable media error. We have tracked it down to most likely a network issue and corrupt transaction log because it only happens between two of our locations. The log copy step report success even though the log is a different size from the source after the copy, so the copy must really be failing somehow. When the restore of that log happens, it obviously isn't a complete log file and fails. Our solution has been to manually copy the failed log file to the destination and restart the restore step. My question is, is there a way to validate the transaction log file after the copy and if it is not identical to the source, retry? Any help and advice is much appreciated. - Wes