Skip to main content

Taking a backup deletes other backups

Thread needs solution

Running TI 2015 build 6613 on Win10 Home build 10586 backing up to a USB-connected external disk with nearly 2TB free space.

After moving to Win10, I created three new manually-started ‘full’ (i.e. not incremental or differential) backup tasks:  to back up one file (task DATABASE in the annexed log), the entire PC (task FULL), and a Documents folder (task DOCUMENTS).  Backup was to a new folder on the external disk.

Checking the emailed log after taking the first backup (DATABASE) showed that backup was taken successfully. But before validation, consolidation occurred (why and what with?), and then a previous full+incremental backup IN ANOTHER FOLDER was deleted…!

I then took a FULL backup. This was apparently OK.

Finally I took a DOCUMENTS backup. The backup was taken successfully. But before validation, consolidation occurred (why and what with?), and then the DATABASE and FULL backups WERE DELETED!!  And the deletion was confirmed with Win File Explorer.

The deletions are lethal: I could have carried on taking backups not knowing that they subsequently were being deleted.

I only made things apparently work properly by defining three new backup jobs with the each of the three backup tasks using different folders on the external disk.

Could anyone possibly clarify:

 

  • why consolidation need to happen before validation (and what is actually happening as shown in the log)
  • why the backup deletions are being made. It is this one which scares me! I only expected automatic deletions when automatic clean-up rules kick in, and then only to the oldest generations of the particular backup task, not backups from other tasks.

 

LOGS (extract)

First (DATABASE file) backup:

31        15/04/2016 20:10:56    Locking partition C:...

32    Information    15/04/2016 20:11:32    Create Backup Archive From:    C:\Users\gaynor\Documents\QH database.accdb

 To file: "DATABASE_full_b3_s1_v1.tib" Compression:    Normal Exclude:               System files 

33    Information    15/04/2016 20:11:32    Writing full version to file: DATABASE_full_b3_s1_v1.tib

34    Information    15/04/2016 20:11:33    The following backups have been successfully created: "E:\WIN10 backup\DATABASE_full_b3_s1_v1.tib"

35    Information    15/04/2016 20:11:36    Validate Backup Archive Location:           "E:\WIN10 backup\DATABASE_full_b3_s1_v1.tib" 

36    Information    15/04/2016 20:11:37    Consolidate Backup Archive Location:   "E:\WIN10 backup\DATABASE_full_b3_s1_v1.tib" Destination:        "E:\WIN10 backup\DATABASE_full_b3_s1_v1_C3BA61CB-1E1D-4A72-A7B3-F2D2C0ABEC6E.tib" 

37    Information    15/04/2016 20:11:37    Consolidate Backup Archive Location:   "E:\WIN10 backup\DATABASE_full_b3_s1_v1.tib" Destination:        "E:\WIN10 backup\DATABASE_full_b3_s1_v1_C3BA61CB-1E1D-4A72-A7B3-F2D2C0ABEC6E.tib" 

38    Information    15/04/2016 20:11:37    Deleting backup file with path E:\TOWER backup\Entire PC_inc_b1_s5_v1.tib.

39    Information    15/04/2016 20:11:37    Deleting backup file with path E:\TOWER backup\Entire PC_inc_b1_s4_v1.tib.

40    Information    15/04/2016 20:11:37    Deleting backup file with path E:\TOWER backup\Entire PC_inc_b1_s3_v1.tib.

41    Information    15/04/2016 20:11:37    Deleting backup file with path E:\TOWER backup\Entire PC_inc_b1_s2_v1.tib.

42    Information    15/04/2016 20:11:37    Deleting backup file with path E:\TOWER backup\Entire PC_full_b1_s1_v1.tib.

43    Information    15/04/2016 20:11:37    Deleting backup file with path E:\TOWER backup\Entire PC_inc_b2_s2_v1.tib.

44    Information    15/04/2016 20:11:37    Deleting backup file with path E:\TOWER backup\Entire PC_full_b2_s1_v1.tib.

 

Third (DOCUMENTS) backup:

31        15/04/2016 21:25:32    Locking partition C:...

32    Information    15/04/2016 21:26:08    Create Backup Archive From:    C:\Users\gaynor\Documents\

 To file: "DOCUMENTS_full_b3_s1_v1.tib" Compression:              Normal Exclude:               System files 

