Backup SQL Always ON 2016 Basic Availiblity Group

[foggy]

Starting next update there will be no logs truncation for excluded databases.

[csmall]

The warnings about in the transaction log backup of the secondary node, are they just annoying or should I be concerned about them? In other words, is it cosmetic or is it an actual problem?

[foggy]

Hi Colin, do you mean logs truncation, not backup? It's not a problem, since you cannot truncate logs there anyway.

[csmall]

I think so, yes. I apologize for the confusion. We had an eventful morning related to the backup of a SQL Availability Group.

The job will warn that it can't truncate logs on the inactive node because it doesn't have read access etc..

We had a failover or two happen in the AG and the log backup job never seemed to recover from it. It just failed repeatedly to backup the logs of the one database in the AG and eventually seemed to stop trying. I'm hoping it resolves itself if I disable the job and re-enable it again.

Or maybe running an Active Full would help?

[foggy]

Depending on the actual error message you saw. It is better to verify with the support team, since we can just guess here. Typically issues caused by failover go away after the next parent job successful run.