After upgrading from 2019 to 2020 >Backup failed> drive not accessable
Version 2019 was working fine.. I liked the product so i thought i would upgrade to version 2020. It seems that there is a bug in this version. I uninstalled and reinstalled twice. Taked with a tech on the support chat and said perhaps I have a ram problem. I dont have a ram problem, this computer is brand new and a monster... it has no problems at all.
I am a tech as well but this problem is specific to acronis.
So i get the backup failed message. I tried 2 different drives, one was new and freshly formated. All of them are external drives.
I have been a customer since version 10 of acronis and have upgraded almost to all newer versions. This is the first time I have had any problems with it.
I also updated by drivers to the newest one.
I have an OMEN laptop with windows 10 pro 64 bit and im trying to back up to external hard drives formated as NTFS.
Any help would be appreciated.
See attached screenshot.
Fichier attaché | Taille |
---|---|
Annotation 2019-09-08 120331.jpg | 186.6 Ko |


- Se connecter pour poster des commentaires

Your screenshot shows two backup files. The first shows to be 397.9GB the last 539.6GB. Did both of these backups fail or just the last one? Can you post a screenshot of the the Activity tab for the backup so that we can see more details?
Can you open the backup files in Explorer by double clicking on them? If you right click on each backup file and select Validate will that process run to completion and what are the results?
To run validation you might need to acknowledge a UAC warning then, hover over Acronis True Image, select Validate.
- Se connecter pour poster des commentaires

It looks like the 539GB .tib was done by ATI 2019 and was successful. The 398GB .tibx was done by ATI 2020 and failed.
We know that ATI 2020 will continue a .tib chain as .tib files. In this case, it appears as though the backup task is possibly defined as a new Full each time (cleanup?), so rather than produce the next Full as a .tib it went with the new .tibx.
Or, was the task recreated with ATI 2020?
- Se connecter pour poster des commentaires

Thank you guys for the follow up. that screenshot was on my other drive which I did use for acronis 2019. But as I said in my post I tried with even with a new and newly formated drive and it failed again.
I cannot open the archive after its done even though it showed that it was creating a file.
In the log file of the backup worker I found this> image backup: failed to close archive
This is for SURE a bug within acronis 2020 no doubt about it... lol
But im running a validation as Enchantech proposed.
and doing a windows memory diagnostic test...
Also this acronis version is annoyingly slow to load and do things even on my i7-8750H with nvme and ssd drives... with 32 gigs of ram ...
lol
- Se connecter pour poster des commentaires

I used the log file viewer tool that Steve Smith has kindly provided in his signature.. and here is what it gave me>
9/9/2019 8:18:46 AM: -----
9/9/2019 8:18:46 AM: ATI Demon started. Version: 24.3.1.20770.
9/9/2019 8:18:46 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/9/2019 8:18:46 AM: Operation LAPTOP-OMEN started manually.
9/9/2019 8:18:49 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/9/2019 8:18:49 AM: Operation: Backup
9/9/2019 8:18:49 AM: Priority changed to Low.
9/9/2019 9:28:42 AM: Error 0xb042f: Destination is unavailable.
9/9/2019 9:28:42 AM: Error 0x13c0005: Operation has completed with errors.
Start: 9/9/2019 8:18:46 AM
Stop: 9/9/2019 9:28:42 AM
Total Time: 01:09:56
- Se connecter pour poster des commentaires

