Read Scale availability group

  • We are designing a new SQL farm in our company, they want HA/DR (so a WSFC cluster), but we only need DR for some certain Databases not HA.  These other Databases will be on other separate VMs due to size and separation.

    If you have a cluster with three nodes two in one site with HA and 1 in another site for DR, what should you do for the databases with no need for HA.  I had planned to have the non-HA databases in a read scale availability group between two VMs away from the cluster to provide the DR ability.

    But thinking about it would it not make more sense to have the two WMs in the cluster, with no quorum votes, with just a synchronous, manual failover availability group between these two VMs?

    Is there ever a situation where you would use read scale availability group where you have a cluster available?

    • This topic was modified 4 years, 9 months ago by  garryha.
  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • It's not completely clear what you're describing here. I think you're making this confusing in some sense. Forget about VMs for a second and treat these as machines. The VM portion can be the same machine or not, but that's an aside. Give the systems some name so that we can talk about the architecture with some context.

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply