Skip to main content

Backup fails with 'backup location was not found', but validation is fine...!

Forum Member
Posts: 23
Comments: 28

TI Build 6571 (current at 20th Aug 16) under Win10

I have a simple backup job that takes full backups to an external disk.

After several successful backups over the last threee months, the job is now failing with:
“The last backup has failed. The backup location was not found on the destination drive. Make sure the correct storage device is connected to the computer.”

I run a Validate using the same backup job (from the  ‘down arrow in ring’).

Validate works fine and red error mark o the backup job (and in the middle of the screen between source and destination) vanishes.

Excellent.

I run the backup job again. Fails with the same error!

 

The only clue I have is that when I last ran backups, version 1 (i.e ….b1-s1-v1.tib) was not present on the destination drive (I wouldn’t delete it, and chkdsk shows no errors; perhaps TI deleted it to keep within the disk-space rules I have set , but I also have told TI to ‘keep the first backup’; so where it has gone is a mystery). The validation that immediately followed gave me the option to ignore this first version, so I did. And subsequent validations has been fine.

I know that validation is supposed to bring the Acronis database of backups into sync with the actual backup files. And what TI thinks was the last backup (at the top of the screen) is displayed in the list of backup files when I ‘open location’ for that job. So everything looks OK but TI thinks otherwise.

Any ideas pls?

 

Forum Hero
Posts: 28
Comments: 9202
mvp

Top

[quote=decomplexity]

After several successful backups over the last threee months, the job is now failing with:
“The last backup has failed. The backup location was not found on the destination drive. Make sure the correct storage device is connected to the computer.”
Validate works fine and red error mark o the backup job (and in the middle of the screen between source and destination) vanishes.  I run the backup job again. Fails with the same error!

[/quote]

decomplexity, do you have the Log File Viewer app (link in my signature below), if so, what does this say about this problem?

Have all your backup tasks been pointed to the same external disk drive without any change of drives?

Have you considered creating a clone of the current task then deleting the original task settings before trying to run the cloned task?

Forum Hero
Posts: 35
Comments: 6086
mvp

Top

What if you re-pick the source and destination again in your backup task?  Does it then run, or give the same behavior.  I'd try that first, and if no dice, try the clone settings featuer that Steve mentions up above. 

Forum Member
Posts: 23
Comments: 28

Top

Tnx Steve and Bobbo

After the failure, I located looked at the log but was no wiser (I have bolded the key error message):

<log uuid="147E3BC7-D2F5-4B08-9A97-C9C704DC5D22" product="True Image" version="19.0" build="6571" task="96F88B9D-3436-46BB-BAAB-B4BBF2A7A8AF" task_name="Win10 Mary tower disk A" >
    <event id="1" level="2" module="100" code="0" time="1471721114" message="Backup reserve copy attributes: format tib; need_reserve_backup_copy false;&#32;" />
    <event id="2" level="2" module="100" code="2" time="1471721114" message="Operation Win10 Mary tower disk A started manually." />
    <event id="3" level="2" module="100" code="0" time="1471721115" message="Backup reserve copy attributes: format tib; need_reserve_backup_copy false;&#32;" />
    <event id="4" level="2" module="316" code="0" time="1471721115" message="Operation: Backup" />
    <event id="5" level="2" module="100" code="11" time="1471721115" message="Priority changed to Low." />
    <event id="6" level="4" module="11" code="127" time="1471721115" message="The backup location was not found on the destination drive. Make sure the correct storage device is connected to the computer." line_tag="0x65E40AA0B487146" >
        <error>AX8ACwBGcUgLqkBeBlRoZSBiYWNrdXAgbG9jYXRpb24gd2FzIG5vdCBmb3VuZCBvbiB0aGUgZGVzdGluYXRpb24gZHJpdmUuIE1ha2Ugc3VyZSB0aGUgY29ycmVjdCBzdG9yYWdlIGRldmljZSBpcyBjb25uZWN0ZWQgdG8gdGhlIGNvbXB1dGVyLgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTcxACRmaWxlAEFrOlw2NTcxXHByb2R1Y3RzXGltYWdlclxhcmNoaXZlXGltcGxcb3BlcmF0aW9uc1xhcmNoaXZlX29wZXJhdGlvbl9iYWNrdXAuY3BwACRmdW5jAEFUcnVlSW1hZ2U6OkFyY2hpdmU6OkJhY2t1cEFyY2hpdmVPcGVyYXRpb25JbXBsOjpDaGVja0xhc3RWb2x1bWVEZXZpY2VJZE1hdGNoACRsaW5lAE61AgAAAAAAAAA=</error>
    </event>
    <event id="7" level="4" module="316" code="5" time="1471721116" message="Operation has completed with errors." line_tag="0x9F2C53C72E8BCE7C" >
        <error>AQUAPAF8zosux1Msn09wZXJhdGlvbiBoYXMgY29tcGxldGVkIHdpdGggZXJyb3JzLgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTcxACRmaWxlAEFrOlw2NTcxXHByb2R1Y3RzXGltYWdlclxkZW1vblxtYWluLmNwcAAkZnVuYwBBbWFpbgAkbGluZQBOhgIAAAAAAAAA</error>
    </event>
    <event id="8" level="2" module="103" code="0" time="1471721118" message="The e-mail notification has been successfully sent." />
    <event id="9" level="4" module="103" code="0" time="1471721118" message="Batch operation has completed with errors." />
