Skip to main content

ATI 2015 looking for version x

Thread needs solution

I have been using ATI2015 for a year or more now, and recently been experiencing a problem with ATI telling me that it cannot find 'Version (X)' and asking me to retry, cancel or browse.   The only option that gets me past the dialog is 'cancel'

This does not happen when I do full backups, but is happening consistently when I do inc backups and seems to happen shortly after the backup begins validating (validate option is set).

I started noticing this problem shortly after I did a backup that ran out of space on a drive during the backup  and, after clearing space, I told ATI to continue.  It continued by making a second version.

Now all my inc backups, even backups with a completely different name on a completely different hard drive, have this missing version problem during validation, even though they only have one version.

What could be causing this?

0 Users found this helpful

Joe, the 'cannot find version x' messages are caused because you have deleted backup files from your backup drive manually instead of using the automatic cleanup rules within the backup task to manage these.

Acronis records information about the backup files created by your task in its own Database files and when you manually delete files via Explorer, the information in the database becomes out of sync with the actual status of the files stored on your drive.

To resolve this situation, you should run a manual Validation for the backup task, then take the Ignore option for each missing file that is reported.

The alternative method is to use the 'Clone settings' option for your backup task which will duplicate your task settings by prefixing the task name with (1) - once you have done this, then delete the settings for the original task and you can do what you like with the backup files.

You can then rename the cloned task to remove the (1) prefix, but edit the destination to point this to a new folder on your backup drive to start a fresh new set of backups in that new folder.

But I haven't done that.   I have manually deleted files from some of the backup drives, but I have always deleted entire backup chains, never parts of a chain.

As proof of that, I have been able to validate the backups by doing a manual validation both in ATI and in the WinPE version.  It is only the validation that is initiated by the backup settings that has this problem.

I think the problem might stem from the fact that I use three different swap-able drives that map to the same drive letter on my machine.    I fear that the back up that ran out of space has made ATI think that drives assignned to that letter will always have a second version, but that is just speculation.

Joe A wrote:

But I haven't done that.   I have manually deleted files from some of the backup drives, but I have always deleted entire backup chains, never parts of a chain.

As proof of that, I have been able to validate the backups by doing a manual validation both in ATI and in the WinPE version.  It is only the validation that is initiated by the backup settings that has this problem.

I think the problem might stem from the fact that I use three different swap-able drives that map to the same drive letter on my machine.    I fear that the back up that ran out of space has made ATI think that drives assignned to that letter will always have a second version, but that is just speculation.

Joe, sorry but any deletions, whether this be of individual files or whole version chains, when done outside of the autotmatic cleanup rules results in an imbalance between the information held in the Acronis database files and the status of actual files remaining.

You will further complicate the issue here by using three different swap-able drives despite mapping these to the same drive letter.  The reason for this is that each drive announces an unique identifier (UUID) that is recorded in the database files along with the drive letter details, so each change then produces a mismatch of UUID.

ATIH is simply not designed to work with multiple different backup drives for a single backup task.  If you want to use 3 different drives, then a) you should have 3 tasks, one per drive and b) pre-assign an unused unique drive letter for each different drive, i.e. take letters from further down the alphabet such as S: T: U: that won't get assigned to any other USB drives or memory sticks.

I do have three swabable drives, but they do not share a task.   Each has its own backup task and unique.    Everything worked fine until very recently although I was able to do an inc backup last night without the version error.

Joe, it is best where possible for the different drives to have unique drive letters to avoid any confusion.