After restoring system, incremental backups don't continue from where they should
Every day at 8pm my system does an incremental image of two of my partitions. After every 6 incrementals, it does a full image, and it keeps a maximum of 3 chains.
So, as of just after 8pm yesterday, this is the set of files comprising my backup:
Both_SSDs_full_b15_s1_v1.tib
Both_SSDs_inc_b15_s2_v1.tib
Both_SSDs_inc_b15_s3_v1.tib
Both_SSDs_inc_b15_s4_v1.tib
Both_SSDs_inc_b15_s5_v1.tib
Both_SSDs_inc_b15_s6_v1.tib
Both_SSDs_inc_b15_s7_v1.tib
Both_SSDs_full_b16_s1_v1.tib
Both_SSDs_inc_b16_s2_v1.tib
Both_SSDs_inc_b16_s3_v1.tib
Both_SSDs_inc_b16_s4_v1.tib
Both_SSDs_inc_b16_s5_v1.tib
Both_SSDs_inc_b16_s6_v1.tib
Both_SSDs_inc_b16_s7_v1.tib
Both_SSDs_full_b17_s1_v1.tib
Both_SSDs_inc_b17_s2_v1.tib
Both_SSDs_inc_b17_s3_v1.tib
Both_SSDs_inc_b17_s4_v1.tib
Both_SSDs_inc_b17_s5_v1.tib
Both_SSDs_inc_b17_s6_v1.tib
So far so good.
At 9pm yesterday my system experienced a BSOD and some files got corrupted. I restored my system partition (C-drive) from the backup that had run about an hour earlier (at 8pm) and all was good again.
However, today at 8pm when the next scheduled incremental backup has run, it has not continued from where it should have. This is the file that was created today:
Both_SSDs_inc_b16_s8_v1.tib
Instead of continuing with the latest chain, b17, it has appended today's backup to an older chain, b16. Why? What is the best way to resolve without having to delete the entire backup set and lose 3 weeks worth of history?
Also, can this please be flagged for Acronis development to look into.
- Se connecter pour poster des commentaires
But Colin, I restored the very latest backup at the time, "Both_SSDs_inc_b17_s6_v1.tib". So all I did is go back 1 hour in time.
Why did True Image then think that it was appropriate to continue from a one week old chain: "Both_SSDs_inc_b16_s7_v1.tib" ? How is that not a bug?
- Se connecter pour poster des commentaires
Grindax,
For clarification,
please confirm whether you restored using the Recovery CD or from within Windows?
Also, did you restore only Drive C or did your restore all partitons on the disk?
Also confirm which version and build you are using.
Is there any chance you actually did restore the wrong backup? Can you look at some file dates and times to confirm the latest was restored.
The newest chain could be moved into a different folder if you want to continue with the existing chain. It will probably do 5 more incs before going into the next full.
You may also find that you now have extra listings of backups on your main screen.
Thank you.
- Se connecter pour poster des commentaires
Hi GroverH,
I booted from the Recovery CD (5551). I just restored the C drive. I've got the latest build installed: 6514.
I definitely restored the correct backup. My C drive went back in time to exactly the period I expected, which was 1 hour prior.
I don't have extra listings of backups in the list now. I ran some backups of the existing job manually by right-clicking on the backup. True Image created a couple more incrementals against the 1-week old chain (b16), and then it created a new full version which it called b17_s1_v1-2, probably so it didn't conflict with the existing b17 chain. At the same time, it then deleted the oldest chain, b15.
This is the fileset as it exists now, sorted in date order:
Both_SSDs_full_b16_s1_v1.tib
Both_SSDs_inc_b16_s2_v1.tib
Both_SSDs_inc_b16_s3_v1.tib
Both_SSDs_inc_b16_s4_v1.tib
Both_SSDs_inc_b16_s5_v1.tib
Both_SSDs_inc_b16_s6_v1.tib
Both_SSDs_inc_b16_s7_v1.tib
Both_SSDs_full_b17_s1_v1.tib
Both_SSDs_inc_b17_s2_v1.tib
Both_SSDs_inc_b17_s3_v1.tib
Both_SSDs_inc_b17_s4_v1.tib
Both_SSDs_inc_b17_s5_v1.tib
Both_SSDs_inc_b17_s6_v1.tib
Both_SSDs_inc_b16_s8_v1.tib
Both_SSDs_inc_b16_s9_v1.tib
Both_SSDs_full_b17_s1_v1-2.tib
Even my separate file backup job was affected too. It too was confused about the middle chain (actually it had no knowledge of it anymore), and when I chose 'Recover' so I could then try and delete the oldest chain (which it did still know about), it just gave an error and couldn't delete anything. I had to manually run the file backup job a lot of times in a row until eventually it auto-deleted the old files and got into a good state where it could manage and delete any of the chains.
So my theory is that True Image is only saving its database in the full backups. When I restored an incremental, it lost knowledge of everything that had happened since the last full backup. Even if that theory is incorrect, something similar has happened which has resulted in this situation.
- Se connecter pour poster des commentaires
I think my theory is correct and that this is a serious bug. Does anyone have a contrary thought?
- Se connecter pour poster des commentaires
bump.
This is a real problem and I'm concerned that there is no plan to fix it in future versions.
Summary for those just joining the thread:
If you restore your system specifying an incremental image within a backup set, then when your restored system comes back up it will have lost all knowledge of backups that happened since the last full backup within that backup set. So when your backup job runs again, it will continue by appending incrementals only to that last full backup, no matter how far in the past that was, and not the most recent incrementals. If you had a full backup 10 days ago and only incrementals since then, if you restore your system using today's incremental you will lose access to the last 9 days of backups within True Image because the restored True Image database will know nothing about those.
- Se connecter pour poster des commentaires