</log>
 

Re Steve's question: "Have all your backup tasks been pointed to the same external disk drive without any change of drives?" I alternate two backup jobs (A and B) and two external disks (marked A and B), and I did check that I hadn't accidentally used backup job A to back up to drive B (each disk has a backups folder whose name includes the disk letter (A or B) to try to pre-empt this. (The disk with latest backup goes into a 'media' fire safe.)

I will pick the source and destination again as Bobbo suggests and see what happens.

If no joy I will clone the job.

If this doesn't work,  I will define a new job (and let the existing backups sit where they are unti they are totally superseded

Clearly, there is a mismatch between which .tibs validate looks for and what backup looks for. And this should be impossible if Acronis was working consistently.

It could just be a spurious error when Acronis gets confused between teh job definition saying "keep teh first backup version" and it not being present!

Forum Hero
Posts: 35
Comments: 6086
mvp

Top

Keep us posted with the results after resetting the source and destination drives again.  

Be careful of Windows automatically assigning drives different letters too - this is common when using the defaullt assigned letter as it is usually D or E or whatever the next available letter is.   This is a good article that explains the exact issue and how to resolve it. 

http://www.howtogeek.com/96298/assign-a-static-drive-letter-to-a-usb-drive-in-windows-7/  

If the drives share the same drive letter because they are usually not plugged in at the same time, but then get plugged in at the same time, Windows will assign a new letter to the last one plugged in and it will retain that letter (unless it gets bumpped further again).  This can happen if you have another drive plugged in (say a flash drive) that picks up that letter by default and then you plug in the backup drive.  It happens a lot more than you'd think and many users don't even realize it.  

Because of this possibility, you might want to change your drive letters further down the alphabet where it's less likely to occur (for instance, start with N and make the other drive O - then re-pick the source and destination in your backup tasks and give them a whirl).  

 

 

Forum Member
Posts: 23
Comments: 28

Top

Tnx Bobbo

I will investigate. The error could be TI 2016's version of the the 2010 (and similar) error when if it could not find a drive at the setup driver letter would try to back up to C:  (i.e. back up to the same disk). If is proves to be so, the present error message is at least an improvement on finding your system drive full of .tibs or - worse - having a hosed C:  and finding that the backups you expected to use for recovery from an external disk werre not there!

It would not explain how Validate successfully finds the backups to validate, but stranger things have happened

Max

Forum Member
Posts: 23
Comments: 28

Top

A solution (suggested by Bobbo:  thank you):

Note firstly that the backup job is set up to use a folder on an external E: drive. Windows File Explorer agrees that the drive contains the desired folder containing the previous .tib versions

- select the failing backup job and run a validate with it. Result- OK (so it should be!)

- start a backup with the job. Result - fail ("The backup location was not found ...." - as before)

- redefine the Custom Destination to be exactly the same as it was (the log confirms this)

- start the backup job again. Result: Success!

Conclusion: the backup job can succeed on Validate and fail on Backup using the same job definition and without moving the external drive and a solution (for me at least) was to redefine the destination to exactly what it was. 

 

 

Forum Hero
Posts: 35
Comments: 6086
mvp

Top

Glad to hear it!  I think we'll be seeing more of this behavior with windows 10 "upgrades".  these upgrades are really full OS installs and it appears as though each install rebuilds the Windows Recovery parition, which may be changing the ID's of the drive and causing this behavior in Acronis.  Doesn't seem to happen for everyone, but seems to be happening enough.  At least it's not too difficult to go back in and reselect the source and/or destination as the exact same location again to get it working if this does happen after the Windows upgrade has occured.  

Beginner
Posts: 0
Comments: 1

Top

A year later and this is still a problem in True Image 2016. Very frustrating especially because the error message is so lacking in diagnostic detail!

Beginner
Posts: 0
Comments: 1

Top

True Image 2017, and this issue just happened to me.  I didnt notice until after a month that my backups were failing.  Re-establishing the backup destination did the trick.  Very stupid, fix this bug. 

I have a feeling though, that this issue occured around the same time when my account came for renew and maybe that cuased some issue...