Skip to main content

Backup initially corrupt, then OK but ...

Thread needs solution

I do a scheduled (daily, 10 PM)  incremental backup (with a full after every five incrementals).  I run a Verify each time.  Since last Tuesday evening, after an incremental (but not after the full) backup, about 20 minutes into the verification process, TI message:  "The backup is corrupted, but you can still try to recover data from it."

If I then select, from the backup's drop down menu, "Verify", the backup will create another incremental backup file, and the verification succeeds.

Any thoughts? 

0 Users found this helpful

Just to be on the safe side, I would check the source disk for disk/ file errors.

Depending upon what is found,, if none, you may even want to check the target disk as well for disk errors.

Thanks for the suggestion, Grover. 

I'm not sure of the terminology -- source vs target, but:

The backups storage disk is a RAID1 array on my Synology NAS.  I just did a quick test (SMART) and they both show completely normal.  I'll run the extended test tomorrow (it takes about 4-5 hours) but I'd be surprised, with a RAID1 array, if there were any issues.

My computer being backed up has a pair of SSD's in RAID0. For unrelated reasons, but after this problem started, I did a "Verify" using Intel's RST driver.  That is supposed to pick up any bad blocks -- but no errors were found.

Any other thoughts? 

Run chkdsk c: /f /r from a command prompt. c: refers to the drive letter of the drive you want to scan. Do a search in windows for cmd to bring up the command prompt. If you are scanning the system drive it will ask you to reboot.

Perhaps you are not aware, but both Intel's Verify, and the SSD Controller itself detect physically bad sectors. The SSD controller also remaps them. 

In any event, chkdsk showed only some unused index entries, and some free space marked as allocated.  Nothing wrong with the file system itself, and no bad sectors.

This morning I awoke to an even stranger situation, having to do with corruption.  TI ran as scheduled last night, and created and VERIFIED an incremental backup.  It sent me an email message stating the operation had completed successfully, and turned off my computer.

9    True Image    10/27/2015 10:00:06 PM    Pending operation 160 started: 'Creating partition image'.
10    True Image    10/27/2015 10:00:28 PM    Pending operation 160 started: 'Creating partition image'.
11    True Image    10/27/2015 10:01:18 PM    Writing incremental version to file: RONBP_inc_b3_s7_v1.tib
12    True Image    10/27/2015 10:02:11 PM    Pending operation 160 started: 'Creating partition image'.
13    True Image    10/27/2015 10:02:33 PM    Pending operation 160 started: 'Creating partition image'.
14    True Image    10/27/2015 10:02:33 PM    The following backups have been successfully created: "\\DISKSTATION\RonBP\backups\Chains\RONBP_inc_b3_s7_v1.tib"
15    True Image    10/27/2015 10:02:34 PM    Validate Backup Archive Location:      "\\DISKSTATION\RonBP\backups\Chains\RONBP_inc_b3_s7_v1.tib" 
16    True Image    10/27/2015 10:02:34 PM    Pending operation 3 started: 'Validate Backup Archive'.
17    True Image    10/28/2015 12:54:09 AM    Operation has succeeded.

However, upon opening the UI, it shows me that the Backup is corrupt  (Little red 'X' on the backup task, and a big "X" in the middle which, if I click on it, says Backup Corrupt).

What is going on here?

 

 

By looking at your screenshot I would suspect that when you open the application it is having issue with accessing your Network share.

With the backup selected click on the round circle with the downward looking arrow in it on the right side of the backup task name.  You should be presented with a menu from which you should have a validate option.  If you see that option choose it.  Does the validation run and complete successfully?

If when you do the above you are prompted for credentials you should have a look in Windows Credentials Manager and make sure that your network share credentials appear there.  If not add them, just might solve the issue.

I did not have the time to run a validation on this occasion, but I doubt there would be any problem (see below).  I will be doing another backup and validation this evening.

In the past, when I've received the backup corrupt message, in association with a "validation failed" email, and done what you suggested, for every single time a subsequent validation was normal, and I was NOT prompted for credentials.

This occasion differs in that the UI shows "corrupt backup", but the email shows that the operation completed successfully.

On this occasion, there is no problem accessing the backup -- if I do a Recover Files operation, the files all show up, and the few I've tested have been accessible.  And again, I am NOT prompted for credentials.

Credentials manager does show the credentials.

Other programs, likewise, do not have a problem accessing the Network share.  In particular, I store videos on the same unit, and they play without any hesitation or stutter.

This problem did not exist at all with TIH 2010, which preceded TIH 2016.  I "upgraded" to 2016 when I installed Windows 10. It is very frustrating.

I see another red dot on your account icon on the left GUI column.  Have you registered the application in the account section of the application?  Doing so might clear things up for you.

Registered?  There's no option to register in the account section.  It does state that it is activated.  I'm guessing the red dot has to due with my data going to be deleted from Acronis Cloud in 13 days (something I never bothered with -- it was a free trial when I installed this product).  Here's what that section looks like:

It appears you are correct.  Is your network share connection via USB?    Could be that if connected by USB the connection is shutting down for power savings and the delay in it coming back on when accessed is causing TI to complain.

The connection is a wired ethernet connection, cat 5E cables and GB switch and router.  The network share is a Synology DS209 with a pair of 3TB drives in RAID1.  The computer shouldn't be turning off the ethernet interface while it is being used, but maybe it is getting confused.  Your thought about the USB shutting down prompted me to disable the setting that allows the computer to shut down the ethernet connection to save power.  Perhaps that will make a difference.  Because the problem has been intermittent,  it may take a while to see if that works.