We initially had a 3 node SQLServer 2012 AAG (Primary1, Secondary2 and DR1) at our DataCenter . In the process of migrating to a new data center at a different physical location, we set up 3 more nodes and evicted the DR node and added the new set of 3 replicas (Secondary3, Secondary4 and DR2).
Here is a summary:
Already Existing: Primary1, Secondary2 and DR1 in the AAG
New Nodes: Secondary3, Secondary4 and DR2
Added Replicas: Secondary3, Secondary4 to the AAG
Changed Primary Replica : Secondary3 to Primary Replica – Primary2 and made Primary1 Secondary Replica Secondary1
Evicted: DR1 and removed from AAG à Had to evict first since SQLServer 2012 AAG supports only 5 replicas at a time
Added Replicas: DR2
At this point time we have : Primary2, Secondary2, Secondary4, DR2, Secondary1
Things looked good so far.
Now is where the problem starts:
Nodes Secondary1 (old Primary) and Secondary2 were evicted from WSFC before they could be removed from AAG leaving these replicas as Orphan. Because of this, the AAG thinks that the two replicas still exist and is not truncating the logs of the databases and due the this the Drives are filling up.
In SSMS, Availability Groups à Availability Replicas I see the two replicas being X-ed (in red) out. Does this mean, I can remove the replicas (Right clickà Remove from Availability Group) without it affecting the AAG negatively?
Thanks,
rgn