duplicate

Make sure your server properties/database settings/database default locations are set to the drives you expect them to be.

Bummer, I figured mine was a fluke.  Thanks for the update.

I hear you on the licensing...mine is SPLA so it is very expensive to bump up.

I applied CU21 late in July.  I had my first restarts this last weekend and both my nodes came up clean with no secondary out of sync issues.   Have you...

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

This usually points to Kerberos double hop issues.  Check you SPN's.

You can use this tool to check it:  https://www.microsoft.com/en-US/download/details.aspx?id=39046

<sigh>  Thanks for the update.

I can confirm I also get some out of sync even though both nodes are on the same patch level.

I'm not 100% sure, but check out Erik Darling's sp_HumanEvents.

I believe you can filter by db and username and log to a table.

The log backup doesn't align with my AG either.

Ooops, I see you already commented on our similar post

It does sound similar.  I just moved from CU18 to CU19 and am waiting to see if it helped. I am thinking about switching off auto seed before the next...

• Same, I have auto seed on and most of the time I have some db's that get out of sync.  Like about 15-20 out of 170 db's need manually...

Same here, mine were fine for a few years before this issue started about 6 months ago.

I also started to experience this about 6 months ago, I wonder if an SP introduced the issue.  I had over 300 tiny databases in my AG.  I've reduced it...

You might try DBCC Updateusage.

I've had to run that coming off some old servers to fix performance issues if it seems storage is your related wait types.

https://learn.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-updateusage-transact-sql?view=sql-server-ver16

Have you reviewed the queries involved in the deadlocks?

Perhaps you are under -indexed or over-indexed.  Maybe the queries can be tuned to hit the tables more efficiently (and same order).