Full Disk Backups Are Including Folders From Other Backups
Hi All,
I have had this problem happen, inexplicably, several times. I would like to know if others have experienced it, and HOPEFULLY found a resolution.
I am using Acronis True Image 2014, on a Win7 ULT (x64) machine, my desktop computer.
Briefly, I created a full B/U of a laptop HD, prior to reinstalling it's O.S. (HD removed from the laptop and connected to my desktop via SATA). The laptop was running Win 10 (x64)
When I went to copy back the data from the full B/U I made, I noticed that there were other folders present on the root (OS partition - C Drive) drive that came from other B/U's I have made. They were NOT present on the original drive.
For example, there was a folder present in the laptop B/U (C:\Backup_091515) that was part of another full backup that resided on the same external USB drive. Neither B/U's were associated in any way.
I dont do incremental B/U's, only full ones, one time only - never scheduled, and store them on an external USB drive.
This has happened several times (similarly) in the past (that I have caught).
Please see the attached image, and please HELP me to understand why this is happeneing, but more importantly, how to STOP it.
TIA!
Tim
Attachment | Size |
---|---|
randomfolder.png | 74.58 KB |


- Log in to post comments

Tim,
There is no way data from a backup task would find its way in the archive of another backup task. In the past, we have seen the ATI app to get confused when you backup the same source to the same destination folder with different tasks. The confusion resulted for example in ATI miscalculating the backup size.
One thing to try is to delete the database folder of ATI in C:\programdata\Acronis\TrueImageHome, then double click on the archive file using windows explorer and see what versions are shown (you should see only one for full backups), then open that version and check whether rogue folders are still showing up.
Another thing to try is to recover the backup with the recovery CD (still delete the database folder in Windows), and see if the recovery contains the folders.
If the rogue folders are still there, they were on the disk when the backup was run, or the disk NTFS volume information is wrong.
- Log in to post comments