33    Information    15/04/2016 21:26:14    Writing full version to file: DOCUMENTS_full_b3_s1_v1.tib

34    Information    15/04/2016 21:26:42    The following backups have been successfully created: "E:\WIN10 backup\DOCUMENTS_full_b3_s1_v1.tib"

35    Information    15/04/2016 21:26:46    Validate Backup Archive Location:           "E:\WIN10 backup\DOCUMENTS_full_b3_s1_v1.tib" 

36    Information    15/04/2016 21:27:35    Consolidate Backup Archive Location:   "E:\WIN10 backup\DOCUMENTS_full_b3_s1_v1.tib" Destination:   "E:\WIN10 backup\DOCUMENTS_full_b3_s1_v1_4038CBA3-E776-44E2-BD50-6A0F0DF967B2.tib" 

37    Information    15/04/2016 21:27:35    Consolidate Backup Archive Location:   "E:\WIN10 backup\DOCUMENTS_full_b3_s1_v1.tib" Destination:   "E:\WIN10 backup\DOCUMENTS_full_b3_s1_v1_4038CBA3-E776-44E2-BD50-6A0F0DF967B2.tib" 

38    Information    15/04/2016 21:27:35    Deleting backup file with path E:\WIN10 backup\DATABASE_full_b3_s1_v1.tib.

39    Information    15/04/2016 21:27:35    Deleting backup file with path E:\WIN10 backup\FULL_full_b2_s1_v1.tib.

0 Users found this helpful

Can't say for sure.  If you haven't deleted the old backup tasks yet, you can see what C3BA61CB-1E1D-4A72-A7B3-F2D2C0ABEC6E is named by opening it in notepad (scripts are located at C:\ProgramData\Acronis\TrueImageHome\Scripts).  It's odd that it has a backup task name appended to the end of what would normally be prededed by ".tib".   Perhaps you had a pre or post command at some point of this task to run one backup right after the other?  

E:\WIN10 backup\DATABASE_full_b3_s1_v1_C3BA61CB-1E1D-4A72-A7B3-F2D2C0ABEC6E.tib

Regardless, it sounds like something in the backup database was corrupted in reference to the existing backup tasks from before the Windows 10 upgrade. Windows 10 upgrade has a lot of moving parts and we're hoping that Windows is getting everything right (for applications and software that already existed) when it's all said and done.  Frankly, I don't trust it.  Upgrades may seem to go OK at first, but it's issues like this that plague users down the road.  My guess is that Acronis installed with certain settings/components in your previous OS, but were slightly modified after the upgrade, or no longer apply specifically in Windows 10.  Why that would only impact the previous backup tasks - no idea, there may be more underlying issues with Acronis or other applications in general that have not yet surfaced. 

In most cases, if you've upgraded the OS when Acronis was already installed, or if you upgraded Acronis from a lower major version to a higher version (like 2015 to 2016), I've found it to be a lot less trouble by uninstalling the old Acronis version and then reinstalling it from scratch.  It certainly has a bit more upfront effort, but generally provides more reliability and frustration down the road. 

After upgrading 2 of my home computers to Win10, I promptly went back and reinstalled Windows "clean" and then installed all of my apps,settings, etc - for the most part both are running pretty well, although there are still some qwerks in Windows that show up in the logs I have to troubleshoot.  I left my old HP netbook as an "upgrade" and it was nothing but trouble from the start with Acronis and a bunch of other apps.  Even Windows started doing all kinds of weird things at one point, like telling me I needed to tell it what app ot open the "windows app store" - huh?  I tried a bunch of solutions online - all to no avail, rebuilt it and now everything works like it's supposed to.  

Moral of the story - upgrades, whether to a specific application, OS or a combination of both, you just really never know what you're going to get with your unique setup since we all maintain our systems differently and have different combinations of software already installed.  

In your case, hopefully just starting new backup tasks will prevent the same behavior, but I'd keep an eye on them.  If you're open to it, I would still recomment running the clean tool and reinstalling cleanly, just in case. Of course, before any major changes, I would take a backup of the system "as is" (also just in case). 

https://forum.acronis.com/forum/113656#comment-334624