Skip to main content

Acronis does not make full backup

Thread solved

I have Acronis 2017 home installed on a Windows 10 Home PC.  It is set to make a differential backup once a week and a full backup after five differentials, keeping two chains.  However, it has begun not making a full backup, just differential.  I have looked through the topics but didn't find anything, so any help is appreciated.

Ken Carney

0 Users found this helpful

Ken, sorry but very difficult to suggest a reason for the behaviour you are seeing without more information to work with.

Please download the MVP Log Viewer tool and use this to check the log files created for each time your backup task runs - the log should hold some clues as to what is happening here? (Link in my signature).

My guess is that the script has been modified and saved and the version chain count is reset as a result. This was the behavior in 2015-2017, but was fixed in the latest version of 2018 and all of 2019. Basically, assume that there will be 5 more diffs if you don't mess with the script (even though you're already at 5 or beyond) and a full should be coming. 

 

I upgraded to Acronis 2019 and initiated a backup, but it did another differential although there were already 11 differentials before the last full backup.  It seems whatever script issues there were with 2017 carried over to the 2019 upgrade.  I will check and see if Acronis support is available for my upgrade (it had expired, only 90 days I think, for the 2017 version).

Kenneth, it might just be carried over from the old backup script.  Create a new backup (perhaps a test with just a small folder of data) and 3 diff retention.  Manually run it back to back 4 times (full1a, diff 1a, 1b, 1c and hopefully a new full2a).

If that works, assuming it does, go in and edit the new task to 4 diff retention and run it back to back 5 times again real quick (diff 2a, 2b, 2c, 2d and hopefully a new full3a).

If so, then we can consider that it's carry over from the old task and that new ones should operate correctly.  If not, then yeah, may still be bugged.  In my own case, I've been able to modify the backup version chain count without any issues (adding more or less to the chain at times).

OK, that worked.  Since the 2019 upgrade continued the error from the 2017 version, it sounds like I need to make a new backup scheme and delete the old one assuming everything works OK.  Thanks very much for your help.

Great to hear that worked. Yeah, seems like that will do the trick and hopefully it's smooth sailing from then on. If you keep the old backup .tibs for retention, make sure to give the new job a unique name - something at least a little different than the old job.