Skip to main content

Recovery Media Backup build 21400 does not validate when checked

Thread needs solution

I tried a total backup of my two drives on my laptop. Checked C and D drives...then on the menu I checked "Validate backup". The backup finished but did NOT validate the file. I had to manually validate. Hasn't worked in 2020 at all

0 Users found this helpful

I have found the same to be true.  I think that this has to do with metadata updating not being finished when validation is enabled in the backup task.  It amy also be a bug in the app.  Please submit feedback to Support.

I submitted all the pertinent materials to Acronis Support.  Received a message that they will get back to me after reviewing all the materials.  Send photos of the backup setup and process and system reports from both TI 2019 and TI 2020 (latest build)...

That's very encouraging.  Keep us posted.

Received a reply from support this morning:

 

Hello Customer, 

I'd like to update you on the status of case 04172741. To find a proper solution, 
I am involving my colleagues from the expert group to review available data and
plan further investigation together. 

Note that this may involve several subject matter experts, resulting in additional 
investigation time. 

We’ll keep you in the loop, and either one of my colleagues or I will get 
back to you once we have an update on the solution, or if new diagnostic 
data is needed. 

Thank you for your support and cooperation while we work on 
resolving this matter! 

 

Doesn't look good at the moment...

Well, there may not be an immediate solution but sounds to me like they will investigate the issue.  Not all is lost.

I am also able to recreate this issue, i.e. using rescue media to do a disk backup with validation selected only does the backup not the validation.

Doing a separate validation in the rescue media works fine!

Backup with validation enabled log.

<?xml version="1.0" encoding="UTF-8" ?>
<log build="21400" product="Acronis True Image" task_name="My Disk Drives Backup" uuid="598448BA-C39F-4ED6-9451-C62B0E95DEE2" version="24.4">
    <event code="0" id="1" level="2" message="Operation &quot;My Disk Drives Backup&quot; started." module="100" time="1569947354" />
    <event code="252" id="2" level="2" message="Backup operation succeeded." module="100" time="1569947825" />
</log>

Separate backup validation of file created by the above backup.

<?xml version="1.0" encoding="UTF-8" ?>
<log build="21400" product="Acronis True Image" task_name="Backup Validation" uuid="598448BA-C39F-4ED6-9451-C62B0E95DEE2" version="24.4">
    <event code="0" id="1" level="2" message="Operation &quot;Backup Validation&quot; started." module="100" time="1569947878" />
    <event code="1" id="2" level="2" message="Using default upnp detection algorithm." module="339" time="1569948422" />
    <event code="252" id="3" level="2" message="The archive was successfully checked." module="100" time="1569948422" />
</log> 

Steve,

Do you get the same result in Windows?  I do, if I run validation at the time of task creation it fails.

Bob, I will need to test as I don't normally include validation with any of my backup tasks - will add an update after testing..!

Bob, just tested adding validation for one of my test backup tasks using single version and it fails as shown in the log below, and also fails validation if run separately!

01/10/2019 22:51:43 :211  -----
01/10/2019 22:51:43 :211  ATI Demon started. Version: 24.4.1.21400.
01/10/2019 22:51:43 :241  Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
01/10/2019 22:51:43 :241  Operation TestSingleVersion started manually.
01/10/2019 22:51:43 :833  Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
01/10/2019 22:51:43 :834  Operation: Backup
01/10/2019 22:51:43 :834  Priority changed to Low.
01/10/2019 23:05:33 :396  Error 0x4000d: The file is corrupted.
01/10/2019 23:05:33 :396  Error 0x4000d: The file is corrupted.
01/10/2019 23:05:33 :457  Error 0x13c0005: Operation has completed with errors.

01/10/2019 23:07:37 :224  -----
01/10/2019 23:07:37 :224  ATI Demon started. Version: 24.4.1.21400.
01/10/2019 23:07:37 :295  Operation Backup validation started manually.
01/10/2019 23:07:38 :272  Priority changed to Low.
01/10/2019 23:11:07 :880  Error 0x4000d: The file is corrupted.
01/10/2019 23:11:07 :910  Error 0x4000d: The file is corrupted.
01/10/2019 23:11:07 :949  Error 0x13c0005: Operation has completed with errors.

Further update on the above validation issue.

It looks to me as if the metadata information is being corrupted when validation is appended to the backup action.

I used the Clean up versions tool to delete the remaining .tibx file even though Explorer still showed that it was physically present on the drive!

I then removed the validation option and re-run the backup task, then repeated a separate validation which succeeded!

One quirk for validation is that the progress bar jumps right across to around 90% and shows 'less than 1 minute' for the duration of the validation process!

01/10/2019 23:19:35 :028  -----
01/10/2019 23:19:35 :028  ATI Demon started. Version: 24.4.1.21400.
01/10/2019 23:19:35 :057  Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
01/10/2019 23:19:35 :058  Operation TestSingleVersion started manually.
01/10/2019 23:19:35 :564  Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
01/10/2019 23:19:35 :565  Operation: Backup
01/10/2019 23:19:35 :566  Priority changed to Low.
01/10/2019 23:19:36 :054  Can't read slices: Error 0x40011: The specified file does not exist.
01/10/2019 23:28:42 :806  Operation has succeeded.

The slice error is from using the Clean up versions tool!

01/10/2019 23:28:52 :492  -----
01/10/2019 23:28:52 :492  ATI Demon started. Version: 24.4.1.21400.
01/10/2019 23:28:52 :545  Operation Backup validation started manually.
01/10/2019 23:28:53 :425  Priority changed to Low.
01/10/2019 23:37:42 :114  Operation has succeeded.

Steve,

I have had similar results.  I found that if I do select validation in the backup task, run the task, then validation it works fine.

I think you may be on to something with the metadata corruption.  I have also thought that because I have fast machines that possibly the backup file has not quite finished its write to disk before the validation is run thus causing the corruption/failure.

I have submitted a report so will see what happens.

Received a new response from Acronis.  Here you go:

 

I would like to inform you about the current status of this ticket.

Our test lab confirmed that this is a reproducible problem in the software, 
so it was passed to the development team. The issue is now being handled by our 
developers and is expected to be fixed in one of the future versions of the program.

Unfortunately, we do not know yet when the new version with the fix will be 
launched exactly, so I would suggest you that we archive this ticket. 
It means that it will be closed temporarily, but not considered as resolved, 
and you can reopen it at any time, e.g. when a new build is available or if 
you have further questions.

Bob,

Thanks for posting the above response.  At least we know they are aware of the problem and have it on the slate for a fix.

Been over three weeks...nothing about a new update???  I am still using 2019, since I don't trust 2020. 

Bob M schrieb:

Seit über drei Wochen ... nichts über ein neues Update ??? Ich benutze noch 2019, da ich 2020 nicht vertraue. 

 I recommend you a refund. Reason; No timely information as to when Acronis developers are willing to resolve your concerns.

Downloaded and installed update to build 22150 today (11/21).  Re-created the WinPE recovery disk...and booted to it and did a backup.  Same old problem.  The backup completes, but even with Validate backup checked...I still have to validate manually.  They DID NOT fix this issue.  I no longer trust Acronis to fix anything.  Next time, different backup software. 

Even though they acknowledged the issue and said they would fix...they didn't

Fool Me Once, shame on you...

 

Bob M wrote:

Even though they acknowledged the issue and said they would fix...they didn't

To be fair, Acronis said they didn't know when the bug would be fixed.  I would not expect the fix to be in a build released 3 weeks after report of the problem.