resp = {.err = -60 (Configuration version mismatch)};
ATI2020 has been working without incident for months until 5/13/21. I've made no changes to either ATI or Windows10 except the forced Windows updates from Microsoft.
On or about 5/13/21, all but one of my backups to the cloud stopped working (why one of them still works puzzles me). Most of these backups are not particularly large. I've tried many things in attempts to correct this problem (including deleting and recreating one of the backups from scratch under a different name).
Using the newish MVPassistant tool, the most consistent error messages I see in the backup_worker log is the reoccurring line:
"resp = {.err = -60 (Configuration version mismatch)};"
I also see this error message sprinkled about (usually, or maybe always, before the "mismatch" error message mentioned above):
"resp = {.err = -22 (Lease request conflicts with another lease)};"
I've attached the complete, short backup_worker log from a failed run today of one of these cloud backups (my name given to backup = "AppData (to Cloud)").
I too am suspicious of a MS update since 2 such updates were applied to my system on 5/13/21 (the very day this started to happen). They were:
May 11, 2021-KB4601554 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, Windows Server, version 20H2, and Windows Server 21H1
May 11, 2021—KB5003173 (OS Builds 19041.985, 19042.985, and 19043.985)
P.S. I have tested the ability to recover files from these failing backups. I was able to retrieve a 300MB file from the "AppData (to Cloud)" backup above. It is a file used everyday (email) and the latest version was 5/12/21 just the day before these cloud backups started to fail.
I thought maybe it would be helpful for comparison purposes to post the backup_worker log from the only cloud backup that is still working. I have 5 backups to the cloud: 4 are failing in the same way; but for whatever reason, this single backup (my name given to backup = "Misc (to Cloud)" is still working properly.
I did truncate this file by eliminating a repetitive sequence of entries (I think they simply logged the data being transferred). I clearly marked where I did this, and left the 1st and last of these sequences of entries in place.
Sandy,
Thanks for providing the log files. I see that prior to the Configuration Version Mismatch error another error is reported two times this error
resp = {.err = -22 (Lease request conflicts with another lease)};Suggest that a connection with the Acronis Cloud server is at issue. Please visit the link provided below and follow the instructions to verify your connection to the cloud server. The instructions tell you how to find the respective cloud server for your backups. You should perform the check process on the task that works as well as one that does not work and note if the servers are different. If you find that they are then this could well be the issue.
Do download and run the respective verification tool indicated by the checking method and make note of the results. Post back your findings.
Thanks Enchantech,
Testing with the connection verification tool will have to wait a couple of days. I set up a brand new backup to the cloud.....this time with a name that has never been used before to see what happens. So far it is running for a couple of hours, but it still has some 36 hours to go. I don't want to mess with anything else in ATI while this test is progressing.
Understood.
OK. I've completed the various test backups I thought might shed light on things without learning anything new. All my backups to the cloud still fail with an eventual network timeout. Until yesterday, 1 of the 5 backups would complete successfully, but now that one too is failing in the same way the others do.
I have attached 2 files. One is the output from the AcronisCloudUS2Check.exe program which showed no errors. The other report is the most recent backup_worker log from the backup that used to work, but now too fails.
I can only suggest that you open a support ticket with Acronis.