Backs up drive to a file, gives an error and then says it hasn't backed up at all

I tried to do one more backup and it added a second file but still came up with the error message and now says my backup is corrupted. What is going on?

The log indicates the full backup is not good, so the inc+full will be no good as well.
Delete your task and create a new one.

I created a new backup and it appears to have worked. Why does it say there are 26 versions when I just created it last night??

You can delete the archives.xml files located in the C:\program data\Acronis\True Image Home\Database\ (or something like that) folder. That should clean up the indications in the UI.

There is definitely confusion within the data base which is causing the appearance of the 26 versions listed as part of the task.
There are several approaches. The deletion of the XML file will delete all the file history (tib backups untouched) and will also delete ALL backup tasks listed including your listing of cloud backups. The net result will be the removal of listed backup tasks which will require the creation of all new tasks both for the cloud and your normal backups.
C:\program data\Acronis\True Image Home\Database\
=======================
Another option would be to use the "Remove from List" option and remove the "K&C Partitions" task from the listing of tasks (tib backups untouched). This will force you to create a new task.
http://forum.acronis.com/system/files/one_task-remove-all.png

This will force you to create a new task. It is possible there are some similarities between the new and the old listing of backups.
For the new task, I would suggest you avoid any consolidation options (use Automatic Cleanup). When creating the new backup scheme, you have been using the option based on elapsed days. I have had much better success when using the "store no more than X recent version chains which is my recommendation that you use.

custom/incremental/Automatic cleanup/store no more than X wrote:

Figure 11-Inc: Example of custom/incremental backup method settings
If using incremental type backups (which is full + X Inc), the 11-Inc is my recommended method. Change the 6 or 4 to fit your available storage.
These automatic cleanup settings will provide for automatic deletion of the oldest backups after the "Store no more than X recent version chains" once quota has been reached.
In this example, deletion of oldest backup will occur immediately following creation of backup #29.

Allow space for 1 more full backup in addition to "Store no more than X number of chains" as the program will NOT delete the oldest full until its replacement has been successfully created.

In this example, one chain or one recent version chain =1 full plus 6 inc or 7 files per chain.
If keeping 4 recent version chains (4 chains of 7 each) retention would be 28 files. Deletion of oldest chain will occur after backup 29 (full).

Also understand the limitations/risk factor of incremental backups. If one inc backups gets corrupt or accidentally deleted, all newer inc are worthless so avoid excessive number of incremental backups. Always maintain a full backup set which are current This explains why keeping a reasonable number of x "recent version chains" can be very important. Keeping a high number of incremental is a high risk factor to your backup data and should be avoided.
For a better understanding of the differences between Inc and Dif as it relates to the safety factor, review this link.
http://forum.acronis.com/forum/40810

When restoring an Incremental backup, select the specific Inc file to be restored and all preceding Incremental files plus the full backup base must be present and will be restored (multiple files required).

=================================
When creating the new task, select a new folder with a name which has not exist elsewhere
Use a new name on the backup task which has not been used before
Also consider assigning a letter to your MyBook at the end of the alphabet so there will be no future mixup of drive letters. (If Cloud backups using H, those backups would fail.)

I note you are creating "partition" backups. I would recommend you change that to "disk mode" or "disk image" backups which is as simple as selecting the option "Switch to disk mode".
http://forum.acronis.com/system/files/mvp/user285/misc/disk-image-backu…

For more information about this type backup, click on Signature link 2 below and look at the first illustration.
Here is short video on creating custom storage folders and custom backup tib file names.
http://screencast.com/t/IaxVq1tQME
===================================
Another option to correct the listing of 25 problem would be to attempt to edit the "ARCHIVES.XML" file found in the DATABASE folder of the Acronis, and remove all the duplications. This is easier said than done. Often times, editing will make things worse and force the user to delete the Archives.xml file anyway.
If you have the time, would you consider uploading me a text copy of that xml file for my viewing. It would be very helpful in viewing its contents. I am very curious about what is inside that file causing the unwanted listing of 25. I am not suggesting this as the cure but it is an option.

Use Windows Explorer and browse to that xml file
----- C:\program data\Acronis\True Image Home\Database\Archives.xml----------
Use the "Open With" option and select with NotePad.
Review its contents for your own curiosity and then
Click the "File Save As" option and change the extension from xml to TXT
so the file will be saved as ARCHIVES.TXT.
Attach the Archives.txt file to one of your future postings.

