Differential Backup Plan - Looks to be saving full backup each and every time
I have a differential backup plan I execute on a weekly basis. Executing a full backup after every 5 differentials.
You'll notice on about the 4th series, it appears to be doing a full backup each and every time. A couple of them even corrupted (v1-2).
Any advice on how I can get it going back to a true differential? Let me know if you need more detail.
Thanks.
Scott
Attachment | Size |
---|---|
ati_backups.JPG | 125.73 KB |


- Log in to post comments
In reply to Scott, we will need to see… by truwrikodrorow…

Hi Steve, where do I find the log files?
Also, the problem appeared the very next scheduled backup after a previous weeks restore.
Thanks in advance.
Scott
- Log in to post comments

Scott, please download the MVP Log Viewer tool from the Community Tools link in my signature and use this to view the log files, this will also show you the location of the same and allow you to make a copy of any you want to share here.
If you are restoring your C: drive contents, then this can be expected behaviour, as you are also restoring the contents of the C:\ProgramData\Acronis\ folders where ATI stores its Database with information on backup files. This database information will not know about files created by the backup image you restored from or any later ones as it was captured before that file was present.
- Log in to post comments

I looked at the log files all look like they "succeeded". However, I am missing log files from 10/30 - 11/20, which is the time period I was doing some "Restore activities" a coupe of times. So, I don't know?
When I do a restore, is there anything special I should do when the normally scheduled backups is to next occur?
Scott
- Log in to post comments

Scott, I have tended to use the 'Clone settings' option after doing a restore where my OS partition is involved, and started off with a fresh new backup for the cloned task so that I avoid the issues with trying to carry a backup task over such a change.
When you clone a task, you get a duplicate task of the same name prefixed by (1) - I then remove the original task, which cleans the database of any reference to it, then rename the new clone back to how it was but with a minor suffix, i.e. -1 to start again. Doing this, I can still keep the backup files for the original task and not trip over creating new backup files with the exact same name which would cause them to get a _v1-1 file name ending.
- Log in to post comments

Perfect, I'll make a note of that going forward. Thanks Steve.
- Log in to post comments