9 month old backup job has been oddly corrupted.
I have a system drive backup to the NAS that I've been running on schedule for 9 months. It runs on the second and fourth Tuesday of the month, every month. Full backups only, saving no more than 2 recent backups.
So last week it suddenly decided not to work. I didn't realize it for a number of days. The log gives me an error 0x1e50023 Cannot access backup file System_full_b19_s1_v1.tib. After 5 retries (every 20 seconds) it gave up.
Looking at the folder, I see b17 and b18 versions so it never got b19 started.
Next I tried to validate the archives and they failed (image below), which ended up causing the backup job to simply disappear from the ATI user interface. I can double click on the existing .tib files in the Windows Explorer and they look fine from there, but I cannot validate them and I cannot add them as existing backups. I tried with both files.
Next, after recreating a new task and running it successfully (different name), I closed ATI and tried again to validate (using the Explorer context menu). This time it seems to be working, and when I look at the backup list, the job is back and all prior activity shows up. I'll try to get that back on schedule to see what happens.
What I forgot to mention is that I tried to open the backup task in the UI and I could not do so because of the "problem". I had wanted to run the backup and needed to disable my pre-command that controlled the schedule. It was then I tried the validate and it too failed, then causing the backup task to just disappear.
Now there is no way of knowing what would have happened if it tried to run the backup on schedule although I expect it may have failed.
It is interesting that after completing the validation, the task is back and looks like it should run on schedule. I'll find out next Tuesday. So yes, it does seem that the problem was in the database and not with the files themselves.
I gotta say, I've run into corrupted backups at various points in time too - not just with Acronis, but with some other backup programs too. Seems like it's just a matter of time in some cases. That's why I still take regular full backups and try to limit the number of incrementals and/or the amount of time between fulls to avoid corruption. Of course, if the database goes haywire, that can cause issues in the application, but I've still always at least been able to recover with rescue media since it hasn't cared about the database (at least in 2019 and earlier...)
Hopefully, the next backup will continue on now and looking forward to your results next week.
Results last night were not good. I got the same failure. Also, I created a new task last time which did exactly the same thing. The new one was named differently, but to the same folder. I was able to manually run the backup just fine but when it came to running it on the schedule it too failed.
I just created another new task, but set to run to a different folder.
All my other backup tasks to the same NAS from this PC and my wife's all work well. I'm hoping changing the folder will solve something. Life's a mystery.
Did using a different folder help at all?
Bobbo_3C0X1 wrote:Did using a different folder help at all?
I was very hopeful, but since it only runs on the second and fourth Tuesday of the month, I need to wait until next Tuesday.
Roger that.
OK, all is back in sync. But for some reason I think I left it in the original folder. What made it work was to remove the backup task from ATI and then add it back again.
That's the problem with having a bi-weekly schedule... you forget from week to week what you did. Anyway, the backs are back on schedule and even the automatic cleanup worked.