I'm just starting on the design phase for a 2013 uplift in the fall, and have started fiddling with the newest sizing spreadsheet. One of the things I can't confidently fill in is "Number of Database Availability Groups." Google likewise seems stumped beyond these two points:
1) There's a 16 server per DAG limit
2) "It depends" - doesn't it always?
Quick caveat, I didn't design the current HA infrastructure. My predecessor did. I may or may not have access to 'why' it is the way it is, so it could be a fresh approach is going to be the most effective. That said...
Our 2010 model is currently 12 servers with two database copies each, one active and one passive. (Ignoring the archives for the moment.) They are built in pairs, so DB01 and DB07 are A/P on one server vs DB07 and DB01 on its mate. Failover is both automatic and manual, and...
