Skip to main content

backup failure

Thread needs solution

Receiving the error message: "last backup failed.  Cannot open the backup".  Using Windows 7 and Acronis True Image 2016.  Have been successfully creating backups until this error.  The program shows both my source drives and backup location, so I don't understand what the problem is.  Thanks in advance for your help.

Paul

0 Users found this helpful

Paul, it could be a number of reasons - corruption of the source and/or backup drive, permission issues on the destination drive (is it a locally attached destination drive or a network drive), how much space is available on your destination drive?  

I'd suggest grabbing FTRPilot's Logviewer app and taking a look at the service logs to see if there is a more specific reason, in addition to checking some of the items mentioned above and then we can go from there.

 

As I have done weekly (or so), I am attempting two backup my C: and F: drives from my Windows PC desktop to my Western Digital 'my passport' 2TB portable drive that is only half full.  The USB connected portable drive requires unlocking, which I have done, so Acronis True Image 2016 recognizes the files on the drive.  This is the same procedure I have used successfully for the past several months until today's multiple failed attempts.

Paul

For starters, reboot, unlock your your external drive and try again.  If it still has issues, please grab the logviewer app and check some of the recent backup service logs with it to see if there is more information.  If you could post an Acronis System Report, your Windows System log and your Windows Applicaiton log, there would be a lot more information available to help determine the cause.  

Bobbo---Thank you for continuing to help.  I tried the backup again, after re-booting, but still no luck.  Same error message.

I can't seem to copy and paste the Acronis System Report to this, but here is the Windows Application log from your app:

log uuid=9197ED1C-08FA-4882-B089-7A85C20E7901; product=True Image; version=19.0; build=6027; task=CA446F08-C9E6-46E4-BA37-E57A92EEC4BA; task_name=My disks
Start= 4/17/2016 7:58:18 AM
event id=1; level=2; module=100; code=0; date/time=4/17/2016 7:58:18 AM
          message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
event id=2; level=2; module=100; code=2; date/time=4/17/2016 7:58:18 AM
          message=Operation My disks started manually.
event id=3; level=2; module=100; code=0; date/time=4/17/2016 7:58:18 AM
          message=Operation description: Stage Description.
event id=4; level=2; module=100; code=0; date/time=4/17/2016 7:58:23 AM
          message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
event id=5; level=2; module=316; code=0; date/time=4/17/2016 7:58:23 AM
          message=Operation: Backup
event id=6; level=2; module=100; code=11; date/time=4/17/2016 7:58:23 AM
          message=Priority changed to Low.
event id=7; level=3; module=485; code=35; date/time=4/17/2016 7:58:23 AM
          message=Cannot access the path: G:\My backups\My partitions\My disks_full_b5_s1_v1.tib; line_tag=0x4D3F22948E29F1C2
Error_Code=ASMA5QHC8SmOlCI/TUNhbm5vdCBhY2Nlc3MgdGhlIHBhdGg6IEc6XE15IGJhY2t1cHNcTXkgcGFydGl0aW9uc1xNeSBkaXNrc19mdWxsX2I1X3MxX3YxLnRpYgAkbW9kdWxlAE4AAAAAAAAAAAB/AAsAQnFIC6pAXgZUaGUgaW5pdGlhbCBmdWxsIGJhY2t1cCB2ZXJzaW9uIGlzIG5vdCBhY2Nlc3NpYmxlIGF0IHRoZSBtb21lbnQuACRtb2R1bGUATgAAAAAAAAAAAC0ABAAG/CE7e3Rf81RoZSBzcGVjaWZpZWQgZmlsZSBwYXRoIGRvZXMgbm90IGV4aXN0LgBmdW5jdGlvbgBBRmluZEZpcnN0RmlsZVcAcGF0aABXXFw/XEc6XE15IGJhY2t1cHNcTXkgcGFydGl0aW9uc1xNeSBkaXNrc19mdWxsX2I1X3MxX3YxLnRpYgAkbW9kdWxlAE4AAAAAAAAAAADw/wAA9LjtZL39KL1UaGUgc3lzdGVtIGNhbm5vdCBmaW5kIHRoZSBwYXRoIHNwZWNpZmllZABjb2RlAE4DAAeAAAAAACRtb2R1bGUATgAAAAAAAAAAAA==
event id=8; level=3; module=11; code=127; date/time=4/17/2016 7:58:23 AM
          message=The initial full backup version is not accessible at the moment.; line_tag=0x65E40AA0B487142; hide=1
