The culprit has been found even tho they lied to me back in August. Acronis True Image 2019 and 2018 for Mac creates these files. Acronis, currently, is seemingly not willing to commit or respond to this. It has been proved that the kext fileprotector (part of Acronis) creates atpstatdb00.db at boot time. It is created at about 825 bites in size. If you have Active Protection enabled as soon as Acronis True Image is loaded, a second file (atpstatdb14.db) is created. Now both files become atpstatdb00.db at @483gb and atpstatdb14.db at @69gb. Disabling Active Protection will cause Acronis True Image to not create the second file however the first file still gets created. Even so there is a bug in fileprotector as it creates a massive load of console messages and continue to interrupt file accesses. The only safe thing to do is remove Acronis True Image altogether. Note: there is nothing wrong with their backup portion as it works just fine. Since they seemed to have invested much into Active Protection, they don't seem to be eager to acknowledge the issues.
Acronis True Image under windows is a slightly different story as it does not seem to create the same files and is a service which is dependent on a Microsoft Crypto service. You can disable the Active Protection service but in my testing I have not found issues except maybe in performance to a degree as it does still consume more heavily than other services.
Uninstalling and removing the mac version of Acronis True Image 2019 or 2018 does not always remove these atp* files so you may have to remove them and double check on each boot for a few times to make sure they are gone. If you continue to use Acronis True Image for backups (like I do) disabling Active Protection is the only option but in most cases the first file will still be created and fileprotector as kext will still be there. I have not tried to remove the kext file to ensure fileprotector was not on line and working.
Reach out and ask Acronis to do something about this. I fully understand the need or use of Active Protection but they did not technology think this through and did not implement this part well on Mac. It does affect High Sierra and Mojave.
Now in all of this your mileage may vary. I would suggest reaching out to them about this; please be careful as they seem to use a rotating auto attendance for their support tickets - based on the responses I got, it seems the attendant was just extrapolating from my ticket and giving me silly things to do that I did not ask - even tho the attendant did have a name.
But Acronis created these problems on mac but as of yet fail to respond. No one will have issues if your destination drive is huge - probably never notice it until they get close to running out space. In my case, my hard drive is 121gb and my destination is 1TB but with these silly files, I can fit only 1 backup and a bit before I run out of space. With these files, each backup is close to or above 600GB. What a waste of time and effort. If your system is super fast and you have a ton of memory, you also might not notice the fileprotector issue with. All hiding behind the scenes.
