Every backup to external drive fails

I would stop using that backup task and create a new one that is also pointed to your D: drive.  However, make sure to use a new, unique name and put the backup in it's own folder (for good housekeeping) - don't put multiple backups in the same folder, and don't use the same name of older backups or you might run into trouble with old pointer references.  

Also, with that drive being D:, there's a good chance that Windows is changing the drive letter on you at some point.  Windows can only ever have one instance of a drive letter in use at a time.  You might set your backup with that drive while it is D:, but if you ever unplug it and then attach another drive (like a USB flash drive), or if another usb drive attaches itself to Windows before the USB drive at logon (it responds faster), your main backup drive could get bumpped from D: to E: or whatever the next available letter is.  Once the drive letter has been changed at any point, the backup will fail in most cases. 

Even if that is not the case, the message is staing the backup is corrupted, so let's not use that one at this point and try to use something new to test with.

Before you create your new backup, manually set D: to be something further in the alphabet - at least a few letters down so you can avoid this potential behavior.  Then create your new backup task, with unique name and it's own folder and try again.

Last, are you picking "entire pc" for your backup task or just the parition?  You should be doing a "full disk backup" so that 1) you pick only the specific disk you want ot backup - entire pc may try to backup other attached drives you don't want to be backed.  2) you want to backup more than just C: if you want to have a bootable OS after a restore.  The disk has other partitions that are needed to be bootable - the boot partiion (MBR or EFI) is critical for that. 

I agree that using Drive D can cause issues; for usb devices that I regularly connect to my PCs I use a drive letter towards the end of the alphabet.

Ian

Thanks a lot guys.

I have tried what you suggested, i.e. assigning a different letter - M: - to the external drive, creating a folder etc., but the problem is the same.

I am backing up the C: partition to a folder on the M: drive as you can see from the attached.

Any further ideas?

As an aside, I am not getting notifications of responses to this thread, even though it is set to.

You whould run chkdsk /f /r on both of the disk you are workiing with.  The error stating backup being corrupt indicates a problem with one of the drives.

Thanks I'll try that, but not sure that'll show up anything,  Not had a problem with anything except this.

chkdsk is 4% done on the external drive after 10 minutes, so I could be here for a while!

If you haven't done so already, download the Log File Viewer and check what is being written to the log for the tasks where these errors are being reported, there may be more information in the logs that will help isolate the cause of the error.  Link in my signature.

Steve Smith wrote:

If you haven't done so already, download the Log File Viewer and check what is being written to the log for the tasks where these errors are being reported, there may be more information in the logs that will help isolate the cause of the error.  Link in my signature.

Thanks Steve.

I can see this message in the log file:

'message=The backup has failed. Please close the application that may currently use the file: M:\Acronis\W10 Partition_full_b1_s1_v11.tib;  line_tag=0x4D3F22948E29F1C8;  hide=1'

Is that useful?
 

Sorry, I think that was a red herring.  Here is the log from one of the failed backups:

log uuid=CED6DC4B-C748-4237-B2EE-7CB0A4902CC8;  product=Acronis True Image;  version=20.0;  build=5554;  task=49DA2C47-329E-4937-B7F6-C72A3964542B;  task_name=W10 Partition
Start= 18/01/2017 14:28:54
id=1;  level=2;  module=100;  code=0;  date/time=18/01/2017 14:28:54
          message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=2;  level=2;  module=100;  code=2;  date/time=18/01/2017 14:28:54
          message=Operation W10 Partition started by schedule.
id=3;  level=2;  module=100;  code=0;  date/time=18/01/2017 14:28:56
          message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=4;  level=2;  module=316;  code=0;  date/time=18/01/2017 14:28:56
          message=Operation: Backup
id=5;  level=2;  module=100;  code=11;  date/time=18/01/2017 14:28:56
          message=Priority changed to Low.
