Error:
The transaction log for database ***** is full due to ‘AVAILABILITY_REPLICA’
Cause:
This occurs when the logged changes at primary replica are not yet hardened on the secondary replica.
Fix:
Make sure Always On setup is working properly.
Start the SQL services on secondary replica server and resume data movement for the always on availability groups databases. The databases should catch up and after they do and log backups log files will free up space and return to normal.
Sources:
Comments