TakeOwn forces "full" file backups instead of incremental file backups

This almost drove me crazy and I already had doubts about all kinds of settings and configurations. So I’m glad that I can now share my experiences here.

The problem was that in one of my setups, very large amounts of data were transferred over and over again, even though the setup was based on one that was already working. But I actually wanted to force a purely incremental data backup. But copying all the data always took days and so I always had a copy process running.

Later I noticed that with hourly incremental backups, sometimes a few backups were carried out correctly in the evening, in just a few minutes and really incrementally. But later there was another full backup at night, which again blocked everything for days. Despite this, the data didn’t seem to have been stored duplicated on the server, so it seemed somehow strange why it was transferring data only to find that it was unchanged anyway.

Long story short:
I have now found out that a recursive script was executed in the early hours of the morning in which ownership of all data on the Windows client was taken over.
The command was:

takeown /f “d:\data” /r

I can now say that this command causes urBackup to lose the connection between data and the backup server and automatically re-transfer all data (as if it were a full backup).

I have now deactivated the script for the time being.
However, I would not have expected this behavior, that a change in file ownership automatically leads to a new transfer of the file.

Is this a bug in the software? I would think so but maybe I miss something?