errors in my backup list when upgrading from TrueImage 2016 to 2017
Been one of those weeks...
I have been using Acronis 2016 and have 3 validated backups on an external disk. Two from early last year, the most recent from 05/2017.
I had a Windows10 crash a few days ago and successfully restored my backup from 05/2017...all good.
I decided it time to upgrade to TrueImage 2017 and did so...installing it yesterday.
Upon launching it, for the first time, I see that only one of my 3 backups has been validated...and the most important backup, 05/2017 has a big RED X and states..."last backup failed" (even though I did not initiate a backup). And worse...I do not have options to initiate a restore or use the file. As a critical backup, I'm turning here for your help.
I looked at the file dates and volume (on my x-drive) and it looks like it has not been written over.
My concern is if I need to run a new Restore, I will not be able to use this backup, which is my most stable and recent.
Can anyone please help and tell me what I need to do to make this backup usable again. I expected old Trueimage backup file to be usable with a newer version.
Thanks, John


- Log in to post comments
In reply to John, welcome to these User… by truwrikodrorow…

Hi Steve,
Thanks for the quick reply. I follow your logic that you outline in second paragraph, although I'm unclear about what a "backup task" is or where to find it??
I was able to do a validation on the older backups (2016 dates), but could not validate the 05/2017 since it had a BIG RED X in it, which only lets me rename it or delete it?
I actually had used the bootable CD when doing the 05/2017 restore a few days ago. Where is the ATI database folder info located? I'll try and validate the 05/21017 file from the boot menu, rather than within ATI / Windows dashboard, if that will work. And as you mentioned, if I do have to restore from that file, I will do it from boot media.
Just so I can sleep tonight...I'm doing a new full backup of my main drive (using ATI 2017)...so I have a backup of the backup.
Any other thoughts? Thanks again
John
- Log in to post comments

John, a backup task is simply the configuration that is used to define what you are going to backup (the Source), where you are backing up to (the Destination), and the options to be used, i.e. incremental etc. These are shown in the main ATIH 2017 (2016 etc) GUI and each will show the name that you have given to the task, and in the main panel will show you a quick summary of the Source & Destination choices, so essentially where you are probably seeing the big red X in the middle?
Next to the task name, you should see a carat symbol v which if you click on this will reveal a task menu that offers further options, including Validation etc.
The ATI Database information is held in MySQL files in C:\ProgramData\Acronis\TrueImageHome\Database but you are advised not to attempt to modify this - these files are also locked when any Acronis Services & Programs are active.
Another option you could try is 'Clone settings' if you see that offered, this will create a duplicate task with the same name but prefixed by (1) that you can then modify.
The last option is to use the Delete option but take the further option to only Remove the settings, not to delete entirely, this will remove the failed task so that you could then add your backup image file back again using the 'Add existing backup' option. You will still need to reconfigure the added back task.
- Log in to post comments

Hi Steve,
I did the last option of deleting the 05/2107 backup from the list, then locating and loading it back. I'm doing a validation right now and it looks good.
Thanks again for your prompt and expert advise. I hope Acronis acknowledges your efforts.
Have a great weekend...John
- Log in to post comments

John, glad to be able to help, thanks for the update.
- Log in to post comments

Once you have completed the validation I would check that all the settings for the backup task are as intended. Since Acronis 2016 the backup parameters are not stored in the *.tib file, merely in the data base. I have had instances where the parameters are incorrect (this was in a case where the data base was corrupted and had to be rebuilt). I foud out 6 months later that one task was backing up the wrong partition.
Ian
- Log in to post comments

Thanks Ian,
I'll double-check and make sure I'm ready for a "new" disaster ;-)
John
- Log in to post comments