Event code: 0x01E50013+0x01E50018+0x000B041D+0x00040011+0x0000FFF0+0x80070002
I had the other day on TI2016, but doing Retry it continued and in the end there was _v30 in the the last file. TI2016 was freshly installed, after doing the cleanup thingy and uninstall before some weeks ago. I was puzzled since I never got a license dialog to enter - but figured that is still in registry then. Yesterday I started getting this with Seagate Disc Wizard as well. I could do backup to a second internal disk - and then copy to backup disk - that works ok. So looking at possible disk failures - but cannot find any. I can copy any range of data with xcopy or similar. And it is always at 5% or so at the very end of backup - never earlier - and Acronis says successful backup? Backup drive is a Seagate 2 TB usb 2 disk, and ran Disk Wizard for 6-7 years without any such message.. What is this, and what does it mean? Is it an error ? I think both DiskWizard and TI2016 goes to same folder even My Backups - something that one writes that the other does not like? I running a full disc scan on external drive now to be safe. Thanks.
Hi, and thank you for commenting.
No, Seagate is removed, I hope by now, on the computer running TI2016(had to go through registry for that).
There were a bunch of things not covered by CleanupTool - maybe that would be a good option if it did cleanup that Seagate as well. I imagine common to startup with DiskWizard the migrating to full version.
It seems to be related to what was suggested in KB - saying files were removed manually.
For purposes not reaching a full disk I did remove files - and remark and even error was over files not there anymore. Very confusing making such a fuzz over files obviously not needed doing full backups on DiskWizard.
So event code were generated over _b12_ and _b09_ when last backup just made was _b14_. And still saying backup was successful - and bothering you with these confusing messages saying it might be corrupt.
Not sure if I entered something with cleanup stuff - and should avoid that in future.
So easiest workaround was to remove all backup files and the job as well, and start over from scratch. Then I had it go through without any strange messages.
So cleanup all jobs - and be sure not to enter keeping extra copies or things like that and see if I can manage this cleanup by myself when disk might be full next time without software interfering.
The real issue I'm not sure what happend was that before this backup on TI2016, incremental one, it kept throwing up dialogs to retry, also some unable to open file, in between so it could not continue unattended. Some files were zero size and some had a couple of 100MB in them. Alltogether _v12 in the last one written.
But this went through ok removing that job and took some 12-13 hours or so doing backup. I was online at the time, so not sure if TI2016 do things over network that create problems. If this comes back with TI2016 I revert to use xcopy /d instead. So much fuzz using TI, I think.
Lars, thanks for the update, and good that you look to have got things cleaned up and have been able to make a new backup.
One thing to consider before going back to using xcopy /d is that this will only be good when copying files & folders - if you have a disk crash, you cannot recover the Windows OS from this type of copy backup.
Hi again, and thank you.
Even though a valid point, that xcopy won't even copy some open OS files probably - I plan to do clean install anyway if disk goes to the cleaners.
Lots of authorizing of various software I have based on that very disk identify and such - just as well do clean install of everything.
I feel less and less in control with TI - and don't like it.
Simplicity of xcopy and just mirroring feels more and more attractive.
Maybe have a look at task scheduler in Windows - and how that tells you - last run, next run etc.
I had TI2016 uninstalled for two years due to it refused to let me shut down computer because it had things to do I was not aware of. I think I made mistake not seeing that default was to schedule job daily or something. This is what I mean by - not in control. I have no clue what is pending.
If it as now tell - last run - but also - next run: manual then you know you didn't configure anything. Or telling when if you did. And for some reason to schedule or not - is not part of default settings you could exclude, so you have to remember turning that off on every job you create.
Lars, you may want to take a look at the changes that Acronis have introduced with ATI 2018 & 2019 versions, where there is a lot more information provided in the main ATI GUI dealing with the activity for any backup task.
The above is for one of my backups going to a NAS drive but which I do not schedule via the normal Acronis scheduler process. I run this via the Windows Task Scheduler instead using a Powershell script that does some checks to make sure I am connected to my network first!
Thank you.
Still think Windows Task Scheduler fields are more important - next run - as one.
If it says manual you know you did not do schedule, or it says when is next - good stuff.
Anyway, ran into serious issues trying to uninstall - posted in TI 2016 forum.
I could not make restore point or anything regarding volume shadow copy.
Three days I tried to figure out - and in the end just reinstalled TI2016 - and then it worked.
So something remains from Acronis that ruins functionality in system it seems.
Still think Windows Task Scheduler fields are more important - next run - as one.
If it says manual you know you did not do schedule, or it says when is next - good stuff.
Lars, this information is still present but just moved around a bit..!