id=6;  level=2;  module=11;  code=1008;  date/time=18/01/2017 14:28:56
          message=Create Backup Archive From: Windows (C:) To file: M:\Acronis\W10 Partition.tib Compression: Normal Exclude: Files matching mask Match criterion:
          hiberfil.sys
          pagefile.sys
          $Recycle.Bin
          swapfile.sys
          System Volume Information
          *.tib
          *.tib.metadata
          *.~
          *.tmp
          C:\Users\defaultuser0\AppData\Local\Temp
          C:\Users\imack\AppData\Local\Temp
          C:\Users\defaultuser0\AppData\Local\Microsoft\Windows\INetCache
          C:\Users\imack\AppData\Local\Microsoft\Windows\INetCache
          C:\Users\imack\AppData\Local\Google\Chrome\User Data\Default\Cache
          C:\Users\imack\AppData\Local\Opera Software
          C:\Users\imack\AppData\Local\Mozilla\Firefox\Profiles
          C:\Users\imack\AppData\Local\Google\Chrome\User Data\Default\Cache
          C:\Users\imack\AppData\Local\Opera Software
          C:\Users\imack\AppData\Local\Mozilla\Firefox\Profiles
          C:\Windows\CSC
id=7;  level=4;  module=1;  code=502;  date/time=18/01/2017 14:28:56
          message=The backup is corrupted, but you can still try to recover data from it.;  line_tag=0x65B5EB7011094700
Error_Code=AfYBAQAARwkRcOu1ZVRoZSBiYWNrdXAgaXMgY29ycnVwdGVkLCBidXQgeW91IGNhbiBzdGlsbCB0cnkgdG8gcmVjb3ZlciBkYXRhIGZyb20gaXQuACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzU1NTQAJGZpbGUAQWs6XDU1NTRccHJvY2Vzc29yXGRpc2thZG1cZGFfY29tbWl0LmNwcAAkZnVuYwBBRGFQcm9jZXNzb3I6OkNvbW1pdEltcGw6Ok9uRGFFcnJvcgAkbGluZQBOWQEAAAAAAAAAIAAHAGNWFXbPy/j1VGhlIGJhY2t1cCBpcyBjb3JydXB0ZWQsIGJ1dCB5b3UgY2FuIHN0aWxsIHRyeSB0byByZWNvdmVyIGRhdGEgZnJvbSBpdC4AJG1vZHVsZQBBdGlfZGVtb25fdnNfNTU1NAAkZmlsZQBBazpcNTU1NFxyZXNpemVyXGNvbXByZXNzXHpsaWJkZl9kLmNwcAAkZnVuYwBBcmVzaXplcjo6WkxpYkRlY29tcHJlc3Nvcjo6UHJvY2VzcwAkbGluZQBOZAAAAAAAAAAA
id=8;  level=4;  module=7;  code=32;  date/time=18/01/2017 14:28:56
          message=The backup is corrupted, but you can still try to recover data from it.;  line_tag=0xF5F8CBCF76155663;  hide=1
id=9;  level=4;  module=7;  code=32;  date/time=18/01/2017 14:28:56
          message=The backup is corrupted, but you can still try to recover data from it.;  line_tag=0x91BD40306B6C5084
Error_Code=ASAABwCEUGxrMEC9kVRoZSBiYWNrdXAgaXMgY29ycnVwdGVkLCBidXQgeW91IGNhbiBzdGlsbCB0cnkgdG8gcmVjb3ZlciBkYXRhIGZyb20gaXQuACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzU1NTQAJGZpbGUAQWs6XDU1NTRccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFxvcGVyYXRpb25zXGFyY2hpdmVfb3BlcmF0aW9uLmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpBcmNoaXZlOjpBcmNoaXZlT3BlcmF0aW9uOjpFeGVjdXRlACRsaW5lAE5uAAAAAAAAAAAgAAcAY1YVds/L+PVUaGUgYmFja3VwIGlzIGNvcnJ1cHRlZCwgYnV0IHlvdSBjYW4gc3RpbGwgdHJ5IHRvIHJlY292ZXIgZGF0YSBmcm9tIGl0LgAkbW9kdWxlAEF0aV9kZW1vbl92c181NTU0ACRmaWxlAEFrOlw1NTU0XHJlc2l6ZXJcY29tcHJlc3NcemxpYmRmX2QuY3BwACRmdW5jAEFyZXNpemVyOjpaTGliRGVjb21wcmVzc29yOjpQcm9jZXNzACRsaW5lAE5kAAAAAAAAAAA=
id=10;  level=4;  module=7;  code=32;  date/time=18/01/2017 14:28:56
          message=The backup is corrupted, but you can still try to recover data from it.;  line_tag=0xF5F8CBCF76155663;  hide=1
