Direkt zum Inhalt

Continue incremental backups after restore

Thread needs solution

I have scheduled backup of my system drive every week. This does some incremental backups and then a full backup. Now I reached up to Backup ...inc_b6_s15_v1.tib when I had to use this (last) backup for a recovery. 

When, after recovery, I run this Backup again, it creates an image file ...inc_b6_s16_v1.tib, and this seems to have a reasonable size, but, when it comes to validation, it complains that it can't find version 15. It offers to search for the file, but when I click the button then nothing happens (I would have expected a file dialog). The same problem happens when I try to mount this new image.  All is perfect with the previous images: I can validate and mount  ...inc_b6_s15_v1.tib with no problems, but the new one doesn't fit in, though it was no problem to create it in the first place.

I also tried to hide the file ...inc_b6_s15_v1.tib (by renaming the extension) because, actually, for the current state of TI this image should not exist (because it reflects a state of the system where this image did not yet exist). But the problem was the same: It creates a (new) image ...inc_b6_s15_v1.tib and, during validation, complains about a missing file ...inc_b6_s14_v1.tib. 

From what I see now I only have the possibility to clone the settings and build a new backup. 

Is this an error or am I doing something wrong?

I think it would be great I one could see which image files are comprised in a backup, according to TI's internal perception of the reality. And, if one is missing, then it should be easy to add this file in the backup chain. Maybe there is such a tool somewhere?

 

Any help is appreciated,

Thorsten

(Using TI 2015 for PC, Build 6525)

0 Users found this helpful

Thorsten,

There are some known issues that arise when you restore a backup on to your computer and have the backup archive file that was used for that restore still present to be found by ATIH.

Some of these issues arise from the restoration of the Acronis Database file contents that hold information on backup task history and version details, so immediately the database is out of sync with the backups being found.

The best way to reconcile these differences is to clone your current backup task settings and then remove the original task settings before running the new cloned backup task so that the database information gets cleaned up.

I would also recommend updating your ATIH 2015 to the latest build 6613 version (unless your signature information is incorrect about using 6525).