Skip to main content

anyone else have to remove and reinstall every 2-3 backups?

Thread needs solution
Forum Member
Posts: 12
Comments: 35

this program seems to self-destruct every 2-3 backup cycles. it begins with logging bogus errors which take forever to track down and verify, and the logs for the most part cannot be deciphered. then it ceases sending notifications creating unneeded sifting to see if the backups were or were not started and completed. last the monitor fails to start.
to fix it, a complete uninstall / reinstall is required and recreation of all your backups. 2-3 hours if all goes well.
fix it and regret it, as the process will repeat itself. this has been going on for several months now, and nothing seems to be able to keep acronis intact on any of my 3 win10 machines, this problem does not occur on my server or win7 machine.

here is an example of a logged error that acronis has never responded to or acknowleged

id=20; date/time=10/2/2019 1:20:34 PM; message=Consolidate Backup Archive Location: Q:\vega\C and D Vega_diff_b11_s5_v1.tib Destination: Q:\vega\C and D Vega_diff_b11_s5_v1_37C9681B-1B7F-472D-A0A8-8CEC79023BB7.tib
Error_Code=AQ4A5QHMRaELzE1bbTxib2xkPkNvbnNvbGlkYXRlIEJhY2t1cCBBcmNoaXZlPC9ib2xkPjxlbmRsLz48dGFicG9pbnQgdmFsdWU9MzA+PGluZGVudCB2YWx1ZT00PkxvY2F0aW9uOgk8aW5kZW50IHZhbHVlPTEwPjx0ZXh0Y29sb3IgdmFsdWU9Im5hdnlibHVlIj4iUTpcdmVnYVxDIGFuZCBEIFZlZ2FfZGlmZl9iMTFfczVfdjEudGliIjwvdGV4dGNvbG9yPjwvaW5kZW50PjxpbmRlbnQgdmFsdWU9ND48ZW5kbC8+RGVzdGluYXRpb246CTxpbmRlbnQgdmFsdWU9MTA+PHRleHRjb2xvciB2YWx1ZT0ibmF2eWJsdWUiPiJROlx2ZWdhXEMgYW5kIEQgVmVnYV9kaWZmX2IxMV9zNV92MV8zN0M5NjgxQi0xQjdGLTQ3MkQtQTBBOC04Q0VDNzkwMjNCQjcudGliIjwvdGV4dGNvbG9yPjwvaW5kZW50PjxpbmRlbnQgdmFsdWU9ND48ZW5kbC8+PC9pbmRlbnQ+PGVuZGwvPgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTk1ACRmaWxlAEFrOlw2NTk1XHByb2R1Y3RzXGltYWdlclxhcmNoaXZlXGltcGxcb3BlcmF0aW9uc1xhcmNoaXZlX29wZXJhdGlvbl9jbG9uZS5jcHAAJGZ1bmMAQVRydWVJbWFnZTo6QXJjaGl2ZTo6Q2xvbmVBcmNoaXZlT3BlcmF0aW9uSW1wbDo6UHJlcGFyZQAkbGluZQBOzgcAAAAAAAAABwQLAMxFoQvMTVttPGJvbGQ+Q29uc29saWRhdGUgQmFja3VwIEFyY2hpdmU8L2JvbGQ+PGVuZGwvPjx0YWJwb2ludCB2YWx1ZT0zMD48aW5kZW50IHZhbHVlPTQ+TG9jYXRpb246CTxpbmRlbnQgdmFsdWU9MTA+PHRleHRjb2xvciB2YWx1ZT0ibmF2eWJsdWUiPiJROlx2ZWdhXEMgYW5kIEQgVmVnYV9kaWZmX2IxMV9zNV92MS50aWIiPC90ZXh0Y29sb3I+PC9pbmRlbnQ+PGluZGVudCB2YWx1ZT00PjxlbmRsLz5EZXN0aW5hdGlvbjoJPGluZGVudCB2YWx1ZT0xMD48dGV4dGNvbG9yIHZhbHVlPSJuYXZ5Ymx1ZSI+IlE6XHZlZ2FcQyBhbmQgRCBWZWdhX2RpZmZfYjExX3M1X3YxXzM3Qzk2ODFCLTFCN0YtNDcyRC1BMEE4LThDRUM3OTAyM0JCNy50aWIiPC90ZXh0Y29sb3I+PC9pbmRlbnQ+PGluZGVudCB2YWx1ZT00PjxlbmRsLz48L2luZGVudD48ZW5kbC8+ACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1OTUAJGZpbGUAQWs6XDY1OTVccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFxvcGVyYXRpb25zXGFyY2hpdmVfb3BlcmF0aW9uX2Nsb25lLmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpBcmNoaXZlOjpDbG9uZUFyY2hpdmVPcGVyYXRpb25JbXBsOjpQcmVwYXJlACRsaW5lAE7OBwAAAAAAAAA=

try tracking a dozen or so of these down a week! yes all that gibberish is in the log as a single error.

my backup drives and working drives are all verified error free. I have lost confidence in the integrity of my backups, and do not have the time to try restoring them on spare drive to verify.

enough of my rant ........ anyone using an alternative backup solution that is reliable.

0 Users found this helpful
Legend
Posts: 81
Comments: 17944

#1

Vega, I have never encountered any problems with any version of ATI that I have used such as you have described in this topic.

The error code you provided (in Base64 code format) simply shows that there was a problem during automatic cleanup (shown as Consolidation in the log) for some reason.

id=20; date/time=10/2/2019 1:20:34 PM; message=Consolidate Backup Archive Location: Q:\vega\C and D Vega_diff_b11_s5_v1.tib Destination: Q:\vega\C and D Vega_diff_b11_s5_v1_37C9681B-1B7F-472D-A0A8-8CEC79023BB7.tib
Error_Code= Consolidate Backup Archive
Location: Q:\vega\C and D Vega_diff_b11_s5_v1.tib
Destination: Q:\vega\C and D Vega_diff_b11_s5_v1_37C9681B-1B7F-472D-A0A8-8CEC79023BB7.tib
$module Ati_demon_vs_6595
$file k:\6595\products\imager\archive\impl\operations\archive_operation_clone.cpp
$func ATrueImage::Archive::CloneArchiveOperationImpl::Prepare

The most common reason for 'Consolidation' errors are when backup .tib files are deleted outside of ATI using Explorer.

Forum Member
Posts: 12
Comments: 35

#2

thanks again Steve,

the only time back up files are deleted is by the auto consolidation by acronis. but for the last several months the bigger problem is the program literally consuming itself, notifications cease, the monitor stops running, then the scheduler fails. I have literally uninstalled and reinstalled acronis on my win10 machines 7 times each now.

today I'm at the last stage, 2 of the pc scheduler has failed, even though the process is running.

Forum Star
Posts: 131
Comments: 2942

#3

May I suggest that you try the ATI 2020 trial version to see if you get the same problem. Before doing so you will need to uninstall ATI 2016 and then install 2020. The native backup for 2020 use *.tibx rather than *.tib files, however, you can still run backups created with earlier versions. As 2016 cannot read 2020 backups it would be a good idea to backup you backups to a separate drive. Once ATI 2020 is installed, you can import the existing backup using add backup. You will need to reconfigure the backup before running it.

Ian

Forum Member
Posts: 12
Comments: 35

#4

all 3 win10 pc's failed to backup today. no messages, nothing in the logs, just skipped over the backups and scheduled tomorrows.

time to find another solution, in the mean time I'll have to manually initiate the backups daily.

thanks to Steve and Ian for the replies and suggestions