Acronis True Image Home 2009, build 9707, Windows Vista Ultimate SP!, 32 bit. For reference, I am using the methodology described by Vlad V, post #4 here: https://www.wilderssecurity.com/showthread.php?t=228046 This method allows me to schedule 7 full backups, and when the eighth is made, the oldest backup is deleted. I have had two days where the "consolidation" part of this part has not worked (IMO). It still creates a full backup, but it doesn't drop the oldest full backup. When I look at the logs for the days that do drop the oldest full backups I see the following: My Full Backup1 (Tuesday, June 15, 2009 12:10:01 AM 1. Information 6/15/2009 12:01:01 AM Operation My Full Backup1 started 2. Information 6/15/2009 12:01:03 AM Analyzing partition 0-0... 3. Information 6/15/2009 12:01:03 AM Analyzing partition C:... 4. Information 6/15/2009 12:01:04 AM Analyzing partition D:... 5. Information 6/15/2009 12:01:04 AM Analyzing partition 0-0... 6. Information 6/15/2009 12:01:05 AM Analyzing partition E:... 7. Information 6/15/2009 12:01:06 AM Analyzing partition F:.. 8. Information 6/15/2009 12:01:07 AM Create Incremental Backup Archive From Disk 1 To file: "F:\Fullbackup(32).tib" Compression normal 9. Information 6/15/2009 12:01:07 AM Pending Operation 138 started: "Creating partition image" 10. Information 6/15/2009 12:01:07 AM Locking partition C:... 11. Information 6/15/2009 12:12:23 AM Pending operation 138 started: "Creating partition image" 12. Information 6/15/2009 12:12:38 AM Locking partition D:... 13. Information 6/15/2009 12:12:38 AM Pending operation 135 started: "Saving partition structure" 14. Information 6/15/2009 12:12:38 AM Consolidate Backup Archive Location: "F:\Full Backup(33).tib" Destination. Fullbackup(33)_32E10B.. 15. A red circle with an X in it and the work Error 6/15/2009 12:12:38 AM Backup date was not found. 16. Information 6/15/2009 12:12:38 AM Operation has succeeded. On the two days where the consolidation part did not work, the log looked just like that above, with the exception that lines 14 and 15 above were omitted. This left the log with 14 entries, and it still said the "Operation has succeeded". Has anyone that is using this method had a similar problem? If so, have you determined why tlhis is happening? Why is it saying the operation has succeeded when it did not perform the task that was scheduled? Why did it perform any task other than the one that was scheduled? I don't think there is a big loss here. In fact, I believe that it did perform a full backup, it just broke the chain and didn't delete the oldest full backup. The latest incident occured on June 16, 2009 and it validated in Windows as well as when the Rescue Boot CD was used. When using the Rescue Boot CD I started a Restore and could see all my drives and I performed all steps except the "proceed" step. When it reached the "Summary" screen it posted the following information: Summary Number of Operations 3 1. Restoring partition Hard disk: 1 Drive letter: C:->F: File System NTFS Volume label: SATA01_C Size: 122.1 GB 2. Restoring partition Hard Disk: 1 Drive letter: D:->F: File System: NTFS Volume label: SATA02_D Size: 342.7 GB 3. Restoring partition structure Hard disk: 1 I would appreciate help from anyone on this matter. June 17, 2009 Again, today it did a full backup, but not the scheduled full backup that is supposed to delete the oldest backup and leave me with 7 full backups. I now have 9 full backups, the last 2 do not have the consolidation part in the log, it did not work, or was omitted. However, under Windows, it did validate. I only have space for about 3 more full backups in my archive. Should I delete my scheduled tasks and start over. I am unable to figure out why it stopped doing the consolidation part of the scheduled task. Any suggestions at all. Sure would like to hear from Vlad V or anyone else using this methodology. JUNE 18, 2009 Same thing again.