"Couldn't Find Version 4. It may have been deleted or moved"
I just added a drive to the system, and have True Image 2018 installed on an Intel Win 10 Pro machine. I have three separate backups, and the first successfully moved to a new drive. Unfortunately, the second comes up with the above error. Retry does nothing, and cancel is the only other option. The disconcerting part is that I never manipulate these files manually. The same error is produced when "validate" is run.
I did the "Change Destination" command, and that seemed to work, but only affects the latest backup? At this point, I'm rather concerned about this. Should I just copy the rest via explorer?


- Log in to post comments

Hi Steve,
I attempted the move via the menu item shown in your graphic. I have never manipulated the archive files outside of the app. I did use the change destination successfully (I think) to the new drive, where a backup was created.
I would assume that since it's "number 4" it must be a delta fille? I wonder if the new backup is valid, or even the entire archive.
- Log in to post comments

Joseph, the key difference between using Change Destination and using the Move option is described in the user guide.
Move - click to move all the backup files to another location. The subsequent backup versions will be saved to the new location.
If you change the backup destination by editing the backup settings, only new backup versions will be saved to the new location. The earlier backup versions will remain in the old location.
- Log in to post comments

I did indeed use the move option. The log reflects that the archive was moved. This morning, I noticed the same error dialog appeared. I only now realized that backups are failing as a result of this. I tried browsing for the file, but do not see a "version 4". Ignore does not work, only cancel, which apparently stops backup.
How can this be corrected? Do I need to redo the backup? If so, I guess the older versions are just lost?
- Log in to post comments

Joseph, how many files are involved here for this backup task and are they all stored in the same location on your backup drive?
What type of backup is involved for this error?
Is it an Incremental or Differential backup scheme?
If Incremental or Differential are all the files for each backup chain correct & present?
Example: do you have all the files sharing the same backup sequence identifier,
_b1_s1_v1 then b1 s2, s3, s4 etc with no missing files or gaps in the sequence?
Version 4 may not refer directly to one of the above numbers!
- Log in to post comments

I've attached an image of the files in the archive folder.
- Log in to post comments

Joseph, I can see several issues from your list of files, assuming that this is a complete list?
You have orphan incremental files for the _b16_ backup chain (s13 & s14) with no full_b16 file.
You have gaps in the list of full backup files, i.e. _full_b1 for the initial full backup being retained, then this is followed by _full_b12, b15, then b20, so you are missing b13, b14, b16, b17, b18, b19 full versions.
These issues will cause 'Cannot find version X' errors because the missing files are most probably still referenced in the internal Acronis database.
You should delete the orphan b16 incremental files unless you have all the other files for that version chain.
You should perform a validation of the task to see if it still gives errors for missing files.
- Log in to post comments

Well, that did get rid of the "version 4" error message. Verify completes silently. Unfortunately, backup fails with without a meaningful error message. This backup was setup as incremental, create new image only every X days, and keep archive under 1TB.
Yes, the image includes every file in the folder. And again, I have never manipulated these outside of the application. This experienced really doesn't do a lot for my confidence in TI.
Please note that I do appreciate your time and effort.
- Log in to post comments

Joseph, the next step is to look at the log created by the backup task that fails, for which you should use the MVP Log Viewer tool to access and format the log. The log should give us more information about why the task is failing. Link to the tool below if you don't already have it.
- Log in to post comments

Joseph wrote in the MVP Log Viewer topic:
Here is the most recent log entry:
7/18/2019 8:17:35 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
7/18/2019 8:17:35 PM: Operation My folders started by schedule.
7/18/2019 8:17:39 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
7/18/2019 8:17:39 PM: Operation: Backup
7/18/2019 8:17:39 PM: Priority changed to Low.
7/18/2019 8:17:39 PM: Error 0xb03e9
7/18/2019 8:17:39 PM: Error 0x13c0005: Operation has completed with errors.Start: 7/18/2019 8:17:35 PM
Stop: 7/18/2019 8:17:39 PM
Total Time: 00:00:04
Joseph, you will need to switch the Log View: from Short (above) to Regular which will then give more details of what the error code shown means.
- Log in to post comments

And here is that result:
7/18/2019 8:17:35 PM: -06:00 33484 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
7/18/2019 8:17:35 PM: -06:00 33484 I00640002: Operation My folders started by schedule.
7/18/2019 8:17:39 PM: -06:00 33484 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
7/18/2019 8:17:39 PM: -06:00 33484 I013C0000: Operation: Backup
7/18/2019 8:17:39 PM: -06:00 33484 I0064000B: Priority changed to Low.
7/18/2019 8:17:39 PM: -06:00 33484 E000B03E9: Error 0xb03e9
| trace level: error
| line: 0x7ace056009c34d63
| file: c:\bs_hudson\workspace\723\products\imager\archive\impl\archive_data_stream_tib_file_impl.cpp:511
| function: TrueImage::Archive::TibFileDataStream::CreateAppender
| line: 0x7ace056009c34d63, c:\bs_hudson\workspace\723\products\imager\archive\impl\archive_data_stream_tib_file_impl.cpp:511, TrueImage::Archive::TibFileDataStream::CreateAppender
| $module: ti_demon_vs_15470
7/18/2019 8:17:39 PM: -06:00 33484 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bce5f
| file: c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617
| function: main
| line: 0x9f2c53c72e8bce5f, c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617, main
| $module: ti_demon_vs_15470
Start: 7/18/2019 8:17:35 PM
Stop: 7/18/2019 8:17:39 PM
Total Time: 00:00:04
- Log in to post comments

Joseph, thanks for the extra log information which didn't offer any clear clues that mean anything to me. The only real clue here is that the backup fails almost immediately (within 4 seconds of starting), so is having an issue with either finding the source or destination files!
I would recommend using the option to 'Clone settings' for this backup task which will create a duplicate task with the same name prefixed by (1), i.e. (1) My folders.
If you leave the cloned task name as given, then you could run this to start a new backup chain to the same destination with files named (1) My folder_full_b1_s1_v1.tib etc.
If you want to use the original task name then you should use a different destination folder and then remove the task settings for the original My folders task (click on the Delete option, and elect to only remove the settings, not the files.
Note: you should not try to run the cloned task to the same destination folder with files in that folder already using the same name as the cloned task - this will give you new files using _v1-2.tib names in that folder.
- Log in to post comments

Apologies for the long delay. Very busy week. I very much appreciate your time. I did clone the task to a new target, and hopefully it will backup successfully. Unfortunately, I no longer have paid support, so I guess I'm just going to give up on this. Frankly, I don't have much confidence in TI at this point, and am looking at other solutions.
Thank you again for your efforts.
- Log in to post comments