Skip to main content

Problem with Validation of copied .tip TI2014

Thread needs solution

My differential backups are created on drive e: (internal).
From time to time i save them to external drive g:

Just noticed the following problem:
If i click (right) on the copied backup on drive g: to get it validated, then TI2014 opens and shows the scheduled backup on drive e: as being validated, including the progress bar.
Meanwhile ProcMon shows that reading is done from drive g: as requested.

Do I need to worry?

Best regards,
Rudi

0 Users found this helpful

ATI is trying to reconcile the archive name with its internal database. This is confusing, probably not right, but innocuous. I would refrain from copying backups that are not full backups. For full backups, you could rename them and then validate them using the right click contextual menu. Validating a renamed file will make it show up in you backup list in ATI

Thanks for your quick reply.

I just noticed that TI2014 even mixes up between backups of different names:

If I request validation of backup x on drive g: then it ignores this order and thinks it might be more funny to validate backup y on drive h:

Totally unusable for validation of different backups.
Totally unacceptable for a program designed to ensure data integrity.
TI2014 even corrupts its own data, so how can i trust that it saves mine?

Best regards,
Rudi

A native problem with ATI is its internal database, where ATI tries to keep track of which backup is where. IF users move or copy backup files manually, ATI gets confused, or, worse, the user loses track of which file/slice is part of which backup.
The benefit of the internal database is that, in theory, you can, for example, save a full backup on a disk, and then store incremental backups of the same chain somewhere else. Not sure there is a lot of value in that benefit, and there are many issues with the internal database approach as you can see.
In your case, you could search for the archives.xml in C:\programdata\Acronis\TrueImage\Database. Rename the file archives.OLD and relaunch ATI.

Best practice is to save one backup task in a specific folder. As I was saying above, copy manually only full backups, unless you are absolutely sure of what you are doing (copy only coherent chains).