Backup Fails
When I tried to backup just now it quit with this message: It shows a red circle with a white X in the center and the message says "Unknown Status"
That is, indeed, a pretty uninformative message, but I think we will need more information to understand what might be going on.
What are the source and destination devices (internal drive, external USB-attached drive, NAS,etc.)? What kind of backup are you attempting (entire PC, disks and partitions, files and folders)?
Have you done anything such as moving or renaming the backup file(s) since the last successful run? Has there been a successful run?
Is the backup task new in ATI 2020 or is it from an older version of ATI?
This is a backup I've made many times with version 2016 and made once with 2020. It is from my windows SSD to an external backup drive. Because I make routine full disk images I must delete one to make room for another. When I tried to delete one I got a 'You need administrator privileges' message. I am an administrator. This didn't help. I finally had to use Fileassassin to remove the backup. Then when I tried to create a new backup I got the message shown in my OP.
Jim, couple of points to pick up on in your post above.
1. ATI 2020 includes Acronis Active Protection which was not around for ATI 2016 - this is why you got the message about needing Administrator to delete backup files. AAP protects those files so you should turn it off before deleting files outside of ATI.
2. Deleting ATI 2020 backup files outside of ATI is a recipe for issues such as this! There are more dependencies on ATI files, especially the new .tibx files than in any earlier version! This is something other users have found and complained about!
I would recommend trying to run a Validation for your backup task where you have deleting files to see if that will help resolve things.
See the following KB documents published by Acronis with regards to .tibx files.
KB 63518: Acronis True Image 2020: do not delete first tibx file
KB 63227: Acronis True Image: Do not delete .TIB or .TIBX files outside of Acronis True Image
KB 63498: Acronis True Image 2020: new tibx backup format FAQ
KB 63425: Acronis True Image 2020: Limitations of tibx backups
KB 63445: Acronis True Image 2020: how to view and manage backup versions in new backup format
KB 63444: Acronis True Image 2020: tibx backups in local destinations
KB 63613: Acronis True Image: local backups are not available for recovery if "metadata" file appears in the backup destination - if you see metadata file(s).
This is exactly the kind of crap that made me reluctant to upgrade.
Using Acronis, I removed the backup I had previously deleted . It still fails to backup and gives the same message as in my original post.
I do not know how to do a validation. I didn't find it in Tools. I tried to follow the procedure about right clicking on a file and choosing validate but all it did is throw me back into the Acronis program.
Apparently in "protects" files made with 2016 as well as files made with 2020.
Of the links you gave these two are scary:
https://kb.acronis.com/content/63613 (sounds ominous)
https://kb.acronis.com/content/63425 (I don't really understand these but it sounds bad)
But, back to my problem. How do I make Acronis do a backup???
For what it's worth, I turned off Active Protection and tried again. It didn't help.
jim wrote:Using Acronis, I removed the backup I had previously deleted . It still fails to backup and gives the same message as in my original post.
This seems odd. Are you saying that you deleted the backup task, recreated it, and it still gives the error message? Are all the .tibx files relating to that backup task gone? Maybe there are some left and this is confusing ATI.
jim wrote:I do not know how to do a validation. I didn't find it in Tools. I tried to follow the procedure about right clicking on a file and choosing validate but all it did is throw me back into the Acronis program.
Validation will throw you back into ATI; it is an ATI function. You can also access it from within the ATI GUI by right clicking on the backup task name and selecting "Validate" from the drop-down menu. (But if you've deleted and recreated the backup task, that option probably won't be available.
You can also do a Validate by booting an ATI Recovery Medium and selecting Validate. That will validate the file, but you will probably then have to do an "Add existing backup". (Someone will correct me if I'm wrong.)
jim wrote:Apparently in "protects" files made with 2016 as well as files made with 2020.
AAP will protect any .tib or .tibx file, regardless of the version of ATI that created it.
jim wrote:Of the links you gave these two are scary:
https://kb.acronis.com/content/63613 (sounds ominous)
https://kb.acronis.com/content/63425 (I don't really understand these but it sounds bad)But, back to my problem. How do I make Acronis do a backup???
At the very worst, you may have to delete the existing backup chain(s), delete the backup task(s), recreate the backup task, and run it. Then, don't delete any of the backup files by any means other than the Cleanup function in the ATI GUI ... another function available by right clicking the task name.
By the way, my guess is that the Acronis developers had no idea that ATI users deleted backup files outside of ATI or they would have done a better job of providing equivalent functionality. And they would have done a better job of documenting the new restriction.
Providing feedback may prompt them to make this functionality available in a form that does not damage the backups.
jim wrote:For what it's worth, I turned off Active Protection and tried again. It didn't help.
What does "It didn't help" mean? Turning off AAP will let you delete .tib and .tibx files without ATI blocking the deletion. But deleting part of the backup chain will still render the backup chain unusable. Turning off AAP will allow you to delete all of the broken chains and start over afresh.
Jim, for validation - look to the right of your task name for a 'V' icon which will then show a drop-down menu when clicked on, where you will find the Validate option for the task.
As to why you cannot create a backup, sorry but just too little information to know what the problem is?
Please download the MVP Log Viewer tool (link in my signature below) and use this to review the log file for your backup operation. This should provide more information on why you are seeing any notification messages?
Your post covers a lot. I will try to address the salient points.
I didn't follow your first remark. I had deleted a backup outside of Acronis. Somehow when I looked at deleting backups the official way it still knew about the missing backup and I was able to delete it. I did not recreate it because I cannot get Acronis to create a new backup.
Your second remark. I have three backups made using the same backup task. How will it know which backup I want validated, or will it validate them all?
Your third remarks. I don't have backup chains. All of my backups are full image files. I am unwilling to delete what I hope are valid backups just to find I still cannot backup, then I not backed up at all.
Your last. As a minimum they could warn you when you try to delete a backup you must delete using the Acronis program to avoid making a mess. They have to know you are trying to delete it because they're the ones preventing the deletion
for validation - look to the right of your task name for a 'V' icon which will then show a drop-down menu when clicked on, where you will find the Validate option for the task.
See my explanation above.
I will download MVP log viewer
C:\ProgramData\Acronis\TrueImageHome\Logs\ti_demon\ti_demon_9CFA3F67-CFBD-4F9F-B09C-5349007D5609_FABE833D-D92D-487B-81CF-D404EB9BB38C_2019-12-30-12-23-19.log
12/30/2019 12:23:19 PM: -----
12/30/2019 12:23:19 PM: ATI Demon started. Version: 24.5.1.22510.
12/30/2019 12:23:19 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
12/30/2019 12:23:19 PM: Operation Copy C to D started manually.
12/30/2019 12:23:19 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
12/30/2019 12:23:19 PM: Operation: Backup
12/30/2019 12:23:19 PM: Priority changed to Low.
12/30/2019 12:23:19 PM: Create Backup Archive From: Disk 1 To file: C:\AcronisBackup\Copy C to D.tib Compression: Normal Exclude: Files matching mask Match criterion:LIST OF FILES TO EXCLUDE
12/30/2019 12:23:19 PM: Pending operation 174 started: 'Creating partition image'.
12/30/2019 12:23:19 PM: Writing full version to file: Copy C to D_full_b16_s1_v1.tib
12/30/2019 12:23:28 PM: Pending operation 174 started: 'Creating partition image'.
12/30/2019 12:23:29 PM: Pending operation 174 started: 'Creating partition image'.
12/30/2019 12:23:29 PM: Error 0x101f6: Failed to create volume snapshot.
12/30/2019 12:23:29 PM: Error 0x13c0005: Operation has completed with errors.
Start: 12/30/2019 12:23:19 PM
Stop: 12/30/2019 12:23:29 PM
Total Time: 00:00:10
What does "It didn't help" mean?
It means I still can't create a backup
Error 0x101f6: Failed to create volume snapshot.
Please do a full shutdown of Windows and then restart again as a first step, then download the Acronis VSS Doctor tool, run this as Administrator and let it fix any VSS issues that it finds.
The volume snapshot is created using Microsoft VSS which is the issue shown in your log.
The backup drive is D:
The only anomolies found were on C: & F: which are my main internal drives
Jim, just looking at your backup log again, the following does not look correct!
Create Backup Archive From: Disk 1 To file: C:\AcronisBackup\Copy C to D.tib
The above suggests you are creating the backup on the same drive C: as the source data?
No. I'm using the method described by Jim Rogers in the 6th comment of this thread
The redirection should be transparent to Acronis. I've been using this method for more than two years and it worked at least once and I think twice to create images with 2020.
Jim, are you also changing drives when using this symbolic link method to redirect the backup?
No. The target is always the same drive, D: I have not changed the backup setup/job/configuration or whatever it's called from 2016
Jim, assuming that your source for this backup (Disk 1) is also the C: drive, then in essence you are asking ATI to backup itself to itself (from C: to C:\AcronisBackup\Copy C to D.tib) which may be part of the issue here, regardless of using a symbolic link.
Have you tested changing the Destination to the physical D: drive for the backup?
Do you have another partition or internal drive that you could use for the location of the symbolic link rather than on the source disk?
Hi Jim,
Your .jpg you posted shows I/O load errors on drives C and F. This means that at the time the backup is scheduled to run, disk activity on these two volumes will not allow VSS to create the snapshot necessary to allow the backup to run. There are a number of possible causes for this.
- Failed VSS writer
- Application running that is not VSS aware (doubtful)
- VSS writer timeout.
It appears that in your case VSS writer timeout is responsible for the backup failure.
You can learn more at the links below:
It would be of benefit to check Windows Error logs to find what they show as well for time periods when the backup task has failed to run. The link below is for a Microsoft Tech Net Article which discusses what these errors are and link to steps to resolve them.
It should be possible for you to discover what applications or processes are running on the affected volumes at the time your backup task is scheduled to run. If possible to change the backup schedule time to a time when these processes are not running that should resolve the VSS issue you have. It is possible, that if this turns out to be a specific application is causing the timeout issue, there is a good chance that the VSS writer for this application is faulty. In this case resolution to that issue would be only available from that application creator.
Do you have another partition or internal drive that you could use for the location of the symbolic link rather than on the source disk?
Yes, I do. But, it's been too long (or version 2020 changed how you choose the target) and I can't figure out where I would change the address of the symbolic link from C: to F:
I created the symbolic link on Drive F: but this version of Acronis appears to only give me options for destination that are in its list. And, it appears to only list folders and not shortcuts. I can't figure out how to enter a destination of my choosing
Jim, first question: do you really need to use a symbolic link here, as if not, you can just click on the Destination panel for your task in ATI 2020, select the actual location where your backup files are stored. The only extra step that may be needed, if the Recovery tab shows 'nothing to recover', would be to use the 'Add existing backup' option and select the most recent file in that backup location.
I would suggest than less than 1% of ATI users ever use symbolic links in the way you are doing here..
If you really want to keep using a symbolic link, create a temporary location on your F: partition, i.e. F:\AcronisBackup\ then do as above to select this as the Destination for the backup task. Save the change then close the ATI GUI, then repeat the process to create the symbolic link by first deleting the F:\AcronisBackup\ folder, then using mklink /d F:\AcronisBackup\ D:\AcronisBackup\ as you did previously.
Repeating from my previous post:
I created the symbolic link on Drive F: but this version of Acronis appears to only give me options for destination that are in its list. And, it appears to only list folders and not shortcuts. I can't figure out how to enter a destination of my choosing
I use a symbolic link for the same reason Jim Rogers came up with it. Because I swap backup drives (they are always D:) and Acronis wants me to create a new backup each time.
Jim, swapping backup drives with ATI 2020 when using .tibx backup files will definitely present other issues due to the way the new file format works! With the older .tib files, you may get away with using symbolic links as you have with ATI 2016.
For the destination, you cannot select a symbolic link because ATI sees it for what it is, a hybrid form of shortcut to another location. This is why Jim Rogers outlined the approach he gave in his linked post, i.e. create a temp folder and point ATI to that, then close ATI, delete the temp folder, then create a symbolic link based on the destination used by ATI.
Personally, I would recommend creating separate backup tasks for each different backup drive you are switching between, then run the appropriate task when the correct drive is connected.
I had forgotten about needing to create, a temporary file, delete the temporary file, then create the symbolic link. This seems to be working. One thing, it's creating .tib files instead of .tibx files. So, what exactly is the advantage of .tibx? Also, where do I go to change this backup to .tibx?
Oh yes, and are .tibx files larger?
I would be surprised if this hack continues to work beyond the first run.
What now!!?? I thought I saw light at the end of the tunnel but as the saying goes "it was an oncoming diesel. "
When the backup started Windows said there was 390Gb of space free on the drive. About 40 minutes in to the backup Acronis threw the error there wasn't enough space on the drive and quit after saving 112Gb and leaving a partial backup on the drive. A typical backup with 2016 was 160Gb or less. And Windows now says there's 268Gb remaining after Acronis gave up.
I've now spent over 8 hours trying to make version 2020 work. Boy!!! Do I regret updating.
UPDATE: Windows now says the file is 158Gb which is the size of a 2016 complete update but I can't trust it.
Jim,
I suspect you running afoul of TI 2020 usage of metadata to track backup files. Your efforts to "fool" TI fail and the result is this hack fails to perform as expected.
My question to you is, why are you trying to break the application and cause it not to work as intended? Your requirement to use 2 alternate drives? Why can you not use a single task for each drive?
I deleted the unsuccessful backup and tried again. This time it completed successfully with the same 158Gb used. Which probably means the first backup was good but for some reason Acronis gave the failure message. This size is in line with the 2016 backups.
You figured it out. Changing the symbolic link to a drive other than C: was the answer. Thank you and thanks for bearing with me.
I would still like to know the advantage of .tibx? Also, how do I change this backup configuration to .tibx and are .tibx files larger than .tib?
You should test if the backup will run again a second time. You should also test if the backup(s) can be recovered.
Jim, ATI 2020 automatically creates .tibx files for new Disks & Partitions backup tasks but will continue using .tib files for such tasks brought forward from an earlier version.
It will continue making .tib files for all Files & Folders tasks as these have not been migrated to using .tibx yet.
So, if you want .tibx files for your Disk backup, then create a new backup task.
See my earlier post #4 above for lots of information about .tibx format files.
You should also test if the backup(s) can be recovered.
I have no way to do that. That's the problem with backup programs, you have no way to know if they will restore when the worst happens. I had another of these image making programs that I used for two years and when the crash came it didn't restore/failed.
See my earlier post #4 above for lots of information about .tibx format files.
Yes, I read through all that when you originally posted it. All I remember are weaknesses and disadvantages to .tibx format files. If there are any advantages they need to be listed somewhere.
FYI, most of the images in this are missing https://kb.acronis.com/node/63445
FYI, most of the images in this are missing https://kb.acronis.com/node/63445
For some strange reason this KB document (and some others) doesn't display correctly in Firefox browsers, but is fine when opened in MS Edge which shows exactly the same images as shown in Firefox but without the empty / broken image frames being shown!
I've tried to Create a New Topic (the same topic) 3 times. I get a message thanking me for posting a new Topic but it never appears. Can you figure out why?
Jim, I would suspect your new topics are being flagged for check by the moderator. If you have used any web links in them, or file attachments etc, this can happen.
No web links. No attachments. Just text
As a test I just now tried to create a Topic titled "issues"
The only content in it were the words "some issues"
The topic does not, did not post/appear
Jim, your posts are going into the Off Topic forum instead of here!
Thanks. I don't know how it decided they went in Off Topic, but at least I know my Topic got posted.
Thanks again for all your help.