[ISSUE] Backup glitches after upgrading from Windows 10 14393 to 15063
ATIH 2017 (NG) b6106, or other ATIH 2016 / 2017 releases
On my installations and also out in the field (I've successfully migrated more than 25 computers to 15063) I am experiencing recurring issues with ATIH 2016, 2017 and 2017 NG of either version.
Problem:
Existing and planned Backup jobs will fail and ATIH states that it fails to find the backup target. A manual validation is running fine. though.
Physically the target has the same drive letter (I tend to assign backup target to letter B: so they dont move around in any case)
In rare conditions I have had issues with authentication like we already had in 2016 b5555. Also the authentication fails when entering the credentials another time.
Workaround:
All issues could get solved by editing the job and defining the source and backup targets anew, either for attached backup targets or network. Aswell as setting up the credentials another time.
Question:
May I suspect that these issue were the reason for the "Creators Update" releated patches for 2016 and 2017 (NG)?


- Log in to post comments

That sounds reasonable Rob. Thanks! At least on my system there is nothing like a second recovery partition, but due to amount of upgrades I've done I have already spotted this behaviour, if the recovery was too small. Whats 450 MB anyway on todays SSDs /ironic.
DISKPART> lis disk
Datenträger ### Status Größe Frei Dyn GPT
--------------- ------------- ------- ------- --- ---
Datenträger 0 Online 465 GB 0 B *
Datenträger 1 Online 465 GB 0 B *
ISKPART> sel dis 0
Datenträger 0 ist jetzt der gewählte Datenträger.
DISKPART> lis part
Partition ### Typ Größe Offset
------------- ---------------- ------- -------
Partition 1 Reserviert 128 MB 17 KB
Partition 2 Wiederherstellun 450 MB 129 MB
Partition 3 System 100 MB 579 MB
Partition 4 Primär 465 GB 679 MB
- Log in to post comments

I still wonder what was the reason for the reprise of the authentication issue, but since I was able to fix it, I better don't bother about that.
- Log in to post comments

Yeah, mine ended up being 509 MB - no idea what caused the increase here. I nuked the original one and reclaimed the space back to partition 3 and made sure the new recovery was working OK though. Hopefully the authentication issues get ironed out soon. Better to leave well enough alone if it's working though :)
DISKPART> list partition
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Reserved 128 MB 17 KB
Partition 2 System 100 MB 130 MB
Partition 3 Primary 217 GB 230 MB
Partition 4 Recovery 509 MB 217 GB
- Log in to post comments

Hello Karl,
If the authentication keeps failing, the logs for investigation could be obtained and send to us this way:
1) change the value of HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Acronis\TrueImageHome\Settings\TraceLevel from the default 2 to 0 (zero)
2) close True Image, if it is running
3) start capturing PCAP log
4) reproduce the problem, take a screenshot of the authentication error message
5) save PCAP log
6) use "Send feedback" feature in the program, keep the checkbox for system report marked and attach the pcap log, attach the screenshot and submit the feedback form. Alternatively, you can always submit a ticket normally.
Regards,
Slava
- Log in to post comments

Hello Slava, thanks for the detailed instructions I will keep them in mind as the problem with the authentication issue was never reproducible again.
- Log in to post comments