Incremental Backup doing full back up everytime
I am having issue on my laptop computer, where every backup that ATI 2016 does after the first backup is essentially another full backup. I don't have this same issue on my desktop computer. Even if I run the backup on the laptop immediately after the last incremental backup, it still wants to back up the entire disk.
The backup is configured for a custom scheme, incremental back up method. Backup is for all partitions on the disk.
Both computers are Window 7 Premium, 64bit. Both have Disk Defragmenter turned off.
Both are running Outlook, but the .pst files are stored on another harddive in the system.
System restore is configured on both computers for disks being backed up.
Both are running the same anti-virus and anti-maleware software.
Why the difference in operation?
Any thoughts would be appreciated.
Greg, welcome to these User Forums.
Very difficult to advise why your one Windows 7 computer is making Full backups every time when you have configured your backup to make incrementals?
Please download the MVP Log Viewer tool from the Community Tools link in my signature and use this to check the backup task log files for the messages written there, hopefully this may help throw more light on what is happening.
Also, how are the full backup files being named on your backup drive for this problem computer? It may help if you can a screen shot of the files to show this.
Has this user problem been resolved as I have similar problem. For some reason when I run my Incremental backup it is doing a Full backup now (it was working fine for a long time before all this).
I am running Win10.
The file names are correct for example (1)Differential20617_diff_b3_s3_v1.tib so why is it doing a Full Backup?
Terry, if your file names show _diff_ in their names then they are not full backups but are differential ones.
It is possible, especially with Windows 10 and regular new updates etc, that the size of your differential backups can be equal to or larger than your original full backup size.
This is one of those cases where I would recommend going for a new full backup, which you could force by using the 'Clone settings' option for your current task, and pointing the new backups to a different destination folder (for safety and clarity).
One point here particular with Windows 10, in the Exclusions tab for your task, consider excluding the C:\Windows.old folder contents that gets created whenever Windows does an upgrade (as for the Creator's update) then gets deleted automatically again around 10 days later, but would count as changes for your backup task. This folder can be very large, from around 5GB up to 20GB in size!