event id=9; level=3; module=4; code=45; date/time=4/17/2016 7:58:23 AM
          message=The specified file path does not exist.; line_tag=0xF35F747B3B21FC06; hide=1
event id=10; level=3; module=0; code=65520; date/time=4/17/2016 7:58:23 AM
          message=The system cannot find the path specified; line_tag=0xBD28FDBD64EDB8F4; hide=1
event id=11; level=4; module=11; code=1001; date/time=4/17/2016 7:58:24 AM
          message=Cannot open the backup.; line_tag=0x65E40AA0B486F47
Error_Code=AekDCwBHb0gLqkBeBkNhbm5vdCBvcGVuIHRoZSBiYWNrdXAuACRtb2R1bGUATgAAAAAAAAAAAOkDCwBhPUUq13X1LQAkbW9kdWxlAE4AAAAAAAAAAAA=
event id=12; level=4; module=11; code=1001; date/time=4/17/2016 7:58:24 AM
          message= ; line_tag=0x2DF575D72A453D61; hide=1
event id=13; level=4; module=316; code=5; date/time=4/17/2016 7:58:25 AM
          message=Operation has completed with errors.; line_tag=0x9F2C53C72E8BCE5E
Error_Code=AQUAPAFezosux1Msn09wZXJhdGlvbiBoYXMgY29tcGxldGVkIHdpdGggZXJyb3JzLgAkbW9kdWxlAE4AAAAAAAAAAAA=
Start= 4/17/2016 7:58:18 AM
Finish= 4/17/2016 7:58:25 AM
Total Time= 00:00:07

Thanks again for your help.

Paul

Paul, thank you for the task log file information, this shows the following key points:

Cannot access the path: G:\My backups\My partitions\My disks_full_b5_s1_v1.tib

The initial full backup version is not accessible at the moment.

The specified file path does not exist.

The system cannot find the path specified;

Have you checked that your WD my passport drive is definitely using the drive letter G: ?

Next check that you can find the My disks_full_b5_s1_v1.tib file at the stated file path.

Please note that your drive path must match that configured in the Backup task being executed in order to satisfy the configuration held in the Acronis Database files.

 

Aha!  It seems Acronis TI is directed to the H: drive because the "unlocker" program on the drive, which is connected to G:, opens the contents on H:.

Perhaps I should force Acronis to the path on G:\My backups\My partitions\My disks_full_b5_s1_v1.tib

Paul

Bobbo---  To clarify, when I execute the unlocker to WD My Passpsort installed on the G: drive, it automatically shows the contents in the H: drive. 

That (H:\My Backups\My Partitions) is what Acronis True Image lists as the target drive.  Hence, the proper path doesn't exist.

Paul

Bobbo---  To clarify, when I execute the unlocker to WD My Passpsort installed on the G: drive, it automatically shows the contents in the H: drive. 

That (H:\My Backups\My Partitions) is what Acronis True Image lists as the target drive.  Hence, the proper path doesn't exist.

Paul

But when you create the backup, is the H: drive available? If yes, you can set up the task at that point.

It is also possible that Windows changes the drive letter depending on whether other disks, cards, devices are connected.

You might want to assign a fixed drive letter to the decrypted disk H: and change it to a letter towards the end of the alphabet. Then test whether the unlocking process ends up consistently giving the same drive letter. If yes, that should solve your issue.

If this doesn't solve your issue, consider creating an unlocked partition on your USB drive, and use the built in archive encryption to protect your backup information. YOu'd still want to assign a fixed drive letter to that unencrypted partition.

