Direkt zum Inhalt

ATIH NG Disk backup failing ...

Thread needs solution

Hello,

I recently upgraded to ATIH 2017/NG. I initially did an "upgrade" from ATIH 2015, but didn't get the ransomware protection, so uninstalled and reinstalled ... Everything seemed to go OK, but now I am finding that disk backups are failing constantly, and folder backups are intermittently failing.

Here is an extract from today's disk BU log:

2017-06-02 12:06:58:914 2588 I000101F8: Pending operation 172 started: 'Creating partition image'.
2017-06-02 12:08:43:680 15044 I00640000: Writing full version to file: DiskC_full_b1_s1_v1.tib
2017-06-02 13:39:05:805 2588 I000101F8: Pending operation 172 started: 'Creating partition image'.
2017-06-02 13:39:43:694 2588 I000101F8: Pending operation 172 started: 'Creating partition image'.
2017-06-02 13:39:43:713 2588 I00640000: The following backups have been successfully created: "F:\BU\Images\DiskC_full_b1_s1_v1.tib"
2017-06-02 13:39:44:044 2588 I000B0402: Validate Backup Archive Location:              "F:\BU\Images\DiskC_full_b1_s1_v1.tib" 
2017-06-02 13:39:44:069 2588 I000101F8: Pending operation 4 started: 'Validate Backup Archive'.
2017-06-02 13:41:02:106 2588 E000101F6: Error 0x101f6: The backup is corrupted, but you can still try to recover data from it.
| trace level: error
| line: 0x65b5eb7011094700
| file: k:\6206\processor\diskadm\da_commit.cpp:345
| function: DaProcessor::CommitImpl::OnDaError
| line: 0x65b5eb7011094700, k:\6206\processor\diskadm\da_commit.cpp:345, DaProcessor::CommitImpl::OnDaError
| $module: ti_demon_vs_6206

Any suggestions, other than uninstall, clean, reinstall ... ?

(I'm happy to do this too, but just wondering if there is anything simpler/quicker to try before that?)

Thanks,

Colm,

Dublin, Ireland.

0 Users found this helpful

Colm, welcome to these User Forums.

You may wish to deselect the option to including doing a validation at the end of your backup process - this is on the Advanced Options page for the task configuration.

Advanced Validation Options.png

I have not used this option for a long time as it is known to cause this type of intermittent error message and doesn't really add any real value.  You could use the second option to validate (as a separate task regularly) or could simply run an on-demand validation, though double-clicking on the backup image file in Explorer and picking a few random files / folders to copy to a temporary folder is as good a test short of doing a full restore of the backup to a spare drive.

In your log file, the earlier message did say: 

The following backups have been successfully created: "F:\BU\Images\DiskC_full_b1_s1_v1.tib"

So the only other question is what/where is your F: drive that you are backing up to?  If this is a USB drive, then issues can arise if you connect a USB 3.0 drive to an older USB 2.0 port due to the increased power requirements needed by the 3.0 device.  You should try to connect drives directly to the computer not via extension USB leads or monitor ports etc.

Thanks Steve.

I have always done the "validation" in previous versions, without issues!
But time to change I guess! :-)

Just for reference F is an SSD attached via USB 3.0 to a USB 3.0 port. It had been working fine on ATIH 2015 ...

I will try your suggestion of separating the backup from the validation ...

Thanks again,

Colm.