I've sett up a backup job of a AO SQL cluster. I followed documentation and everything went smooth.
Backup job runs well and backup copy works to.
I get just one warning, doesn't seem dangerous but I don't like unsolved warnings

It says that on my secondary node the job is unable to truncate the logs. I've been searching and found some good post's but non seem to answer my question.
I read it like that it's normal that the secondary node log isn't truncated, no problem but way is it trying? can I exclude it from the secondary node? Are the logs on the secondary node truncated in any way?
My setup is to virtualized windows 2016 servers that run inside a Hyper-V cluster I use SQL 2017 or version nr 14.0.2027.2
I greatly appreciate any comments that sheds some light
Regards Rene