Rogue Backups Downloaded to Scripts Folder
After all the MMSM and 22510 upgrade issues from Nov-Jan, I finally decided to upgrade to the current version on 4 PC's on my network that had not been upgraded. After the upgrade, two of them ended up with scripts (in the Acronis scripts folder) from some of the other PC's script folders. The computer "Bugatti" ended up with a NAS backup script and a Cloud backup script from the computer "Tesla", showing up under "This Computer". These Tesla scripts would run on Bugatti, and would indeed backup Tesla files remotely using the same .tibx file on both the NAS and Cloud (at a different time that the original target computers scripts). I had this exact problem back in Oct-Jan. The solution is simple. Turn off Active Protection. Shut down Acronis. Just go into the scripts folder, open the .tis files one-by-one, and find a computer name in the script that matches the name of the offending backup script name. Delete those scripts and voila!! Problem solved.
What bothers me about this is how this can happen at all. Another computers backup scripts should NEVER be downloaded into a different computer and that computer be able to run them. Seems like a HUGE security flaw and leak. Anyways, all the computers are upgraded and that particular issue is resolved but I wanted the community to know that the Acronis "servers" are still running code that changes our backups.
Chris, are you sync'ing the Acronis ProgramData folders with any other computers at all? That is the only way I can think that such things as described here and your other password issue might happen.
I posted this issue backup in November and Enchantech confirmed he had seen the issue as well. Steve Smith also commented on the problem. The problem existed then and it still exists today. Please see:
Chris, thanks for the reference to the older forum topic - my comments in that topic remain the same, that I have not seen this issue other than when I have used the 'Reconfigure' option for a task coming from a different system.
I have not seen the issue being caused by having other computers online when installing ATI etc as Enchantech mentioned, but I do not ever map any drives between my computers so there should be no way for Acronis to pick up backup files from those other online PC's. I use a common Synology NAS for backups but again, the backups are separated by unique folders on the NAS per computer, and such backups only appear in the 'Other' section in the GUI if I have been opening them via Explorer on this PC.
Never touched the reconfigure button. In fact, I wasn't even "driving" the Bugatti PC (pun intended). The Acronis Tech was driving it via TeamViewer and all he did was initiate the 22510 upgrade. When the upgrade finished, the two rogue backups were now there under "This Computer". The rogue "Tesla" backups were a Cloud backup the other was a NAS backup, both configured for computer "Tesla". The Tech saw it happen in real-time.
I believe that Acronis 2020 does keep a copy of the backup scripts on their servers whether they are NAS or Cloud backups. The only way for a script (or two) from computer A to get copied over to computer B, when running Acronis' application upgrade is that it would have to be going through their servers, from Computer A to Computer B. I do consider this a serious bug, as all of the password and encryption information in the scripts remained intact, enabling the user of Compute B to delete the backup files of Computer A on the Cloud and NAS. I found that out the hard way back in November.
I do believe that you've never seen it, but the bug is there either in the Acronis client app or on the Acronis server side.
Have to hope the Acronis tech was able to capture enough diagnostic information for this to be fixed by their developers as it is alarming to say the least! Perhaps another reason to stop & disable the MMMS service (assuming it is doing the communicating of the script files).
Chris, why was the Acronis tech initiating the upgrade? Prior to that, had you had the MMSM service disabled? Just wondering if something was still amiss on the server side since last November and just didn't appear until the service was enabled on the upgrade.
The Tech was going through the normal routine of confirming what the issue was. Starting the backup, seeing the failure code. He then started checking the basic settings, including the version of Acronis running. He wanted to upgrade that to the latest version, since the machine was still on Release 1 of Acronis 2020 (the other 3 PC's on the network had been upgraded to Release 2). I had disabled the MMSM service on this system since November. It has been backing up successfully every night (one NAS backup, one Cloud backup) until 2/28/2020. When the Release 2 upgrade was applied, MMSM gets turned on (I think I remember Steve pointing that out back in that Oct-Nov timeframe on the forum).
The Acronis Server side software is still causing issues for folks that initiate an upgrade.