How can I restore extra backup files?
I've been making backups in a set called BACHomeS. I have 1 full backup and 10 more incrementals. True Image is installed on the C: drive while the backup files are on an external USB hard drive. Because of problems with the Windows Creator Update (not related to True Image) I had to do total drive restoration of the C: drive twice. After the restores, I continued making incremental backups.
I assume because of the total C: drive restores, I screwed up the True Image file numbering. Twice the backup filenames get a -2 appended to them. I wouldn't care but out of 11 backup files, only 9 show up as selectable when I try to to a file restore. The backup filenames are:
03/17/2017 01:38 PM 140,178,954,240 BACHomeS_full_b1_s1_v1.tib
03/18/2017 06:51 AM 4,995,769,856 BACHomeS_inc_b1_s2_v1.tib
03/19/2017 03:25 PM 6,305,596,928 BACHomeS_inc_b1_s2_v1-2.tib
03/20/2017 10:05 AM 9,380,716,032 BACHomeS_inc_b1_s3_v1.tib
03/21/2017 12:58 PM 12,841,486,848 BACHomeS_inc_b1_s3_v1-2.tib
03/22/2017 10:20 PM 4,062,727,168 BACHomeS_inc_b1_s4_v1.tib
03/23/2017 04:41 PM 1,940,617,728 BACHomeS_inc_b1_s5_v1.tib
03/24/2017 05:53 AM 1,183,899,648 BACHomeS_inc_b1_s6_v1.tib
03/27/2017 10:26 PM 22,475,481,088 BACHomeS_inc_b1_s7_v1.tib
03/30/2017 07:38 PM 4,498,062,848 BACHomeS_inc_b1_s8_v1.tib
04/06/2017 05:15 PM 124,413,069,312 BACHomeS_inc_b1_s9_v1.tib
11 File(s) 332,276,381,696 bytes
Absolutely nothing went wrong during any of the 11 backups.
However, when I attempt to restore a file, True Image Image only lists 9 backups, not 11. I have tried removing BACHomeS from the database and re-adding in that backup set, but all I ever get is 9 backups, not 11. It's skipping each of the ones just prior to the -2 backups. See backup dates in attached image.
How can I correct True Image to show all 11 backups? Would it be safe to rename all the files to a s1 through s11 sequence and then remove/add again?
Thanks.
Anhang | Größe |
---|---|
restore.jpg | 491.32 KB |


- Anmelden, um Kommentare verfassen zu können

Very confusing, but I think I understand. I sure wish TI would have handled that better.
Now that I know I can't trust TI to build a good incremental chain under all circumstances, I'm wondering if taking an extra step after the C: restore would have avoided this mess.
If I know I am doing a total restore of C:, after the C: restore is done, remove the entire BACHomeS chain from the database and then re-add it in. TI will then have an oportunity to scan the files, see the extra file, and rebuild the database before the -2 files are ever created. That way I can then continue with the incrementals, rather than having to take full backups every time I restore C:
Would that likely work?
Thanks.
- Anmelden, um Kommentare verfassen zu können

Bruce, the other approach here would be to save a copy of the latest C:\ProgramData\Acronis\TrueImageHome\Database folder / contents and restore this back after restoring the whole C: drive, then you would be putting the database back to how it was when you created the backup just restored.
Having said the above, any further incremental after doing the restore will be significantly larger due to the volume of changes caused by doing the restore, therefore, perhaps the best approach is a different one altogether.
Do the restore of the drive, then in ATIH, take the option to 'Clone settings' for your backup task, which will create a duplicate of the task with the same name but prefixed by (1). Next, remove the original task settings and edit the duplicate task to remove the (1) prefix and point this to a new folder on your backup drive.
Doing this will leave the original files in their original folder in case you need to access them.
When you run the new, duplicate / cloned task, you wil start with a new full backup and new incremental chain taking you forward from that restore point without any confusion over old backup chains / files etc.
- Anmelden, um Kommentare verfassen zu können

I would have liked to have saved the database folder, but the Creators Update left my C: drive unbootable, twice, so there was no easy way to capture that folder, even if had known in advance to do it.
Yes, creating a clone of my lastest tasks is what I normally do every 10 incrementals. I don't trust TI to manage a long chain (or even a short one for that matter, as this experience reinforces), so cloning/creating a new backup task every 10 incrementals is how I miimize program mistakes.
- Anmelden, um Kommentare verfassen zu können