id=11;  level=4;  module=316;  code=5;  date/time=18/01/2017 14:28:57
          message=Operation has completed with errors.;  line_tag=0x9F2C53C72E8BCE4E
Error_Code=AQUAPAFOzosux1Msn09wZXJhdGlvbiBoYXMgY29tcGxldGVkIHdpdGggZXJyb3JzLgAkbW9kdWxlAEF0aV9kZW1vbl92c181NTU0ACRmaWxlAEFrOlw1NTU0XHByb2R1Y3RzXGltYWdlclxkZW1vblxtYWluLmNwcAAkZnVuYwBBbWFpbgAkbGluZQBOWAIAAAAAAAAA
Start= 18/01/2017 14:28:54
Finish= 18/01/2017 14:28:57
Total Time= 00:00:03

Interesting, do you have any other applications active on this system that may be trying to lock the backup image file such as a disk defragmenter or security software scanning files etc?

One certain way to prove that the backup drive is good would be to boot from the Acronis Rescue Media and do a full backup offline from Windows in that way - if that completes successfully then you know that you have something in Windows which is interfering in this process.

You say that the issue is backing up to an external drive. What sort of external drive, and how is it connected?

Don't connect via a hub, a port in a monitor, or a USB extension cord, etc. Connect the external drive directly to a USB port on the rear of the computer case.

Is it a USB 3 drive?

Guys,

The drive is a Seagate 2Tb USB 3.0 external drive.  I have run chkdsk with no errors.  It is normally connected to a powered hub, but, as suggested, I connected it directly and formatted the drive again.  I did the full partition backup successfully, but got the usual 'corrupted' message when try to do a subsequent one.

Steve, where do I get the Acronis Rescue Media from?

You can make the Rescue Media from within the Tools menu of the installed application - you have a choice of two types, the standard, Linux based media, or the Windows PE version media where this requires the Windows ADK to provide the PE part - ATIH Rescue Media Builder will direct you to install the ADK if you choose this option.

You would need the Rescue Media to make a bare metal recovery should your drive die and have to be replaced by a new one.

"Corrupted" is, unfortunately, a rather non-specific error message, in spite of its rather specific sounding term. It really just means that ATI can't validate the archive, which can be caused by disk errors or connection errors, rather than any problems with the .tib file itself.

Validation failure is often due to hardware issues. To troubleshoot, see Grover's backup and restore guides http://forum.acronis.com/forum/29618 and http://kb.acronis.com/content/1517

Try a different USB port. Try a different USB cable.

From an administrative command prompt, run chkdsk /r on each partition of the internal drive, and on the external HD. If there are hidden partitions, assign letters to them so you can chkdsk.
Also run a drive checking utility from the drive manufacturer, as those sometimes catch errors missed by chkdsk.

Are you still using the exact same backup job/name as before?  Did you also try creating a brand new backup task, with a new name and go from there?  If the old task and/or name that was previously used, has a pointer to some other old backup (for instance, if there are older backups on that drive, or somewhere else on the computer using that name), this could be part of the problem.

Thanks for sticking in there, I'm sure we'll figure it out.  The less "leftover" stuff though, the easier it may be to pinpoint the exact issue.

Have you also checked your Windows system logs for signs of any disk trouble?  Look for things with a yellow warning or red exclamation mark that might have something to do with hardware.  Probably not, but needs to be ruled out.

As for the USB cable - the hub is out of the way now, but where is it plugged into the system?  If it's a PC, use the back ports - more power.  Front ports may not have enough power and can randomly cutout at times with spinning drives (even smaller 2.5" drives).  I can use my front ports with an SSD, but regularly have issues for long read/write tasks on a spinning drive on any of my front USB ports.

