Skip to main content

Upgrade Failure

Thread needs solution

I would not recommend doing an upgrade from 2019 to 2020.

1) Upgrade hung and I had to  close the window. Launched 2020 but it wasn't working properly. Ran upgrade again and it succeeded.

2)Current backup was a .tib file. I wanted new .tibx file. Deleted and created a new backup. Why even offer an upgrade if the backup needs to be recreated?

3)Backup succeeded but when I selected the recovery tab. No backups were listed.

4) Active Protection wouldn't load until I ran the second 2020 installation. It still wasn't working properly. I was able to delete backups without notifications.

5)Several options on the backup pull down were missing. Including backup location.

I uninstalled 2020. Ran CleanupTool. Installed 2020. Everything seems to be functioning normally.

0 Users found this helpful

2)Current backup was a .tib file. I wanted new .tibx file. Deleted and created a new backup. Why even offer an upgrade if the backup needs to be recreated?

ATI 2020 will run backup tasks created with earlier versions of ATI, so there is no need to create a new backup task unless you wish to take advantage of one of the features introduced in ATI 2020.

There have been several reports of problems when upgrading to 2020, I had issues when doing a new installation after uninstalling the second beta of 2020. There have been reported problems with in-place upgrades but I cannot say if they are more prevalent than with ATI 2019.

Ian

To fix your issues:

- close ATI,

- stop all Acronis Services using Services.msc

- kill all Acroniss processes using Task manager

- delete all the files in the Database folder in c:\programdata\Acronis\TrueimageHome (hidden folder)

- restart ATI

- run the backup manually. The commands should reappear in the backup menu, and the recovery tab should work.

Makes sense. A clean install is always a more thorough approach. When you want to preserve backup scripts (so that you don't have to add backup and reconfigure upon reinstall), however, the manual cleaning of the database should be enough to solve this type of problem.

In your case, it is a moot point, since you want to switch to tibx format and that means you need to create new backup tasks anyway.