"Cannot find version 1" error -- And NO reason for that
I need to recover my C:\ drive from my last backup. I am getting what I find on this forum to be the much dreaded "Cannot find version 1" error. When I try to validate the backup I get the same error.
In my case there I see no reason for the error. I am using an external drive plugged into the same USB port I made the backup from. I did a full manual backup, with scheduling turned off (and it is still off) - so "differential" backup or other options like that are not a factor.
I am using ATI 2014 Premium. I'm totally stuck on this -- hope someone can help. Nothing in other threads is helpful.
OK --- here is the problem. I got ATI to burp somehow (not sure how) and provide some additional information about what triggers the error.
My file name is: 24Mar17--FULL_full_b61_s1_v1.tib (The first "full" was part of my name for the backup.)
ATI is looking for: 25May14_full_b15_s1_v1.tib
Note that ATI is looking for a backup that I made almost three years ago, as apparently part of this recovery. What is going on here?
I have only two .tib files on the external drive; both from this March, and they are the only backups on my list (I have removed all the others).
Larry, the reason for the error message about missing version files is simply caused by deleting backup files outside of using Acronis automatic cleanup rules, by deleting files using Windows Explorer.
Acronis keeps track of all backup files created in its internal Database files, so when you delete them in Explorer, these database files become out of sync with the actual status of files.
You need to run a Validation for your backup task, this will present a pop-up message for each missing backup file, so there may we a lot if it is looking for Backup version 15 (B15) when your current backup version is 61 (b61). Take the Ignore option for each missing file until the validation finishes.
Thanks, Steve! I never would have guessed that it would take multiple "ignores" to clear the problem. After taking care of that, I now have one backup validated and the other in the process of being validated.
This is a very finicky program, and far from foolproof. Much earlier versions of ATI really saved me a few times, and didn't seem to have the pitfalls like this one that have cropped up over the last several years.
Larry, glad the validation has been working for you. If you use the automatic cleanup rules for your backup task, this should take care of managing the number of backups being kept and avoid having to manually delete them.
How much time does automatic cleanup take? Both the delete and validate features take many hours (for my 1+ T .tib files), which means the backup process won't be done overnight.
I am puzzled why ATI works this way. Does it maintain a complete index on my hard drive to the .tib file on my external drive? And if so, why does it take so long for ATI to delete an entry instead of just deleting the index for that file? Maybe you won't know the anwer to that. But it seems that for saving time in the long-run I am better off manually deleting and then doing a validate for the rare occurances when I need to do a recovery. Too bad that the pop-up with the "ignore" button gives no indication that the button may have to be pressed times to clear ATI's backup records to allow a validation to proceed. The program needs some fool-proof features like that.
Thanks for all your help.
Larry, if you have setup automatic cleanup correctly, then it takes virtually no extra time to work, just the time needed to delete any qualifying complete version chain files from your backup drive and update the Acronis Database information for the backup task - this shows in the log file for the task as 'Consolidation'.
Acronis maintains this information in the Database files for exactly this purpose.
My preferred use of automatic cleanup is "Store no more than X recent version chains" which means that if X=2 for example, then when the 3rd Full backup has completed successfully, the 1st version chain will be deleted to maintain just the 2 existing versions, i.e. version 2 and the new version 3 chain.
A version chain = a Full backup plus all Incremental / Differential backups using the same backup sequence number, i.e. sequence 1 has _b1_ in the file name, sequence 2 has _b2_ etc.
Russell, sorry but this forum topic has nothing whatsoever in common with your promotion of the long path tool software which is totally irrelevant in this context. Acronis True Image can handle long paths in Windows without the need for such a tool.
The "internal DB files" theory may have worked for Larry but it is not the answer. I have two identical machines running identical software, including Acronis, doing local backups to a high-volume device. Suddenly, one Acronis instance started failing with the "cannot find version nn" error. It also started failing backups silently, which is unacceptable. Creating a new, clean backup folder which succeeds and removing (from within Acronis) the other backups still gives the error.
David, first welcome to these User Forums.
This forum topic is nearly 2 years old and this forum is for older Acronis products (2014 and earlier).
If you are using a later version of Acronis True Image, then I would recommend opening a new forum topic in the relevant forum for that product, using the Create New Topic button, then provide more information about exactly what you are seeing, what scenario this issue is happening in, i.e. Windows OS version, backup configuration details, storage medium, how connected etc?