TIH 2014: initial backup is supposedly corrupt(?!)
I had a differential backup with around 20 pieces in the chain. It worked fine until this past week when it ran on schedule and it failed saying it was corrupt. So I moved (actually accidentally deleted) the old backup to start fresh. I ran it for the very first time and it failed saying it couldn't find the original backup file. I then cloned and deleted the original backup tasks and ran it. I figured nothing could go wrong since everything was new and fresh. And it failed with the error log below.
I then reformatted the destination drive ("B") and ran a CHKDSK. It found 0 bad file records and 0 bad sectors. I tried cloning the backup settings again and running it again fresh - and it failed in the same way again...
Please advise. Thank you so much!
1 Information 8/13/2017 12:50:52 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 2 Information 8/13/2017 12:50:52 PM Operation S-drive backup started manually. 3 Information 8/13/2017 12:50:52 PM Operation description: Stage Description. 4 Information 8/13/2017 12:50:56 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 5 Information 8/13/2017 12:50:56 PM Priority changed to Low. 6 Information 8/13/2017 12:50:56 PM Create Backup Archive From: Disk 2 To file: "B:\S-drive backup\S-drive backup.tib" Compression: Maximum Exclude: Files matching mask Match criterion: *.tib, *.tmp, *.~, S:\ALL DATA\Aaron\Desktop\^both^\, S:\ALL DATA\Eliezer\Documents\Backup archival ^acronis^, *^acronis^*, *^both^* 7 Information 8/13/2017 12:50:56 PM Pending operation 158 started: 'Creating partition image'. 8 Information 8/13/2017 12:51:44 PM Writing full version to file: S-drive backup_full_b1_s1_v1.tib 9 Information 8/13/2017 4:04:05 PM Pending operation 155 started: 'Saving partition structure'. 10 Information 8/13/2017 4:04:05 PM The following backups have been successfully created: "B:\S-drive backup\S-drive backup_full_b1_s1_v1.tib" 11 Information 8/13/2017 4:04:06 PM Validate Backup Archive Location: "B:\S-drive backup\S-drive backup_full_b1_s1_v1.tib" 12 Information 8/13/2017 4:04:06 PM Pending operation 3 started: 'Validate Backup Archive'. 13 True Image 8/13/2017 4:14:21 PM Operation with partition '0-0' was terminated. Details: The archive is corrupted (0x70020) Tag = 0xF5F8CBCF76155663 14 True Image 8/13/2017 4:14:21 PM The archive is corrupted 15 True Image 8/13/2017 4:14:21 PM Operation has completed with errors.


- Log in to post comments

Thanks, Steve. You're correct; I misspoke. The failure was upon the initial validation. I did try running a separate validation and it also failed.
I found a useful post recommending deleting the Archives.xml file which did work. Seems a bit extreme, but it worked.
- Log in to post comments

Eliezer, thanks for giving feedback on the solution that you found. This will work for your older version of the product but later versions no longer have an archives.xml file in the database folder, so would need a different solution.
- Log in to post comments

