The issue is an internal Exchange 2016 tracing logs that are recording Exchange functionality itself. These logs are completely different from Exchange databases' log files and not affected by backup log truncation tasks.
Please review 3rd party sources on how to maintain Exchange 2013/2016 logging. For example:
https://collaborationpro.com/exchange-2013-logging/
https://shanejacksonitpro.wordpress.com/tag/exchange-2016-logs/
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center