HELP - "Error 0x70020: The backup is corrupted, but you can still try to recover data from it."
Hello ATI2018 Forum,
Trying to do a partition (win10 C) backup to my Synology NAS as a scheduled backup. If I run it manually it works fine. Verification of the backup also works fine. I do scheduled validation once per month and am trying to do scheduled backups once per week.
I have run a "clean" disk check on the drive. Win10 nor does WD utilities see any errors on the disk.
All that said, why do I get failures?
2020-11-29T18:30:01:593-05:00 12304 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-11-29T18:30:01:594-05:00 12304 I00640002: Operation Golfer1 started by schedule.
2020-11-29T18:30:04:669-05:00 12304 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-11-29T18:30:04:674-05:00 12304 I013C0000: Operation: Backup
2020-11-29T18:30:04:676-05:00 12304 I0064000B: Priority changed to Low.
2020-11-29T18:31:06:220-05:00 12304 I000B03F0: Create Backup Archive From: Disk 1 To file: "\\192.168.1.X\Backup\{subfolder name]\<filename>1.tib" Compression: {some text removed}
2020-11-29T18:31:06:244-05:00 12304 E00070020: Error 0x70020: The backup is corrupted, but you can still try to recover data from it.
| trace level: error
| line: 0x33004b92f00b7763
| file: c:\bs_hudson\workspace\723\core\resizer\backup\imglist_persist.cpp:282
| function: resizer::ImageListReader::LoadImageList
| line: 0x33004b92f00b7763, c:\bs_hudson\workspace\723\core\resizer\backup\imglist_persist.cpp:282, resizer::ImageListReader::LoadImageList
| $module: ti_demon_vs_15470
2020-11-29T18:31:06:469-05:00 12304 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bce5f
| file: c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617
| function: main
| line: 0x9f2c53c72e8bce5f, c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617, main
| $module: ti_demon_vs_15470
Thanks for the insights Steve!
ATI was installed by me under my admin level account on my Win10 PC. Also "funny" is that I have three other (total of four) backup scheduled backup jobs that now run without issue. They are all of different folders on my Synology NAS and the backup files are stored on a 2nd (D:) internal HDD on the same Win10 PC.
I ready in one of the older ATI2015/16 posts that the same error message could be related to what ATI believes is an issue with the source HDD, but I have run a few different disk checks & tools and none report any errors on the drive.
I also run all my backup jobs on different days to help ensure there are no competing tasks that might clash with each other. Are there any additional logs or debug level commands that can be enabled in ATI to help provide more info?
Over the next few days I will try a series of tests (including your suggestion about using the Windows scheduler) to see if i can further ID the issue.
### UPDATE ####
In checking things out I discovered occasional slow response from my Synology NAS. Checking this out, i found that the disk utilization was pegged at 100%. A few google searches later I found that others had issues with the Synology AV service running and causing high disk utilization & other performance issues. I even had to hard boot my NAS to regain access to the management interface but once in I removed the scheduled AV scans (not sure where those came from).
I re-setup all my ATI backup jobs and ran each manually to be sure they worked. I have also re-enabled the backup schedule and the first two jobs ran without issue. What appears to have been the issue is that the other NAS disk activity may have been occasionally higher when the backups were running over night. No one ever noticed any file access issues during the day so I never considered the issue might be the NAS.
Will update in a week or two as to how things are progressing.
Thanks for sharing the update about the AV scans on your Synology NAS - have been checking my own and checked the AV settings there!
### UPDATE ####
Life has been much better since disabling Synology AV. Again, Not sure how or when that went sideways as its been months since I even touched Synology. I will add that in late OCT, i lost my primary WIN10 HD and had to try to recover from ATI backup. While the files were located on my Synology share, there were issues with the backup files and was not able to do a clean recovery. I had to re-install ATI2018 and re-add the backup jobs ..... and here we are today.
Hopefully these insights help others as they run into issues.