Skip to main content

"Last Backups" are not recognized and can not be restored

Thread needs solution

Hello everyone,

I've got an annoying problem/error which make me doubt the level of backup security that Acronis TI 2017 is able to provide.

I created a backup task for each of my partitions. Everything is backuped once a week on two external harddrives. When the backup has been made, the header "Letztes Backup" (last backup) shows the date and time stamp of the backup just made.

But when I start the program again after shutting it down the header just shows "..." and there is no possibility to open or recover the backup files. I already erased the backups and started from scratch, but the behaviour stays the same.

Most irritating is the fact, that not all of the backups are inflicted by this error, but "only" five out of seven.

Has anyone viewed the same problem and is there maybe a solution for it? At the moment I am not quite sure if it is save to relate on TI 2017 for saving my data against hard drive crashes or something like that …

Kind regards

Michael

0 Users found this helpful

Michael, welcome to these user forums.

I am not aware of any specific problem with ATIH 2017 that would give the symptoms you are describing in losing the Last Backup date.

There are several potential causes that might give this type of problem.

  1. If you are using multiple external backup drives with the same backup task - this is not supported by the ATIH product apart from when you use the option to make a Backup Reserve Copy in the Advanced options tab.  Using multiple backups drives will cause the Acronis Database to be confused because the application records to unique drive identifier (UUID) for the drive associated with the backup task in the Database, then a different UUID is presented when a different drive is used.
  2. The Acronis Database files have become confused / corrupted for a different unknown reason.
  3. There is a problem with the Acronis application installation.

If you are using one external drive per backup task and not mixing these, then 1. above should not apply.

If the database files are causing the problem, then you can rename or delete the C:\ProgramData\Acronis\TrueImageHome\Database folder to force ATIH to rebuild these database files.  All Acronis Services and Processes need to be stopped/ended in order to rename or delete the database folder.

If there is a problem with the ATIH application, then doing a Repair install - i.e. reinstalling the latest build version over the top of the existing application should resolve that - all installs should be performed as an administrator to ensure correct permissions are given. 

Hello Steve and thank you for your answer!

The first of the causes can be denied. Each backup task is adressed to one single drive. I'm having problems to end/stop all of the services because they keep restarting themselves. Maybe I need to start windows in secured mode.

I'll now try to install the latest build.

If any of this methods does the trick I will let you know.

Thank again

Michael

Michael, when trying to rename / delete the Database folder, stop the Acronis Services first - type Services.MSC at the run prompt then stop each running Service, then use Windows Task Manager to end any Acronis programs.  If you stop the programs first then the Services relaunch them.

Okay, I was able to perform steps for causes 2 and 3 but none of them did the trick.

Deleting the database folder seems to cause that all of my backups are now unrecognized, not only 5 out of 7.

Thank you, Steve, for the advice so far!

Michael, the database folder holds all the history information but this will be repopulated when you run your backup tasks again, and the last run date should be picked up from the file date.  You can also run a Validation for the backup tasks to reconcile the database if you prefer to do that rather than run the backup task itself.

Steve, it won't let me validate the files because the backup behaves as if they are non-existing. I only get the possibility to rename the backup, clone the setup or delete it.

I will try to run one of the smaller backups again to look after your suggestion.

Okay, maybe cause no. 2 was the one that caused the false behaviour. I just did another backup, closed the program and restarted it. The date and time of the backup was still there.

Now I'll do the same with the other backup files and look after a reboot if the data is still present.

Thank you Steve!