Security Descriptor write errors
(This is a renewal of the same topic that I just accidentally deleted when trying to just delete an accidental copy of my initial text. As you can see I am a rookie here!)
A few weeks ago my TI2016 started to create write errors when writing incremental backups with system disk (SSD) as source and a mechanical hard drive as target. Same kind of "Security Descriptor" errors occurs regardless of target disk brand or full or additional incremental writes or MBR or GPT types. All disks are new, latest Windows 10 version, latest TI2016 version. All disks scanned OK for hardware errors with HD Tune (disktest).
These errors are detected with chkdsk run from Windows 10 graphic User Interface after rightclicked on diskname/Properties/Tools/Check. Result is "You don't need to scan drive, no errors found" - but clicking on Scan still reports these errors - I am attaching a typical chkdsk "scan-and-repair" log file here.
To confuse me even more, writing to an older hard drive performs OK.
Should I upgrade to Acronis TI2019 just to solve this or can there be some other solution/explanation to this? Since chkdsk always says "repaired OK" after these scans - is it safe to continue using Acronis TI2016 just as before, just adding this scan+repair after every backup? Is it even to consider an "error"?
Acronis backup software is an essential part in my business and when it fails it creates big risks for me. This is the worst IT-error I had for many, many years. I am really desperate to solve it!
Regards
Olof C,architect,Sweden
Attachment | Size |
---|---|
chkdsk-repairlog_systemSSD-to-1TB-HD,AcronisTI2016,WrErr-full-incr-tib-file.docx | 10.9 KB |


- Log in to post comments

Steve, thank you so much for the prompt and highly competent answer! I will now consider every word of it continuing to solve this problem. I will update on how it goes.
- Log in to post comments

Steve, as promised, here comes my report on my meticulous analysis of this issue. I have found a work around, a possible error source and have also posted this as a "feedback" to Acronis (since I have no support any more). What to you think about this? Details in the attached zip-file.
Attachment | Size |
---|---|
461537-152339.zip | 374.78 KB |
- Log in to post comments

Olof, thank you for the detailed investigation information documents.
I have run CHKDSK against 2 different drives where some of my backup files are stored (with files created from various recent ATI versions [2016, 2017, 2018 & 2019] of mixed full and incremental types) and did not find any security descriptor errors being reported or repaired. This was done on my Windows 10 laptop system.
It will be interesting to see if Acronis make any response to your Feedback submission.
One option that you may want to consider is downloading a 30-day trial copy of ATI 2019 and testing some backups from this system to see if you see any similar issues arising. With the trial software you would also be able to submit a support ticket during the 30-day trial.
Note: I would recommend making a full backup of your computer with ATI 2016 before installing ATI 2019 to give you a method of reverting back and keeping all your backup tasks intact. Otherwise you would need to do a clean install of ATI 2016 after removing the 2019 software.
- Log in to post comments

Steve, as before thank you for your lightning fast response and your very important advice that I will follow carefully. When you tell me about your non-erratic .tib files it makes me a bit confused but also a bit hopeful about ATI 2019, which I of course will test, considering what you say about this. If I ever come beyond my work around to a solid solution, I will report it back here.
- Log in to post comments