But that success was very short-lived because I immediately ran into another problem. The initial backup worked and validated successfully. But I tried running a second (incremental) backup and it failed with the log below...
:-(
1 Information 8/14/2017 1:51:43 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 Information 8/14/2017 1:51:43 PM Operation S-drive backup started manually.
3 Information 8/14/2017 1:51:43 PM Operation description: Stage Description.
4 Information 8/14/2017 1:51:48 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
5 Information 8/14/2017 1:51:48 PM Priority changed to Low.
6 Information 8/14/2017 1:51:48 PM Create Backup Archive From: Disk 2 To file: "B:\S-drive backup\S-drive backup.tib" Compression: Maximum Exclude: Files matching mask Match criterion: *.tib, *.tmp, *.~, S:\ALL DATA\Aaron\Desktop\^both^\, S:\ALL DATA\Eliezer\Documents\Backup archival ^acronis^, *^acronis^*, *^both^*
7 Information 8/14/2017 1:51:51 PM Pending operation 158 started: 'Creating partition image'.
8 Information 8/14/2017 1:56:24 PM Writing incremental version to file: S-drive backup_inc_b1_s2_v1.tib
9 Information 8/14/2017 1:56:24 PM Pending operation 155 started: 'Saving partition structure'.
10 Information 8/14/2017 1:56:25 PM The following backups have been successfully created: "B:\S-drive backup\S-drive backup_inc_b1_s2_v1.tib"
11 Information 8/14/2017 1:56:25 PM Validate Backup Archive Location: "B:\S-drive backup\S-drive backup_inc_b1_s2_v1.tib"
12 Information 8/14/2017 1:56:25 PM Pending operation 3 started: 'Validate Backup Archive'.
13 True Image 8/14/2017 2:01:33 PM Operation with partition '0-0' was terminated.
Details:
The archive is corrupted (0x70020)
Tag = 0xF5F8CBCF76155663
14 True Image 8/14/2017 2:01:33 PM The archive is corrupted
15 True Image 8/14/2017 2:01:33 PM Operation has completed with errors.
- Log in to post comments

Eliezer, the only other suggestion would be to try doing a Repair install of your ATIH 2014 in case something has got damaged/corrupted in the application?
A repair install is where you re-install ATIH 2014 over the top of your existing installation without uninstalling. You may need to download the final version of the ATIH 2014 installer from your Acronis Account online.
- Log in to post comments

Steve, thank you. I did exactly that and the log below is what happened with my initial backup.
Incidentally, the whole issue with failing validation is on the backup of this drive ("S") but not my other ("C") drive's backup... Is that indicative of anything with the drives that I'm backing up?...
1 Information 8/14/2017 3:13:07 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 Information 8/14/2017 3:13:07 PM Operation S-drive backup started manually.
3 Information 8/14/2017 3:13:07 PM Operation description: Stage Description.
4 Information 8/14/2017 3:13:12 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
5 Information 8/14/2017 3:13:12 PM Priority changed to Low.
6 Warning 8/14/2017 3:13:12 PM The initial full backup version is not accessible at the moment.
7 Warning 8/14/2017 3:13:12 PM The specified file does not exist.
8 Warning 8/14/2017 3:13:12 PM The system cannot find the file specified
9 Information 8/14/2017 3:13:12 PM Create Backup Archive From: Disk 2 To file: "B:\S-drive backup\S-drive backup.tib" Compression: Maximum Exclude: Files matching mask Match criterion: *.tib, *.tmp, *.~, S:\ALL DATA\Aaron\Desktop\^both^\, S:\ALL DATA\Eliezer\Documents\Backup archival ^acronis^, *^acronis^*, *^both^*
10 Information 8/14/2017 3:13:12 PM Pending operation 158 started: 'Creating partition image'.
11 Information 8/14/2017 3:14:03 PM Writing full version to file: S-drive backup_full_b1_s1_v1.tib
12 Information 8/14/2017 6:25:55 PM Pending operation 155 started: 'Saving partition structure'.
13 Information 8/14/2017 6:25:55 PM The following backups have been successfully created: "B:\S-drive backup\S-drive backup_full_b1_s1_v1.tib"
14 Information 8/14/2017 6:25:55 PM Validate Backup Archive Location: "B:\S-drive backup\S-drive backup_full_b1_s1_v1.tib"
15 Information 8/14/2017 6:25:55 PM Pending operation 3 started: 'Validate Backup Archive'.
16 True Image 8/14/2017 6:26:17 PM Operation with partition '0-0' was terminated.
Details:
The archive is corrupted (0x70020)
Tag = 0xF5F8CBCF76155663
17 True Image 8/14/2017 6:26:17 PM The archive is corrupted
18 True Image 8/14/2017 6:26:17 PM Operation has completed with errors.
- Log in to post comments

I just ran a CHKDSK on the source "S" disk; no problems...
S:\>chkdsk
The type of the file system is NTFS.
Volume label is Data.WARNING! F parameter not specified.
Running CHKDSK in read-only mode.Stage 1: Examining basic file system structure ...
227584 file records processed.
File verification completed.
746 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
247012 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.9715 data files processed.
CHKDSK is verifying Usn Journal...35447680 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.3815317 MB total disk space.
1307341516 KB in 166738 files.
55048 KB in 9716 indexes.
0 KB in bad sectors.
448219 KB in use by the system.
65536 KB occupied by the log file.
2538125 MB available on disk.4096 bytes in each allocation unit.
976721407 total allocation units on disk.
649760212 allocation units available on disk.S:\>
- Log in to post comments

I ran Memtest86+ and see 80+ errors. Now what?...
Could that be causing backup errors for one drive but not the other?
- Log in to post comments

Eliezer, if you are seeing errors from Memtest then it suggests that you have a memory module going bad that you need to try to identify / isolate.
Memory problems are unpredictable at best and can impact on different areas / applications without any reason or pattern - all depending on what touches the problem area of memory and how it is touched.
As mentioned earlier, the calculation of the checksum done by Validation is predominently a memory intensive function, so perhaps it shows more because of moving data in/out from the external drive and doing the checksum calculation all together, though I suspect that your other backups will have similar stresses to memory, so ???
- Log in to post comments

OK, I've contacted the RAM manufacturer for replacement.
I've run a number of backups on both C and S --- C validates consistently while S fails validation consistently. Could it be due to the fact that S is a 4 TB drive while C is only 250 GB?
- Log in to post comments

Eliezer, your 4TB backup will need more memory to validate / verify the checksum than your 250GB backup for sure. Hope all goes well with the RAM replacement conversation.
- Log in to post comments