Skip to main content

The last backup has failed

Thread needs solution

I have been using True Image for about a month. I have the program set to do an incremental backup every morning. I just noticed 'The last backup has failed', which has happened for the past five days. I reviewed the log files and noticed a red 'X' beside 'Backup date cannot be found'. That appeared twice and at the top a red 'X' beside 'Operation has completed with errors'. I have attached a snapshot.

Can anyone tell me how to get the backups back on track?

Thanks.

Glenn Dennis

Attachment Size
backup_failed.jpg 61.9 KB
0 Users found this helpful

The information about your backups is stored in a database and it appears to have become corrupted. Rather than simply start over with the same settings, my suggestion would be to create a backup scheme which does not involve consolidation--which your scheme does every day.

Click on link#2 inside my signature below and look at example figure"11-Inc". The help file on custom scheme may also be of benefit.
This example create a full plus 6 incrementals. Then a 2nd full is created with a new set of 6 incrementals. Then a 3rd full created with a new set of 6 incrementals. Then a 4th full with a new set of 6 incrementals. At this point, you have 4 "Recent version chains" as per the example.

After the next full is created, then backups set #1 will be deleted (1full+6inc) and 6 incs added to the most recent full. Next, a new full will be added and the backup set #2 will be deleted, etc. Much like an escalator with the new full coming on and older chain dropping off and the chains kept are those in the middle. 4 fulls +4 sets of 6 incs are the retaining rules in my example of 6 and 4.

You can change the 6 and 4 examples to fit your needs but understand a large number of consecutive incs can be less safe. If one inc becomes bad, then all newer links are worthless. There is no magic number for inc but my personal preference would not exceed 10 incs before creating a new full.

Keeping x number of complete chains (recent version chains) is a better option as compared to keeping based on elapsed days or elapsed space--which also has options listed--but not my recommendations.

One of my personal rules is also never edit an existing task. If edits needed, create a new task and start over.
Another personal rule is that each task points to its own storage folder with no intermixing of backup files. One folder or sub-folder for each backup scheme.

You may wish to adjust the 6 and 4 to fit your needs but this method has worked for me and I believe it would also for you--if it fits your needs.