Skip to main content

Cannot find version 3

Thread needs solution

During my most recent scheduled backup, the system issued the error "Cannot find version 3".  I believe this was triggered when I lost the network connection to the drive where the backups are placed during the last scheduled backup.  This may have left one of the .TIB files in an inconsistent state.  I have not moved nor deleted any files in the backup chain.  Is there anything that can be done to recover from this error?

Currently, I am unable to complete any additional incremental saves nor can I now recover any files from this backup.  I have seen this type of error many times in the past, and the only solution I have found is to destroy the backup and recreate a new one in a new location.  Seems like there must be a better way.

Is there a way to reconstruct the backup chain (full plus the 2 incrementals), throw away version 3 and then continue with a new version 3?  Don't know if it helps, but here's the listing of all the files on the backup folder:

Full_b1_s1_v1.tib
Full_b1_s1_v2.tib
Inc_b1_s2_v1.tib
Inc_b1_s2_v1-2.tib
Inc_b1_s3_v1.tib
Inc_b1_s3_v2.tib

I appreciate any feedback/suggestions on how to best proceed.

steveg

0 Users found this helpful

Full_b1_s1_v1.tib
Full_b1_s1_v2.tib
Inc_b1_s2_v1.tib
Inc_b1_s2_v1-2.tib
Inc_b1_s3_v1.tib
Inc_b1_s3_v2.tib

You're correct that one of the files became corrupted when you lost network connectivity during the backup - as referenced by the -2 which is a retry of the existing (corrupted)Inc_b1_s2_v1.tib because the previous file did not close properly and Acronis attempted to use the same name when the network connection was restored.  

This is a problem in the incremental scheme as each incremental relies on all the ones before it and if an earlier one in the chain is corrupted this way, it basically makes all the rest unusable. 

To resolve you could try:

1) Validate the backup and see if it can do so.  if it validates, you might be in luck.  

2) Try deleting (move it somewhere else first as a test) the original Inc_b1_s2_v1.tib file and then rename Inc_b1_s2_v1-2.tib to the original name of Inc_b1_s2_v1.tib and try to validate and see if that is successful.

3) If 1 or 2 don't help, manually delete all of the incrementals, but leave the full.  Then validate the backup.  When it asks you to locate the missing files, just ignore them until the prompts go away.  Run a new backup and see if it creates a new incremental.  If it does, try to validate the backup again to make sure it can.

If none of these work, you still have a good full backup and can hold onto it, but time to start a new backup task again.

I generally have 2 different backup jobs, one with daily incremetnals (1 full + 6 incrementals >>> daily for 1 week of backups) and a second with differentials run every other day (1 full + 3 diffs weekly) and the fulls are run at offset days to provide maximum options for recovery points. Of course, this eats up more space too, so you could space your second differential backup less frequently (once every 3 or 4 days and set it so that the full is only once a month).  Any secondary backup scheme is better than none at all.  If you can create one to one disk and the other to another disk for redundancy and distribution, even better. In most cases where data is important, you should try to follow the 3-2-1 backup method.