Skip to main content

Old version cleanup rule not working

Thread needs solution

TI 2017 updated in place from 2014.  It would seem that the cleanup rule is not being applied.

I have setup for a differential backup with one full and 6 diffs.  I have also set up for no more than three version chains.  Right now I have 5 chains on the backup media and is starting a new chain.  This used to work in 2014.

Any ideas?  Can I just delete the old chains without upsetting the TI database?

 

 

0 Users found this helpful

The change from 2014 to 2015 was considerable (2017 is based off of 2015).  In some cases, running a full cleanup using control panel to remove Acronis completely, then running the clean tool, rebooting and doing a fresh install with the full installer can make a world of difference.  Might be the way to go here too - just for overall stability down the road.

That said, for the current situation, if you move or delete the chains manually, then go back into the GUI and run a validation.  You will be prompted to locate the missing files or ignore them.  Ignore each item until the prompts are gone.  This should update the database and let you start anew again.

FYI... version chains get "reset" each time you go into the backup script and save it again.  For instance, if you have a chain that consists of 1 full + 6 incrementals (that runs daily) and you complete the 4th incremental, but go back into the settings and save again, then it will take another 6 incrementals (and no changes to the backup task again), before then next chain starts again.  Also, version chaings don't complete until the next full has completed successfully.

David,

Are you performing a "Validation" as part of the backup task?  If there are issues with the validaton, then the cleanup may not run.  Recommend you download the log file viewer and see if the service logs provide any informaton.

https://forum.acronis.com/forum/115626

 

Thanks Bobbo & FtrPilot.  Checking the log gives me a clue although I don't understand why you need a separate utility to read the logs but...

Here's a snippit from the service log:
          message=The following backups have been successfully created: I:\My backups\MGA Backup\My_Partitions_diff_b6_s3_v1.tib
id=15;  level=2;  module=11;  code=1026;  date/time=9/26/2016 12:06:27 AM
          message=Validate Backup Archive Location: I:\My backups\MGA Backup\My_Partitions_diff_b6_s3_v1.tib  
id=16;  level=2;  module=1;  code=504;  date/time=9/26/2016 12:06:27 AM
          message=Pending operation 4 started: 'Validate Backup Archive'.
id=17;  level=2;  module=11;  code=0;  date/time=9/26/2016 12:56:20 AM
          message=Consolidate Backup Archive<tabpoint value=30><indent value=4>Location: <indent value=10><textcolor value=navyblue>I:\My backups\MGA Backup\My_Partitions_diff_b6_s3_v1.tib</textcolor></indent><indent value=4>Destination: <indent value=10><textcolor value=navyblue>I:\My backups\MGA Backup\My_Partitions_diff_b6_s3_v1_307B6087-73CA-4FA6-89CF-D2180F92D965.tib</textcolor></indent><indent value=4></indent>
id=18;  level=4;  module=495;  code=39;  date/time=9/26/2016 12:56:20 AM
          message=Failed to perform consolidation. Ensure that folder J:\My Backups\MGA Backup\ is not deleted or renamed.;  line_tag=0x6D5B4DCC0BA14A28

So that explains why the cleanup isn't happening.  My backup scheme uses an external drive (Drive I:) and I don't have a Drive J: in my system.  I don't think I ever did.  Is there a way to convince TI that Drive J: doesn't exist?

To answer your question I do have validate backup when created turned on.

 

 

David, one of the reasons for these errors is that drive letters have changed due to another USB device being plugged in before your backup drive at some point.  Acronis stores drive information in its internal database and then tries to perform automatic cleanup based on that information held.  The term consolidation is misleading as it is actually referencing the cleanup activity.

I would recommend running a Validation for your backup task to see if that will throw up any error messages that either can be Ignored, or will let you browse to the correct location of any missing files.

If you still encounter a problem, then I would recommend setting a drive letter for your backup drive from later in the alphabet via Windows Disk Management, then cloning your backup task and selecting the backup drive at the new drive letter for the new cloned task.  Once done, remove the old task settings to remove that information from the database.

Steve, I thought Acronis was allowing that in the latest version.  I havent' personally tried, but if this does work now, I'm assuming it would only be the case in a fresh/new backup task and not one that was created prior to the new version. Or, it still doesn't work :)

http://www.acronis.com/en-sg/support/updates/changes.html?p=38886

Other improvements:

  • Added the ability to create disk- and file-level backups from Windows File Explorer directly.
  • Improved reconnecting behavior for online backups when Acronis Cloud is not available.
  • Increased number of stored backup versions for Acronis True Image for Mac (now up to 20 versions).
  • Compression level and encryption method are now visible while editing an existing backup (available on Windows only).
  • The application now works correctly if a drive letter changes (available on Windows only).

Rob, I suspect that you are correct in that the changed behaviour for drive letters would only apply to new tasks created by ATIH 2017 rather than any carried forward from an earlier version, but have not test this myself either.