I’ve randomly had two backups corrupt at one of my clients. Not sure why it happened, but they did. On one of them, I deleted from disk all of the restore points on the local datastore, and took a new full. I left the cloud data alone, and as we speak, the new restore points are peacefully transferring offsite, no issue. The second backup has been a different story…
Because of the nature of the server, I decided to take a new full and leave the old data in place, just in case. The new full local backup was fine, but the offsite failed. I tried running an active full of the offsite, but same deal; the offsite failed. So now I am trying a new strategy. I took a look at the restore points and 99% were corrupted (I believe this was the offsites), so I decided to just wipe everything and start from scratch, because I think the corrupted restore points are causing issues with the new data going offsite. The offsite failures have been throwing an error I’ve never seen before. I’ll paste it below. I’ll keep you all updated on what ultimately happens with this. The new local full is running as I type this.
Processing *sever name* Error: Bad Data.
Failed to call CryptDecrypt
AesAlg failed to decrypt, keySet: ID: 45ee103e03b54e69630b13affc7ecb56 (session), keys: 1, repair records: 1 (master keys: 1057cad7009d95a034d2d62be82b7040)
Failed to upload disk. Skipped arguments: [servername_1-flat.vmdk];
Agent failed to process method {DataTransfer.SyncDisk}.
Exception from server: Bad Data.
Failed to call CryptDecrypt
AesAlg failed to decrypt, keySet: ID: 45ee103e03b54e69630b13affc7ecb56 (session), keys: 1, repair records: 1 (