Backup Failed
After running for a couple of months, Acronis True Image 2020 now fails. Message is: "Ensure the destination F:\ is accessible." F:\ is accessible under Win 10 ( I can write files to it with File Explorer.) and there is at least 2TB of room on it. What else should I do? I bought Acronis because of its reputation but so far it has been nothing but a hassle. Acronis needs to get out a product that is "set and forget" like Apple's "Time Machine" and I am no Apple fan.
Is drive F: still the same drive that has been used from the start for this backup task, or have you changed the drive with another one at any time?
Thanks for your help.
1. No changes to the back up routine. It ran out of room so I deleted the last backup(s) using the Acronis tool but no directory or drive change.
2. Backup fails both on scheduled run or manually triggered.
3. Same F:\ that it has used since day 1.
4. Here's the most recent log file:
2019-10-11 13:04:19: -----
2019-10-11 13:04:19: ATI Demon started. Version: 24.3.1.20770.
2019-10-11 13:04:20: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2019-10-11 13:04:20: Operation WCS-OFFICE-XPS started manually.
2019-10-11 13:04:20: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2019-10-11 13:04:20: Operation: Backup
2019-10-11 13:04:20: Priority changed to Low.
2019-10-11 13:28:12: Error 0xb042f: Destination is unavailable.
2019-10-11 13:28:13: Error 0x13c0005: Operation has completed with errors.
Start: 2019-10-11 13:04:19
Stop: 2019-10-11 13:28:13
Total Time: 00:23:
Brian, did the failures occur right after you did Step 1? How did you delete them? Have you tried to change the destination in the ATI UI (even to the same place), to see if that resets it?
I cannot recall for sure, but I believe the failure occurred the first time after I deleted the oldest backup to make room. The deletion was done from within ATI 2020 using one of the options under the drive in the left hand window.
Just tried resetting the destination to the same F:\ and restarted the backup. Same failure.
Brian, couple of things...
Please post the log again but from the Log View: Regular view of it which has more information about the error issue.
The log shows that the task has run for around 23 minutes before the error is thrown - how long does it normally run for, and what type of backup is this, i.e. disk & partitions backup, files & folders backup - and should the backup be making a full, incremental or differental backup at this time?
Finally, please try doing a validation of your backup task and see if that throws up errors?
1) Here's the expanded log file info:
2019-10-12 00:15:00: -07:00 10328 I00000000: -----
2019-10-12 00:15:00: -07:00 10328 I00000000: ATI Demon started. Version: 24.3.1.20770.
2019-10-12 00:15:00: -07:00 10328 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2019-10-12 00:15:00: -07:00 10328 I00640002: Operation WCS-OFFICE-XPS started by schedule.
2019-10-12 00:15:01: -07:00 10328 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2019-10-12 00:15:01: -07:00 10328 I013C0000: Operation: Backup
2019-10-12 00:15:01: -07:00 10328 I0064000B: Priority changed to Low.
2019-10-12 00:59:36: -07:00 10328 E000B042F: Error 0xb042f: Destination is unavailable.
| trace level: error
| line: 0x5d5406763c32a94
| file: c:\bs_hudson\workspace\1105\products\imager\archive\impl\operations\utils.cpp:582
| function: TrueImage::Archive::MakeDestinationUnavailableError
| line: 0x5d5406763c32a94, c:\bs_hudson\workspace\1105\products\imager\archive\impl\operations\utils.cpp:582, TrueImage::Archive::MakeDestinationUnavailableError
| Path: F:\
| StrId: \local\hd_ev\vol_guid(1C9060F711E986701E006596121DCD4C)
| $module: ti_demon_vs_20770
|
| error 0x2160015: A backup error.
| line: 0xa340ffd3416335cf
| file: e:\bs_hudson\workspace\mod-disk-backup\480\product\core\da_api\backup.cpp:353
| function: da_backup::Commit
| line: 0xa340ffd3416335cf, e:\bs_hudson\workspace\mod-disk-backup\480\product\core\da_api\backup.cpp:353, da_backup::Commit
| $module: disk_backup_vs_480
|
| error 0x29b138d: Input/output error
| line: 0x30ba355f9fd4ffbd
| file: e:\bs_hudson\workspace\mod-disk-backup\480\product\core\resizer\archive3\utils.cpp:364
| function: `anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc
| line: 0x30ba355f9fd4ffbd, e:\bs_hudson\workspace\mod-disk-backup\480\product\core\resizer\archive3\utils.cpp:364, `anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc
| function: archive_stream_write_shbuf
| path: \\?\F:\/WCS-OFFICE-XPS.tibx
| $module: disk_backup_vs_480
|
| error 0xfff0: Invalid access to memory location.
|
| line: 0x30ba355f9fd4ffbd
| file: e:\bs_hudson\workspace\mod-disk-backup\480\product\core\resizer\archive3\utils.cpp:364
| function: `anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc
| line: 0x30ba355f9fd4ffbd, e:\bs_hudson\workspace\mod-disk-backup\480\product\core\resizer\archive3\utils.cpp:364, `anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc
| function: pcs_co_file_readv
| path: \\?\F:\WCS-OFFICE-XPS-0004.tibx
| code: 0x800703e6
| $module: disk_backup_vs_480
2019-10-12 00:59:36: -07:00 10328 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bced6
| file: c:\bs_hudson\workspace\1105\products\imager\demon\main.cpp:736
| function: main
| line: 0x9f2c53c72e8bced6, c:\bs_hudson\workspace\1105\products\imager\demon\main.cpp:736, main
| $module: ti_demon_vs_20770
Start: 2019-10-12 00:15:00
Stop: 2019-10-12 00:59:36
Total Time: 00:44:36
2) I'm not sure how long it normally runs because I run it while I'm asleep.. Maybe 45 minutes?
3) The backup is an image backup of C:. It does a full then 6 incremental back ups then another full etc.
4) I don't know how to do a validation because none of the available back ups give me that option now.
Brian, this is a known problem that was fixed in the latest update build 21400 for ATI 2020 which you should update your application to from the older 20770 version.
See forum topic: Acronis True Image 2020 Update 1 is available! - and in particular for the error from your log: | error 0xfff0: Invalid access to memory location.
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."
The update seemed to work. It took 2.75 hours but said it only backed up 3.5 GB. However, it shows 790 GB as "data to recover" so I'm confused. I'm further confused by the fact that when I click on recovery, it says "there is no data to recover yet. Create your first backup to see its contents here".
Brian, I would recommend making a new backup task for this data and checking that that new task does work correctly. There may be some issues with the old task left over from the earlier build of ATI that the upgrade hasn't resolved. If the new task is good, then remove the old task settings to leave just the old files until you are sure you don't need them anymore.
Once again, you are correct. I made a new backup regime and manually started the backup. It appears to have run just fine (in 1 hr, 20 minutes) and got everything. The recovery tab shows what it should.
Hopefully now I'm back to being able to rely upon the backup system. All that remains is for Acronis to reinstall the feature that automatically deletes old back ups to make room instead of just quitting with a message.
All that remains is for Acronis to reinstall the feature that automatically deletes old back ups to make room instead of just quitting with a message.
Brian, automatic cleanup is working just fine for me for managing my backups and pruning the oldest when the cleanup rules say they should.
Cleanup works on completed version chains and only deletes old chains after a new chain has been started by a new full backup file.
OK, maybe that feature was reinstalled in the latest update. Last time I checked with Acronis, I was told that feature had been eliminated in ATI2020.
This is an ATI 2020 topic in the ATI 2019 forum. Is it possible to move it to the 2020 forum? Ekaterina?
BrunoC wrote:This is an ATI 2020 topic in the ATI 2019 forum. Is it possible to move it to the 2020 forum? Ekaterina?
Moved the topic to the correct forum, thank you!
Brian Weeks wrote:OK, maybe that feature was reinstalled in the latest update. Last time I checked with Acronis, I was told that feature had been eliminated in ATI2020.
I'm not following this. What feature? There were some bugs in cleanup (at least in the Beta test) and maybe some features that weren't included in the initial GA release but were fixed/added in the later updates. Is that what you mean?
The underlying mechanics of cleanup may have changed a bit with the .tibx support, and cleanup based on backup size has been eliminated, but the basic cleanup philosophy as outlined by Steve has not changed.
Here's the link to the earlier discussion. See the end posts....
https://forum.acronis.com/forum/acronis-true-image-2020-forum/seems-dum…
Brian, you need to use the available automatic cleanup options rather than those which are no longer shown due to the changes introduced by Acronis with the new .tibx format backups.
Those other cleanup options will help you to manage your backup size and delete older version chains to avoid getting to a full disk issue.
Personally, I have never used the "Keep size of the backup no more than [defined size]" option, so I hadn't noticed that it was no longer offered for .tibx tasks.