Skip to main content

"Error while checking the metadata integrity of points in time in the archive"

Thread needs solution
Beginner
Posts: 2
Comments: 0

I upgraded from the Acronis 2016 to Acronis 2019 about a month ago and everything has been working fine until recently when I started getting this error.

I tried deleting all backups with the 'Clean Tool', then ran the backup again. Same error.

I even uninstalled, downloaded and re-installed ATI 2019 Build 14690 . Still getting same error.

I opened a ticket with support but haven't yet received a reply.

To me, looking at the log file, it seems like an issue with the 'validation' part of the backup. ?

It looks like the back up is being created 'successfully'.

It's the next operation, "validate backup archive" that gives the error.

I am backing up to a local internal hard drive on my computer.

Log files and screen shot attached

0 Users found this helpful
Legend
Posts: 113
Comments: 31105

Ken, welcome to these public User Forums.

The log files do show that the backup is being created successfully but that the error message is being given when performing a validation immediately afterwards.

Please can you try performing a manual validation for one of the backups by using the option for this in the drop-down menu for the backup task (see the v to the right of the task name in the GUI) and see if this gets the same error or not?

I would recommend doing a CHKDSK F: /F for your backup drive as a precaution against any file system issues on that drive.  When a backup image file (.tib) is created, ATI writes regular checksum values throughout the file, then during a validation it recalculates these checksum values from the file data.  This PITS error is suggesting that the checksum calculation is not matching the value expected, thus potentially an issue either during data transfer to the backup drive or in writing to the drive.  If F: is an external drive, check the cable connections too.

Forum Hero
Posts: 90
Comments: 7818

Welche Hardware wird verwendet?

Ich habe dieses Problem mit einem Ryzen R7 2700X und Asus CH6 mit X370 Chipsatz und 4x 8GB GSkill TridentZ Ram.

Bei mir liegt es an nicht stabilen Rameinstellungen (Spannung, Frequenz, Timings).

Nach einem Kaltstart sind bei mir am nächsten Tag, die am Vortag funktionierenden Einstellungen meist nicht mehr stabil (nach spätestens 10 Minuten Prime95 würde ein "Worker" aussteigen).

-------------------------

Which hardware is used?

I have this problem with a Ryzen R7 2700X and Asus CH6 with X370 chipset and 4x 8GB GSkill TridentZ Ram.

For me it is not stable Ram settings (voltage, frequency, timing).

After a cold start the next day, the settings that worked the day before are usually not stable anymore (after 10 minutes Prime95 a "worker" would get out).