Salta al contenuto principale

ATI does full backup instead of incremental (yes, I've already researched similar existing issues here)

Thread needs solution

Ok, so here's what happened:

1) I created a brand new incremental backup task, set to create an initial full version and then only incrementals afterward. In this backup, disk E: which is a raid0 is backed up in its entirety to disk A: which is also a raid0 of the same size. Disk E: happens to be more than half full.

2) I did an initial full backup of E to A, no problem.

3) After the full backup had completed, I examined the settings of the backup task, where I noticed a little warning that stated there might not be enough free space on the target disk to do the backup (may or may not be relevant).

4) I then attempted to do another backup which should have been incremental, but instead appeared to be full. I attempted this incremental backup immediately after the initial full backup had finished. There was no defragging, and pretty much no files changed. The incremental backup would have been very small and would surely have fit on the target disk along with the initial full backup.

I only encounter this problem with this very large backup (2.1 TB).

0 Users found this helpful

Nat Milder wrote:

2) I did an initial full backup of E to A, no problem.

Did you manually perform a full backup, or was this the first run of the incremental backup task. Every incremental backup task starts with a full backup created by that task, irrespective of whether you previously manually created full backups.

Still not clear. Are you saying that the incremental backup task ran on schedule the first time and created a full backup, and that the second time it ran on the schedule it also created another full backup?

1) I created a brand new incremental backup task. I did not specify it to run on a schedule.

2) I manually ran the backup task for the first time. It created a full backup as intended.

3) I manually ran the backup task for a second time. In the little status bar that appears when a backup is actively running, it showed the target output filename of the currently running backup task as "Storage_Backup_1_full_b1_s1_v1.tib", implying, as far as I can tell, that it was attempting to perform a full backup instead of an incremental one.

I don't have the option set to create a full backup after n-incremental backups. Just one full backup and then incrementals thereafter. I kept the scenario as cut and dry as possible to eliminate as many variables as I could. Put plainly, the software is not behaving as expected.