Ditto to Pat's post.  Windows will automatically try to assign the next available drive letter.  In some cases, a USB drive may normally be G or H in this case.  However, if another USB flash drive or some other media is plugged in first, it may get G or H that time and  bumg the letters on the portable drive to something else.  By setting it to something farther down the alphabet, it's likely this will occur.  And if it is drive X: while locked and becomes drive Y: when unlocked (can be any letters though), you do want to make sure to set the backup task for Y: and not X:.

Bobbo (and Pat and Steve)---Thanks.  I understand what you are saying, but the WD My Passport is definitely in USB port and showing in My Computer as drive G:.  However, only the "unlock" program appears in drive G:, with the balance of the files on the drive (a couple of previous, successful backups) showing up as drive H:.

When I configure Acronis TI to backup to H:\My Backups\My Partitions the operations fails and I receive the error message. 

Paul

What happens if once it's unlocked and showing up in H: if you close down Acronis, then restart it and  try to create a new backup job and point it to H: at that time?  Is it still throwing the error then?

Same problem.  I even tried backing up to a different folder in the H: drive.  Very frustrating.  Guess I'll try to call Acronis tomorrow.

Paul, have you rebuilt the OS or reinstalled or recovered by any chance?  Can you manually add/remote files to the drive in the same location (like creating a new .txt file).  Just want to make sure you still have access to make changes to it from outside of Acronis.  

It still seems odd that your backup drive is listed as G: drive in Acronis, but it is mounted as H: drive in Windows explorer.  But, you mention that pointing it to H: it still fails.

Can you make sure that your local account or "administrators" is the Ownder of the entire H: drive?  Perhaps retake ownsership and replicate the ownsership to all folders on the drive as well.  After doing that, then re-push the permissions on the entiere drive, making sure that your local accoutn and "administrators" both have MODIFY (read/write) or FULL access to the root and all subdirectories.   I have seen persmission issues like this if/when connecting an external drive from one machine and then connecting it another and back again and am wondering if the local system permissions somehow got changed in the process and now the drive is no longer "writeable" with you current account.

Maybe I confused you or mistated something earlier.  Both the G: drive and H: drive show up in Acronis...and Windows Explorer, as do my files in what Windows designated as H: drive...("My Backup" and sub folder, "My Partitions").  The contents of the G: drive contain the "Unlocker" program.

Paul

It sounds to me like there is an incomaptibility between the Unlocker program and Acronis.  Possibly there is a setting that you can make in the Unlocker to enable a third party app like Acronis to have access.

Thanks to all who posted suggestion and tried to help.  It turns out the problem was with the Acronis True Image software.  Technical Support found and fixed the problem.

Paul

Excellent - did they say what the issue is/was?  It looks like the new version was released today as well...

Latest Build: #6559 (Size: 476.62 MB2016-04-18 00:00:00
MD5: 0f9be8b1e5c047cb273aefec371a2ec3

List of changes

 

What’s new?

  • Full support for high-DPI screens.
  • The "Do not show again" option has been added to the product notifications in the Windows taskbar notification area.
  • Improved design and usability of the product notifications in the Windows taskbar notification area.
  • Custom text labels in the subject of the email notification messages that simplify monitoring backup statuses.
  • Timing of the product notifications has been coordinated.
  • An option to limit the upload speed when you back up data to Acronis Cloud.
  • Acronis Media Add-on has been included in the product installer.
  • An option to force a computer shutdown while a backup is in progress.

Fixed issues

This release includes the following issue fixes, increased stability, and performance improvements:

  • Acronis True Image 2016 disables Windows 10 fast startup
  • The message about terminating current operations prevents a computer from shutdown
  • Under bootable media, Acronis True Image 2016 (build 6027) doesn't see the internal disk on Microsoft Surface 3 and Microsoft Surface 4
  • The error "Cannot create a database" appears when starting Acronis True Image 2016
  • The default subject of email notification messages is changed to the computer name
  • A disk cloning operation fails, and the computer boots directly to Windows
  • The default sync was deleted after the product update from Hotfix 3 (build 5634) to Update 1 (build 6027)
  • Only the first custom backup scheme is saved correctly
  • The current Try&Decide changes are discarded after you select to keep them when the computer restarts
  • A P2P sync fails when you join this sync on the second computer