Acronis backup failure after Win10 upgrade
I upgraded this weekend from Win 8.1 to Win 10.
Now, my backups are failing with the following error:
6 True Image 7/27/2016 3:00:04 AM The backup location was not found on the destination drive. Make sure the correct storage device is connected to the computer.
7 True Image 7/27/2016 3:00:04 AM Operation has completed with errors.
The destination is the same that I have been using for over a year. The destination opens fine in Windows File Explorer.
Why is this happening and what is the solution?
You can see in the image attached that the drive letter is indeed "V".
Joe, sorry, missed the lower part of your screen shot when I zoomed in on the top part to see the drive letter shown in the Acronis GUI image.
Have you tried doing a Validate against the two backup tasks that have the crosses shown (E & I)?
If the Validate still gives this error, then try moving the mouse over the Destination and clicking on Change Destination and try to re-select the same drive path again.
OK, I clicked on the destination and changed it back to what it had always been. Then tried to do a manual start, which is worked.
If this has something to do with the Win10 upgrade (Win10 Pro), then you might get a lot more of these problems in the next few days as everyone rushes to beat the 7/29 free upgrade deadline.
Thanks.
Joe, it is possible that when Microsoft migrated the C:\ProgramData\Acronis\TrueImageHome\Database information from your previous version of Windows to Windows 10 that something got changed / corrupted in the database files related to your backup tasks.
Something DID get changed because the backup tasks had been working fine before that event.
Acronis should be looking into what is going on.
Joe, I do not know what Acronis could do in this situation - your upgrade between different versions of Windows and the migration of user data by Microsoft in that process is far outside the remit of the Acronis programmers to try to anticipate any potential issues that could arise. This would be equally true for any other applications that exhibited problems following such an upgrade.
If you wish to raise this directly with Acronis, then please use the Feedback tool in the application GUI Help section - this is just a user forum and an I am just another user like yourself apart from having been recognised as an MVP.
Acronis people SHOULD be monitoring the forum, where they might discover issues of importance. I don't have the time to jump through Acronis hoops and report things multiple times in diferent places.
If they don't care, then why should I?
I agree that this is an Acronis issue. My Windows 10 64-bit PC with TI 2016 has just upgraded to the Windows 10 1607 Anniversary update and the scheduled backup job now fails:
1 True Image 04/10/2016 12:57:48 Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 True Image 04/10/2016 12:57:48 Operation Samsung SSD 840 EVO started by schedule.
3 True Image 04/10/2016 12:57:50 Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
4 True Image 04/10/2016 12:57:50 Operation: Backup
5 True Image 04/10/2016 12:57:50 Priority changed to Low.
6 True Image 04/10/2016 12:57:50 The backup location was not found on the destination drive. Make sure the correct storage device is connected to the computer.
7 True Image 04/10/2016 12:57:50 Operation has completed with errors.
I have looked at the Acronis backup job and the destination drive is showing as expected:
E:\Acronis backups\Samsung SSD 840 EVO and this folder location exists as it has aways done.
mville, for other users who have encountered this type of problem, the simple way to solve the issue is to go into your backup task and reselect the destination drive, even if this is showing the correct information - reselect it and then save the task by clicking on either Backup now or at a later time.
It appears that the Windows 10 upgrade can cause disk / drive signatures to change and this causes the issue - reselecting the drive(s) will correct any incorrect information used by Acronis.
mville, for other users who have encountered this type of problem, the simple way to solve the issue is to go into your backup task and reselect the destination drive, even if this is showing the correct information - reselect it and then save the task by clicking on either Backup now or at a later time.
It appears that the Windows 10 upgrade can cause disk / drive signatures to change and this causes the issue - reselecting the drive(s) will correct any incorrect information used by Acronis.
I understand that due to the Windows 10 Anniversary update, that certain system/disk/registry changes have occurred.
However, none of my other 3rd party applications, that reference my non system disk C: drive i.e. my E: and F: drives, show any problems whatsoever.
So, something in the way that Acronis accesses disks in the Windows environment, is flawed and needs to be fixed.
First question, did you try as I suggested and if so, did it resolve the issue?
Secondly, how many of your other 3rd party applications store the unique disk identifier information (UUID) in a database for the drives involved as Acronis does?
I am not convinced that you are comparing apples with apples here, especially as the issue was caused by a Windows Upgrade with no change to the Acronis application.
First question, did you try as I suggested and if so, did it resolve the issue?
Secondly, how many of your other 3rd party applications store the unique disk identifier information (UUID) in a database for the drives involved as Acronis does?
I am not convinced that you are comparing apples with apples here, especially as the issue was caused by a Windows Upgrade with no change to the Acronis application.
Firstly, I tried the suggestion and at first, it DID NOT resolve the issue. After navigating and selecting the destination folder location, I got a large red circle with a white cross in between the source and destination windows in the Acronis software.
A little later, after trying again a couple of more times, the issue seemed to resolve itself, but I am left with little confidence in the software.
Secondly, are you suggesting that system critical systems running SQL Server etc. all need re-configuring after a Windows OS update? I don't think so (in fact, as a systems administrator, I know so).
As I say, the way Acronis accesses drives here is flawed. If the link between the backup job and the backup location has become compromised, the Acronis software should have built in tests for such and offer the end-user with an explanation and fix.
I am glad to hear that the issue has been resolved for you though it seems it didn't happen immediately.
On the second point, sorry but Acronis is not running SQL Server or anything of the kind, it is simply recording information in an SQL-lite database structure and the upgrade caused a mismatch to that information, so this is not about server systems etc.
I would agree that the Acronis software should be more resilient in terms of handling this type of change but given there was no change to that same software, this would need to be introduced in a future build version, assuming that Acronis deem it necessary to do that. Until users report this as an issue to Acronis it is unlikely to happen. This is a user support forum run mainly by users with little interaction by the people at Acronis who need to understand that this is a problem. I would encourage you to report this to Acronis using the Feedback tool found in the GUI Help section.
The changing of the source is a common issue with backup software after a Windows 10 upgrade - not just with Acronis (I see it with Retrospect and other backup applications such as AOMEI too).
The reason is that with each "upgrade" Windows 10 is actually being completely installed and a new recovery partition is being created, which changes the partition scheme on the drive, making the originally selected "disk" no longer possible since the partition layout was modified and the disk ID changed as a result.
In some cases, you may even end up with multiple recovery partitions on the hard drive after a Windows 10 upgrade. This AOMEI article explains the Windows 10 recovery partition change pretty well: http://www.disk-partition.com/windows-10/recovery-partition-after-upgrading-to-windows-10-4348.html
and this explains it too:
http://askubuntu.com/questions/200923/what-scenarios-causes-a-hard-drive-uuid-to-change
The Universally Unique Identifier (UUID) is integrated in the filesystem. By this we can recognize a filesystem by it's unique number to avoid confusion (e.g. when mounting drives).
Anything that affects the file-system will also change its UUID. Under normal circumstances this will be
- formatting a drive
- (re-)partitioning of a drive
Under rare circumstances we may be faced with an external drive that mounts a temporary filesystem (e.g. live systems booting from an USB drive). In this case the UUID may also change.
We can manually assign a fixed UUID to a drive if we wish:
This would be another scenario where the UUID of a drive changes.
In case we need manual control over the disk identifiers we may also use a disk LABEL:
You're most likely going to see this behavior with each Windows 10 "upgrade" with many backup applications as they do rely on the UUID of a disk to help eliminate users accidentally overwriting the wrong disk when they swap one out for another (for instance when chaning external usb drives that may not be plugged in at the same time, but that both show up as the D: drive when they are plugged in seperately).
The short and simple fix is to go into the backup task and not only select the source, but also the destination again after a Windows 10 upgrade.
As I said previously, if the link between the backup job and the selected/destination disks becomes compromised, for whatever reason, the Acronis software should have built in tests for such and offer the end-user with a warning/explanation/fix/notification etc., not just ignore it.
As you see this as such a big issue, please submit Feedback to Acronis for it to give them the opportunity to consider whether it is an issue that they can fix, rather than being one that can be circumvented by reselecting the source / target drives.
Agree with Steve.
There is a warning:
1) the backup doesnt run
2) You get a red dot on the backup job as a result
3) it says why in the logs (although the log reader is missing so it's best to use FTRPilot's logviewer until Acronis brings this back): The backup location was not found on the destination drive. Make sure the correct storage device is connected to the computer.
This behavior may be resolved in 2017, but I haven't tested as the specific change says it works only if the drive letter has changed - but probably still not if the UUID has changed too.
http://www.acronis.com/en-us/support/updates/changes.html?p=38886
- The application now works correctly if a drive letter changes (available on Windows only).