Skip to main content

Backup location not found - Backup drive connected with correct drive letter

Thread needs solution
Regular Poster
Posts: 19
Comments: 83

Hi,

I'm running ATI 2017 with build 8058 on Windows 10 Fall Creators.  Last night my scheduled backup failed with error 0xb007f, the backup location was not found on the destination drive.  The drive is connected to my laptop with the correct drive letter.  ATI GUI shows the external drive as G:\ASUS Backup V6\.  I can access the drive using File Explorer, and I can view the tib files in the ASUS Backup V6 folder.  If I click on the down arrow on the ATI backup screen for the backup, one option is Open location.  Clicking on it opens a File Explorer window showing the tib files in the ASUS Backup V6 folder.  I have rebooted the laptop, disconnected and reconnected the external drive, and a manual start of the backup gives the same results.  I have attached the MVP Log Viewer log from my most recent attempt.  If you need more than the ti_demon log, let me know.  Is something clobbered within ATI?

Gary

0 Users found this helpful
Forum Star
Posts: 60
Comments: 1412

Gary,

Take a look in the folder:  C:\ProgramData\Acronis\TrueImageHome\Scripts

There will be a script (.tib.tis file) for this backup.  In the script file the <volumes_locations> section will show the drive identification and uri (drive letter, folder, and file name) for the destination.  Example below:

<volumes_locations>
                        <volume_location device_instance_id="STORAGE\VOLUME\{719568CB-7082-11E6-918E-806E6F6E6963}#0000000008100000" uri="D:\ATI_Test\Trial_full_b1_s1_v1.tib" volume_id="1121190054" />
                        <volume_location device_instance_id="STORAGE\VOLUME\{719568CB-7082-11E6-918E-806E6F6E6963}#0000000008100000" uri="D:\ATI_Test\@task@.tib" volume_id="0" />

ATI uses disk signature as well as drive letter/folder.

 

Regular Poster
Posts: 19
Comments: 83

This is what I found for volumes_locations

<volumes_locations>
                        <volume_location device_instance_id="STORAGE\VOLUME\{CA26A0B2-4C9C-11E7-833F-8019344091AA}#0000000000100000" uri="G:\ASUS Backup V6\GARYS-ASUS Backup V6_full_b21_s1_v1.tib" volume_id="2921349461" />
                        <volume_location device_instance_id="STORAGE\VOLUME\{CA26A0B2-4C9C-11E7-833F-8019344091AA}#0000000000100000" uri="G:\ASUS Backup V6\@task@.tib" volume_id="0" />
                    </volumes_locations>

Legend
Posts: 110
Comments: 29184

Gary, have you tried just reselecting the Destination drive for your backup task then either running the backup task or doing a Validation for it?

Forum Star
Posts: 60
Comments: 1412

Gary,

I would recommend giving Steve's suggestion a try.

If it works, then you should be good to go.  If not, the link below shows how to get a disk signature.

https://www.howtohaven.com/system/change-disk-signature.shtml

If the disk signature is the same as what's in the script file, then I really don't have any more suggestions.

 

In reply to by FtrPilot

Regular Poster
Posts: 19
Comments: 83

Randy and Steve,

The disk signature was completely different from the script file.  I followed Steve's suggestion to reselect the destination drive, and the backup is running.  I've searched to see if I could find a reason for the signature to change, but most of what I've found shows how to change the signature.  Because the backup is working I'm fine.  Thanks to both of you for all of your help.

Gary

Legend
Posts: 110
Comments: 29184

Gary, glad to hear the suggestion was good for your situation.  Drive signatures can change simply by doing a Windows Upgrade / Update to new build, when a new Recovery partition is created.

In reply to by Steve Smith

Regular Poster
Posts: 19
Comments: 83

Steve,

Now I know how the signature change occurred.  On Nov 30 the backup ran, and on Dec 1 I installed the Fall update for Windows Creators.  I'm certain I left the backup external drive connected during the update.

Gary

Forum Star
Posts: 60
Comments: 1412

Gary...glad it worked for you...thanks for the feedback and followup.

 

In reply to by FtrPilot

Regular Poster
Posts: 19
Comments: 83

One interesting thing about this issue.  If ATI can stop the backup because the disk signature is incorrect, why can't they stop a backup if the drive is mounted with the incorrect drive letter?  The drive letter is in the script.  There have been some occurrences where I realize I didn't have the external drive connected to my laptop 5 minutes prior to the scheduled backup.  I've hurried and connected it not noticing that it connected with the incorrect drive letter, and the backup proceeded without errors.  Of course, when it was time for automatic cleanup to delete that backup file, there were problems that I've been able to correct.

Gary

Forum Hero
Posts: 59
Comments: 9379

I believe the application should check for drive connection before running the task.  It may be that because you did hurriedly connect the drive that the backup ran anyway.

Best to provide feedback about this to Support.