SQL Multi Site Clustering and Replication

Soldato
Joined
30 Sep 2005
Posts
16,736
Calling all SQL Admins :D

Does anyone administer an SQL farm across a multi site environment. I'm keen to hear about peoples approach to the infrastructure design.

I'm researching SQLs ability to store DBs on highly available application shares, as I'd like to be able to fail over in the event of a site outage. Obviously SQL clustering is easy to do, and putting an extra node in multiple sites is easy, but the defacto standard has always been to use a single storage array. I want to use two, which is leaning me towards an HA share clustered at the windows level, and replicated as such.

There are third party products out there, but I think I might as well wait for 2016 and do it within the OS

Thoughts?
 
My biggest gripe against all the work that Microsoft has put into storage in the last few years is that it is insanely complex. It is all managed through PowerShell, with very little visibility of what is happening. When something has failed and you have the app users screaming "Sev 1" at you, the last thing you need is to be googling the correct syntax for the correct PowerShell commandlet.

isn't that all changing in 2016 :confused:
 
Not as far as I've seen -- they keep introducing powerful new capabilities, but it's all managed from the command line, and there are so many layers (5 or 6 between NTFS and the spinning disks) that troubleshooting has got to be a nightmare.

It does seem to be the case, that whilst you can configure something via the GUI....actually watching it work and/or troubleshooting is all powershell.
 
My initial plan was for 2016 file replica, so should I stick with that or the sql AO group?

There are two sans at each site anyway with plenty of disk space. However!! There will be two physical server nodes at Site A, but only one in Site B

p.s. Thanks for your help with this!!
 
Last edited:
Back
Top Bottom