Skip to main content

"Failed due to an error" but still validates

Thread needs solution

After my first backup to a newly reformatted, bootable external hard drive, the Activity tab shows me "Failed due to an error" messages at 12:11 AM and 2:35 AM and 5:00 AM. The final three .tibx files show those same times. When I right click on any of the 181 .tibx files, OR when I open ATI 2020, the validation begins. It is running now with varying estimates of time to completion. I don't understand what is going on. Can a failed backup be any good? Double-clicking any .tibx file in Windows Explorer tells me the file is empty, but the file sizes are identical except for the last one. In .tib files double-clicking in Windows Explorer showed me the directory of that file so I could copy out one individual file. I WANT THAT FUNCTIONALITY BACK!
Any idea what can cause the pauses and failure messages?

0 Users found this helpful

Kent, welcome to these public User Forums.

If you are seeing 181 .tibx files where the majority of those files are 'empty' suggests that there are other issues at work here as well as the new file format in ATI 2020!

Unfortunately, all these .tibx files for a single task are interdependent, and if you are validating this task, it will read through all of them to try to establish if the chain is valid.

The logs for the task should give more information about why this many files are being created but just on the information here, it says that the task is failing over & over, retrying and failing continually.

The MVP Log Viewer tool (link below) can show some basic log information for the task but the full diagnostic detail is stored in the backup_worker logs not shown by the tool because have been introduced in 2020.

Under normal circumstances, you can double click on any .tibx file the same as with .tibs and get the same functionality as with previous versions.

I would suggest checking the logs or zipping up some of the latest ones and attaching here, plus running CHKDSK against all the drives involved in the backup task source & destinations if possible.