Skip to main content

Recover Files - Cannot find version

Thread needs solution

Build 6613:

I have been using incremental backup for years and recently needed to recover an old file.  When I tried Recover Files it said "cannot find version 6".  If I ignore this ittried to find version 5, 4, 3, 2, and 1 but all fail.  If I go to the backup directory I see sets of backup files starting with a full backup and then 5 incremental backups before going to the next full backup.  The backup files seem to be there but Recover can't find them.  How can I get access to the files?  I think I deleted some old backups in a way that corrupted the lookup process.  I have three full backup chains that are stored but can't seem to access them.  I can't believe I'm the first person to have this problem but I couldn't find any similar cases in the KB.

0 Users found this helpful

Larry, I would recommend trying to recover your old file by booting from the ATIH 2015 Rescue Media as this works completely outside of Windows using a Linux boot environment.  If this works for you, then it is likely that the Acronis Database information on your system has been corrupted when you deleted the old backups outside of using ATIH, i.e. via Windows Explorer.

The other option is to attempt to Validate your backup chains via the ATIH GUI and then take the option to Ignore all missing versions that are reported by the validation task.

I am also getting the "Cannot find version 1" message even though the all file(s) in the incremental cycle are there.  The backup is scheduled to run at night, but will wait for "User response" until the morning.  There is no Ignore option, but if I browse to the Version 1 I think it is looking for (ususally 2 or 3 times) the backup will eventually finish and validate and I get the email confirmation that the backup completed succesfully.   The target drive is always available and has been removed from any defrag process so there should be no changes to the tib files.

I did initally have the backup size limit set and did change that and the number of incremental versions to keep.  I guess my question is why does the ATI backup database not "heal" itself if it goes through a valid backup and verification cycle.  It has not done this for the last 5 incrementals; the limit is currently 6.  I am hoping that when it reaches 6 and creates the next Full backup, that things will get back on track.

If this does not happen, I will report back and then do the standard "delete, recreate, and change the target folder".  One of the things that bothers me is that when you get the message about not finding v1, it does not include the entire path of the file it is looking for.  Back in the (very) old days when I wrote programs, I tried very hard to display all the parameters that generated the error so that there would be no confussion as to what went wrong.  Having to peruse cryptic log files to understand what is going wrong is poor programming (IMHO).

I do want to personally thank all the Acronis MVP Volunteers; I have gained a better understanding of the software reading your responses.  I also see that you bear the brunt of the frustrations of the users as if you work for Acronis, but you handle it with grace and empathy.

Acronis True Image 2016 Build 6571

Oops; thought I was on the Backup thread.  My previous post should be moved to one of them.

Weimsguy - see if applying this small fix, rebooting and validating resovles your issue.  There's really no forum moderator so your post is likely to stay here :) 

https://forum.acronis.com/forum/117232#comment-359062

 

Bobbo_3C0X1 - I'll give this a try if and when the situation comes back.  For now, I just kept doing my "Browse" to the V1 ATI could not (or would not) find until the next Full backup.  When the next Full backup ran, it completed successfully without any messages.  I will not say it is repaired until the next Incremental backups also complete without any errors.  Thank you for your reply; I'll keep it in my tool box.

Since completing the full backup cycle by manually browsing to the V1 file that ATI was not able to find, the backup process is completing successfully without intervention and the next full backup cycle has started.  The database seems to be cleared of the problems that were causing the "cannot find V1" error.

That's good new.  Hope it stays that way for you now :)