I have a database sitting on a 2016 Standard clustered MSSQL Server configured with asynchronous replication via an availability group to a standalone instance.
The database is not being used so there is no changes being made to the database at all.
Over the weekend the log file grew from 0 MB (when i set up the AG) to 450GB all without any transactions being carried out by users. I'm guessing SQL is doing something in the background and is maybe getting stuck and looping causing this growth.
How can i diagnose/stop this?
Any help greatly appreciated as my disk space is going to run out!
Yesterday, i managed to shrink the file to 4MB by doing a log backup, shrinking the file and restarting the SQL services. I've come in this morning and the log is now 3GB without any users creating transactions.