Skip to main content

"The Last Backup has failed"

Thread needs solution

After upgrading to Windows 10 Acronis 2016 won't back up when requested. Get the following: "The last backup as failed. The back up location was not found on the destination drive." What can be done? Thanks fo all help. Ran System Report and got a report that's attached. 

Attachment Size
systemreport.zip 1.43 MB
0 Users found this helpful

Marc, welcome to these user forums.

Thank you for the System Report information.

Please check that you can see D:\Entire PC (TEKASSOC).tib through Windows Explorer, as this is what your Entire PC backup task is looking for but reporting that it cannot find?

If the file is present on your drive D:\ then please also check that this is shown correctly in ATIH 2016 in the GUI for the Destination for the task.

If it is shown correctly, then I suspect that perhaps the Acronis Database information for the task may have been damaged during the Windows Upgrade and you should do the following to resolve this.

  1. Click on the (V) icon next to the Entire PC (TEKASSOC) task name and take the option to Clone the task settings.  This will create a new task with the name (1) Entire PC (TEKASSOC) (or similar). 
  2. Delete the original backup task - just the settings when clicking on Delete.
  3. Check the settings for the new cloned backup task, reselect the Destination as your D:\ drive, and rename the backup as needed.
  4. Perform a Validation of your backup task to check that it now finds your backup on the D:\ drive.
  5. If all is OK, then run the new backup task (or let it run to your schedule).

Steve,

Thanks so much for your well specified input. Unfortunately, the file "D:\Entire PC (TEKASSOC).tib' is not on the D: drive. There are many other files that start with "D:\Entire PC (TEKASSOC)_X_X_X.tib" files. Should I uninstall and start all over again?

Marc,

After the upgrade, the destination drive may no longer the same because you have a brand new OS (even though it was an upgrade), plus, you are using what looks like to be an "entire pc" backup and the drives may be reported differently after the upgrade.  Or, the attached drive is no longer D: and is now some other letter like E: or F:.  Or, you're now using a different drive for the backups than what was originally used when the backup was created.  I can't really tell which one is the culprit from the error messages - it just says that the destination drive is not found and that's why it's failing.  

You should be able to edit the existing task and navigate to the destination of choice and just pick up where you left off after that.  

Personally though, I would create a new backup task to avoid any carry over issues after the upgrade.  Instead of using the default "entire pc", hover over it and change to "disks and paritions".  Then specifically select only the disk(s) you want to backup and ensure all paritions are selected (they are if you select the entire disk box). Name the backup to something else (just make it unique so it's different than the existing backups) and put the backup files in their own folder (to keep things clean).  Then run the backup and all should be well.  You can keep the old backup files for posterity and/or delete them to free up space once you're satisifed the new backup task is working corretly

 

This is what your logs are reporting as of 7/27...

---------------

task_name=Entire PC (TEKASSOC)

The backup location was not found on the destination drive. Make sure the correct storage device is connected to the computer

Operation has completed with errors

---------------

prior to that it showed success...

task_name=Entire PC (TEKASSOC)
message=Create Backup Archive From:  To file: D:\Entire PC (TEKASSOC).tib Compression: Normal Exclude: Files matching mask Match criterion: blah blah blah (not really, but didn't want to post them all)
message=The following backups have been successfully created: D:\Entire PC (TEKASSOC)_full_b5_s1_v1.tib
message=Operation has succeeded

 

I was having the 'last backup has failed' problem and did a full uninstall and reinstall and the problem has gone away.