From reading further into what steve said about a known problem with acronis 2020, im sure that this is the issue. Like here>
Folks, a couple of comments here.
The ti_demon logs for new .tibx backup tasks only contains an overview of what is happening, not all the full details - the latter is held in the backup_worker logs for .tibx backup tasks!
Dean, your issue looks to be the same as forum topic: Large backups fail at around 900gb - created by user Patrick where the core issue seems to be around a memory issue, which in turn begs a question as to whether ATI 2020 is using memory more intensively for new .tibx tasks?
error 0xfff0: Invalid access to memory location. (from Dean's update above).
Karl, your issue scenario looks to be complex to say the least.. I doubt that I would be able to get near to trying to recreate such a scenario. I have never used my NAS as the source for any tasks and currently only have one laptop running ATI 2020 #20600 public release. My other computers are running a mix of ATI 2019 and 2018.
- Se connecter pour poster des commentaires

Interesting, looking forward to the results of validation.
- Se connecter pour poster des commentaires

Enchantech! The backup is valid.. lol Gofigure..
So now what?
It seems like it was working and the very end it would fail saying its not accessible.. but if its writing gigabytes of data then how is it not accessible.
Im thinking of ditching it and going back to 2019... what do you guys think?
- Se connecter pour poster des commentaires

Since validation passed then I think the backup would restore fine. Would you have an extra drive that you could restore to and find out?
This error has plagued a number of users. I have not experienced it myself but then my backups are no where near 500+GB either.
Whether or not to revert to 2019 is up to you. Personally I would not. If you can restore the backup file to another disk and prove that successful then I believe the application developers would be very interested in that!
- Se connecter pour poster des commentaires

I have approximately 540 gb to back up and it wont even start before saying the drive is not accessable. It is a brand new Seagate 2tb portable usb drive, freshly formatted. I was able to write and read from the drive.
Fichier attaché | Taille |
---|---|
512714-172350.JPG | 76.05 Ko |
- Se connecter pour poster des commentaires

Ralph, welcome to these public User Forums.
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 a problem here?
Without more detailed information it is impossible to say if you are seeing any of the issues referred to in this topic.
- Se connecter pour poster des commentaires

KUser wrote:Enchantech! The backup is valid.. lol Gofigure..
So now what?
It seems like it was working and the very end it would fail saying its not accessible.. but if its writing gigabytes of data then how is it not accessible.
Im thinking of ditching it and going back to 2019... what do you guys think?
>>
Since 2019 was working well for you, why not revert to that and than retry the 2020 upgrade in a few months with some of the bugs are worked out? 2020 seems to have been a larger than usual jump in terms of new file formats and added code, so it may take some time for it to be as reliable as 2019. It's also not yet feature complete in that certain functions from 2019 are currently not available for the new TIBX file format but are planned in the near future.
Given that the new TIBX format has been updated for better overall reliability, especially in validation, I'd expect 2020 be a better choice once fully patched.
For my part, I'm staying on 2019 for now since it works perfectly for me and the backup/restore code is bullet proof. I look forward to moving to 2020 once it's had some more time in the oven.
Best of luck,
Philip.
- Se connecter pour poster des commentaires

The backup passing validation indicates that a recovery of the backup would work. I wondering if in your case the error is false. Possibly others getting the error are also false. Until someone whom has this issue attempts a restore and that effort fails I believe I will consider it a false positive.
- Se connecter pour poster des commentaires

it's not letting me upload a log file.....
copy and paste
9/8/2019 22:27:48: -----
9/8/2019 22:27:48: ATI Demon started. Version: 24.3.1.20770.
9/8/2019 22:27:49: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/8/2019 22:27:49: Operation My partitions started manually.
9/8/2019 22:27:49: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
9/8/2019 22:27:49: Operation: Backup
9/8/2019 22:27:49: Priority changed to Low.
9/9/2019 3:22:37: Error 0xb042f: Destination is unavailable.
9/9/2019 3:22:38: Error 0x13c0005: Operation has completed with errors.
Start: 9/8/2019 22:27:48
Stop: 9/9/2019 3:22:38
Total Time: 04:54:50
no file was written to the disk
- Se connecter pour poster des commentaires

Ralph, just looking at the time your backup task was running for suggests that you are hitting the known issue with backups of large volumes of data, i.e. over 500GB as documented in forum topic: Large backups fail at around 900gb (the size in the topic title was the size that the original poster hit the problem at, but other users have reported the same with sizes ranging from 500GB up).
There is no fix for this issue at this time other than either reverting back to ATI 2019, or else if the backup is not of your Windows OS drive, you can use a Files & Folders type backup which doesn't have this problem, or you would need to split your backup source into smaller pieces.
- Se connecter pour poster des commentaires

The new update that just came out (sept 24th) Build 21400 has fixed these issues...
See changelog here https://www.acronis.com/en-us/support/updates/changes.html?p=42014
and>>>
Acronis True Image 2020 Update 1 for Windows
What's new
- Added support for the Windows 10 September 2019 Update
- Bug fixes and other improvements
Fixed issues
- TI-173951 Login to Acronis True Image fails if the "Go Daddy" certificate's chain on the machine is incomplete.
- TI-168095 Cloud Entire PC backups are empty if browsed from mobile applications.
- TI-174833 Disk backup fails with the error "No Volsnap driver was found."
- TI-173964 The "Unable to copy the product files" error appears during Acronis Survival Kit creation to USB flash drives formatted to GPT.
- TI-174635 Backup to Acronis Cloud fails with the error "Acronis Cloud is full."
- TI-173934 Disk-level backup to an external drive fails with the error "Invalid access to memory location."
Known issues and limitations of this version
- Please note that new technology for disk-level backup is introduced in Acronis True Image and is being improved, so it may currently have the following limitations:
- TI-169821 Backup conversion to VHD format is not present for the new backup format.
- TI-171553 Moving the backup through the Acronis True Image console is not present for the new backup format.
- TI-169548 Renaming local backups is not possible for the new backup format.
- TI-172340 The backup mounting option is not present for the new backup format.
- TI-172086 A differential backup is created instead of full backup, after the second launch of a local disk backup using the "Version chain" scheme.
- TI-168969 Acronis Universal Restore cannot detect external USB drives.
System requirements
Hardware requirements:
- A CPU that supports SSE instructions
Operating systems:
- Windows 10 (all editions, including September 2019 Update, except for Windows IoT editions)
- Windows 8.1 (except for Windows Embedded editions)
- Windows 8 (except for Windows Embedded editions)
- Windows 7 SP1 (all editions)
- Windows Home Server 2011
It is possible for the software to work on other Windows operating systems, but it is not guaranteed.
File systems:
- NTFS
- Ext2/Ext3/Ext4
- ReiserFS(3)
- Linux SWAP
- HFS+**/HFSX
- FAT16/32/exFAT*
Storage media:
- Internal hard disk drives
- External hard disk drives with any of the following interfaces: USB (including USB 3.0), eSATA, FireWire (IEEE-1394), and SCSI
- Solid State Drives (SSD)
- Networked storage devices
- Se connecter pour poster des commentaires

Kuser,
I take it that means you no longer are experiencing the discussed behavior? That's very good to hear!
- Se connecter pour poster des commentaires

Yep Enchantech , the issue was solved by this update. Actually Acronis support had told me (but not right away.. lol) that it was a known issue and they would be fixing it on the next update.
So im sharing this info in case others download the older version or have the older version. the bug was squished in Build 21400 (sep 24th)
- Se connecter pour poster des commentaires

Great to hear, I saw your post to the other thread on this as well.
- Se connecter pour poster des commentaires