========================================
Regarding the error which occurred on one of your backups. The cause might be a file or disk error. You might consider checking for disk or file errors on ALL the partitions on the system disk including any non-lettered partitions. To check an unlettered partition, you need to use Windows Disk Management and temporarily assign a drive letter to the partition and check it for errors. After checking, then removed the temp drive letter and return the partition to its non-lettered status.

Attached is the archive file. There is an xml file called mounted.xml. Should I delete or rename that too?

Elizabeth,
Thank you for the archives file. You were very kind to provide it.

If you are interested, I believe we can edit the file and remove most of its content and make it functional again, if you are willing.
If you choose to follow this path, what is discussed next cannot be implemented in parts, it is all or not at all.

All of our actual backup files in your storage folders would remain untouched. If restorable or non-restorable, , they would continue as is for future use.

Actions by you:
1. You would need manually use the "Remove from task" option and remove ALL backup tasks from list except the Online Cloud task.
Only the Cloud task would remain.
http://forum.acronis.com/system/files/one_task-remove-all.png

2. Recreate all new tasks as discussed in preceding post. Each task would point to a new sub-folder with a new tib backup file name.
The new tasks could be either scheduled or non-scheduled as you prefer but I do suggest the use of the Automatic cleanup using the option to "Store no more than X recent version chains."

3. Before any new task creation, you would need to Windows delete several of the scripts found in the Scripts folder.
----- C:\program data\Acronis\True Image Home\Scripts\---------
I will need to see a screen capture of this scripts file.
Sort the folder on date/time before doing the capture.

4. Use Notepad and edit the archives.xml file with my suggested changes--to be provided after examination of scripts folder.

5. Risk factors:
No risk to your tib backup files but if for any reason, TrueImage rejects the editing of the xml file, then you might have to start over with all tasks including the Cloud task.
I really do not know how TI will react as as I have not been involved with the Cloud.

6. If you want to proceed, then provide the scripts capture jpg so I can determine which scripts to keep or delete based on the contents of the current archives.txt file.

7. Its your call.

OK let's try it. I attached my current screen and the scripts files.

Sorry here is the scripts files

Don't make any more changes until we get finished with the editing.
Open the script folder and look at the Sep 30 item in Notepad--if that will open it.
See what other info it contains as it has 0 bytes.

That file has nothing in it.

Note the two attacments. The instructions are in one file and a finished example in the other.
With TrueImage closed, after you perform the edit and save the file as ARCHIVES.XML (not txt)
then delete everything in the scripts folder.
and except for cloud, remove the other backup tasks via the "Remove from list" option.
Let me know how you make out. This is my last posting for the night.

Note: if during the edit, you need to start over with a new edit, just discard the bad file without saveing and reopen the xml file again.
It is important that Notepad be opened in Run as Administrator mode as per instructions.

Edit: I would urge you to check your partitons for file or disk errors as per my prior post. This may(?) be the cause of your error on your other file.

I deleted the section in the archive file and all the scripts files. When I went back into the program the old backups schemes were gone so I didn't need to remove from task. After reading your cautions about incremental backups I set up the new backup as a differential with 5 differentials and no more than three chains.

I will let you know how it went after it is finished with the backup.

Question: Did the deletion of the scripts also remove the backup task for the online backup?
Automatic cleanup will begin after the 4 full which will be backup #19. (1+5=6 backups per chain and keep 3 chains=18 backups stored.)
Deletion of old files will begin after the 4th full or after backup #22 at which time the first chain (6 files) will be deleted.

Deleting the scripts files deleted the tasks when I did it last night but this morning the old tasks reappeared. I deleted the tasks (not the files) for each of them. Hopefully they don't reappear again. The backups seem to to working. I got a 3TB external drive for backups so I switched to differential backups. Attached is the differential setup I am using. Any comments or suggestions.

Grover H

Now the cloud backup isn't working. It is supposed to backup daily and hasn't backed up in two days. The other two worked last night.

Depending upon what you want to do.
Option 1: Edit the scheduled time to something different-such as by a minute and see if that helps.
Option 2: Start over with a new task.
Option 3: If you would want to copy the scripts folder from your last backup (before the new one last night) and zip those scripts into a zip file, I would be willing to look inside each via notepad to see if there is any association with the cloud backup. Based on what I saw in the xml file, none of the scripts appeared involved but i could look further. If we find that one is involved, we could copy that one backup into service and see if that helps. Its a longshot but we can try if you wish. This was one of the risk factors where I was not sure what would happen with the cloud backup. You might want to run the cloud manually unitil you decide what you want to do.

I deleted the old cloud backup and am now backing up a new version that has a different name. It will probably take all night. I do hope this is the last time I have to fiddle with this program to get my backups to work.