Unexpected consolidation occurred during scheduled backup job
I am running ATI 2014. I have two backup jobs that run as follows: File backup scheme; 1 full and 3 incrementals; Store no more than 2 recent version chains; no validation; Performance-Compression: none; shedule-Once a week on Sunday. The target folder is on a NetGear NAS with 2 TB of space. The disk had more than enough space to hold another of the largest full backup that should have been produced.
(I have another job that performs a Partition backup on a similiar plan. This job worked normally.)
These two jobs have been running flawlessly for months. Suddenly this last Sunday something went wrong. The jobs were due to perform the third incremental. But an incremental was created and after that was complete the job performed a consolidation, then deleted the older backup set, full and incrementals. The older backup set should not have been deleted until next week.
The sequence numbers are:
D-Drive_full_b36_s1_v1.tib.
D-Drive_inc_b36_s2_v1.tib.
D-Drive_inc_b36_s3_v1.tib.
D-Drive_inc_b36_s4_v1.tib.
D-Drive_full_b37_s1_v1.tib
D-Drive_inc_b37_s2_v1.tib
D-Drive_inc_b37_s3_v1.tib
D-Drive_inc_b32_s3_v1.tib
The _b36_ set was deleted. (note the _b32_ sequence number in the last entry) Since these sets are now trashed, I'm guessing I'll need to restart the whole sequence.
Why would a perfectly working job suddenly do something like this? Is there something I can do to head this off in the future?
One additional piece of info: I have another file backup that runs on Monday. Due to other reasons, I needed to cancel this job while it was running. Could this have glitched something? How can I verify my other jobs ok?
I have the log files if that will help. But I don't see anything that say why this happened.


- Log in to post comments