Direkt zum Inhalt

Backup and recovery tab says last backup failed, log says otherwise

Thread needs solution

While composing my last forum post about comparing backups, opened the program and saw that on the "Backup and recovery" tab, the entry for my daily backup task said

"The last backup has failed"

However, looking at the log, I find that not only did the last backup finish completely, there are NO failed backups mentioned in the log at all.

There are a few "Warning" entries from the few days after I installed the program when I was testing various configs and manually terminating the backup in progress, but otherwise, everything is green.

Any idea what that's about?

0 Users found this helpful

It's that darned internal ATI database. Go look in the storage directory, are the backups there? Can you validate the last one? Is it the same date as the one ati is reporting as having failed?

If so, then just run another backup to get rid of the disconcerting message. IF the backup runs fine, then you should be good to go. If not, then delete the task and create a new one. The database is abit like Homer Simpson, doesn't take much to confound it.

When viewing the log, click the "Reset all filters" option and reselect the event source to be the specific task again.
If you do not see what you need, You may have to toggle the 3 types sort options.
Successes, warnings, errors, etc

I ran a validate on both backup chains after seeing the message, and both were deemed OK.

Running the validate changed the message to "The backup is valid."

Last night's backup happened to be a full backup, but the message left from the earlier validate is still there.

Even though last night's backup probably is valid, the message doesn't actually pertain to it.

It would be nice if the status line were cleared or updated to reflect the status of the most recent operation. I suppose saving and displaying DATED messages pertaining to outright failures would be OK.

Did all that, and there are no errors anywhere in the log for this installation of TI.

I was surprised to see a number of errors displayed going back as far as 2009! Looks like TI never forgets, unless you tell it to. Now that I know that the current installation is working correctly, I think I'll delete the log and start over.