Help Understanding huge discrepancy in LDF file growth on AAG between primary and secondary
carriann last edited by
I currently have a SQL Server 2014 instance with a very basic AAG setup. There are 2 nodes in the AG. The Log drive on the primary has 90% free space, and the log drive on the secondary has 5% free space. I guess the 2 questions I have are:
- Shouldn't they always be more or less the same size since they are synchronized?
- How can I shrink the log size on the secondary without making it the primary first?
Is there a way to accomplish the second one without doing a manual failover, making it the primary then doing all the work? How can i prevent this massive size discrepancy in the future or is this just to be expected? Thanks in advance for any help.
jeanid last edited by
As it turns out the drive was misreporting space used. The LDF files on the primary totaled 151GB used, after analysis it matched exactly with the secondary. The real issue was the secondary needed chkdsk run on it. once complete, it accurately reflected the used space.