Okay, upon further review, it looks like the consolidation completed successfully one night, and then failed the next night. I have two files in my backup location that look to be temp files created during consolidation. After reading through Grover's help doc (thank you very much by the way), it looks like a backup set (the full backup and all diff's or inc's) is not deleted until all diff or inc backups have been consolidated. Once they have been consolidated you are left with a single backup from that set that contains all of your diff or inc backups compiled together. I suppose this becomes an issue if the consolidation does not work correctly, because it appears that TI just straight up ignores the backup rules once something goes wrong. The logs reference the violation, but it doesn't look like it's doing anything to address it. My backup location has a max number of 7. I currently have 10 files in there. 7 backups, two huge consolidation temp files, and the location config file. I am going to reconfigure the scheduled task to do only full backups and see if that is successful. IMO, this consolidation method is just asking for trouble. As much as it pains me to admit, Ghost actually has excellent and easy to use/understand scheduler and retention options. Sadly, that's about the only thing that app does well, but Acronis would do well to look into how Symantec handles those functions.