What type of USB 3.0 cable as well - full size or micro?  I have a WD 1TB with a USB 3.0 micro and I hate it.  If you breath on it wrong, the micro end seems to lose connectivity.  I've actually taped the drive and cable to my desk to prevent it from coming out (it looks like it's connected, but it's like it barely makes contact at times).

The problem may not be with the HDD itslef, it could be a problem with the controller board that connects the SATA HDD to USB port. I have had several USB HDD fail not because of a problem with disk but with its controller board. This has not happened recently, and I have only seen it with 3.5" drives. Try running the Seatools diagnostics and see if it finds anything amiss. (Assuming that it checks USB HDDs.)

Ian

Guys, thanks for all your very useful comments.

So, in the last couple of days, I've re-installed Windows and True Image. Now, the backups work ok, EXCEPT for the fact that whenever I plug in the external drive, a message pops up saying something like 'Acronis True Image has a problem with this drive, please scan for errors'.

That doesn't stop True Image from completing the backups successfully every time. Weird. 

I have not seen any other issues with this drive, and I have run EVERY test there is in Seatools - as sugggested above - and there were no problems reported at all.

I remember another similar post. The guy put it in a different external case, if I rem bee correctly. Not really sure what would be causing that message.

try chkdsk as well, just in case.

chkdsk /f /r 

And doing so remedied the problem ???? My recollection is that that was the case. The issue is with the conroller card rather than the HDD itself.

Ian

Guys,

The backups are completing OK as there are correct looking tib files, and I get 'backup was successful' emails.  However, on the main screen, for the partition backup, both 'Last backup' and 'Total size' are blank!

Any thoughts?

If you are not seeing valid information for the Last backup and Total size information shown in the GUI, then the most likely reason is a problem with the Acronis Database.

You could try renaming or deleting the C:\ProgramData\Acronis\TrueImageHome\Database folder and allowing this to be recreated when you next start the main application.  To do this, you must first stop all Acronis Services and then end all Acronis programs to release any locks on the folder & files.

Hi Steve,

Yep, you were correct. Allowing the database to rebuild solved the problem.

Thanks again.

Glad to hear that the last problem is resolved.

Another question guys, is there a way to make TI prompt to insert drive for backup?  For example, on my Mac, I use Carbon Copy Cloner, and one of my backsups is scheduled for 5pm each day to an external drive.  If the drive is not connected - which is most of the time - any time I log in, CCC will always promt to ask for the drive to be made available.  Even if it is after the scheduled time, CCC is aware that a backup needs doing. Can True Image do this?  

The only option that I am aware of in this area is the ability to run a missed backup when an external drive is connected.  I cannot find any option to prompt for an external drive to be connected as you describe for CCC.

Hi Steve,

Where is that option, I can't see it, and it sounds like what I need!

Hi Steve,

Where is that option, I can't see it, and it sounds like what I need!

The option can be found in the Scheduling > Advanced settings section - see the ATIH 2017 User Guide section:

http://www.acronis.com/en-us/support/documentation/ATI2017/index.html#7941.html

Scroll down to the Advanced Settings area of the page, then you will see one bullet point:

• If you schedule a backup to a USB flash drive or validation of a backup that is located on a USB flash drive, one more check box appears: Run when the current device is attached. Selecting the check box will let you perform a missed operation when the USB flash drive is attached if it was disconnected at the scheduled time.

The user guide shows this for a USB flash drive, but it may also work for other types of USB drive so worth giving it a try to see if it would work for your external drive? 

Thanks Steve. I have that option ticked already, but it doesn't work. When I connect the drive, the backup does not start automatically. 

imacken go back into your task and re-select the source and the destination and save the change.  Then run the backup manually (to make sure it runs).  After that, then try unplugging and plugging the USB drive again.

I am wondering if your external drive information may have changed from when the backup task was selected?  Doing things like a restore/recovery, changing partition size, or Windows assigning a different letter to the drive can cause previously scheduled backups to stop working until the source and destination are re-selected to accomodate those new changes since the drive is seen by Acronis (and Windows) as a different device after some of these instances - even though they may appear to us to be the same in the foreground. 

duplicate post - deleted