[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 128
  • Last Modified:

Microsoft Clustering and SQL - what about the storage?

Hello all,

I am working on MS SQL clustering and looking into redundancy.  I understand all of the diagrams with regard to failover but the redundancy seems to stop at shared storage.  Multible nodes all pointing to the same storage array.  

Can anyone point me to a diagram and/or documentation on how to ensure redundancy of the storage array as well?  I have worked with Dell Equallogics and we replicated data between sites but what I'm looking for in this situation is to:

1.  Have the cluster nodes write to more than one storage location.  Is this possible with MSCS?
2.  If cluster nodes cannot talk to two storage arrays, can an array replicate every change to data/databases to another array instantly rather than using some scheduled replication?  What is the terminology for continuous/immediate replication?

Just starting on this so anything will help.  Basially looking at having a cluster with a node at one site and a node at another physical site.  MS has now allowed this over the network and removed the same subnet restriction but now I'm stuck on how to ensure the databases are replicated between the two sites.

Dell shop guys...just so you know.
0
yccdadmins
Asked:
yccdadmins
1 Solution
 
PadawanDBAOperational DBACommented:
What version and edition of MS SQL Server?  #1 (and in turn whether or not we need to go down the #2 path) depends on that answer =)
0
 
yccdadminsAuthor Commented:
Version is currently 2008 R2 running on a 2008 R2 Enterprise server.

I think what I'm looking for is how to get synchronous replication of the SQL database storage area rather than asynchronous.  So far, I have not seen a clustering diagram with that type of set up.  The diagrams always seem to have only a single storage array shared by all cluster nodes...
0
 
Scott PletcherSenior DBACommented:
You can do synchronous, if you're willing to have the delays and the potential issue if both sets of data are not available.
0
2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

 
yccdadminsAuthor Commented:
I think I found a lead on this but I'm hoping one of you all can expand.  What I described above has now changed since I found this and we can go back to our original design.

We have two nodes in a cluster that will be at separate locations.  They will now run MSCS/SQL and the database(s) remains on local disk - not on shared storage.  The application we are replacing was okay with this but we are moving to MSCS.  MSCS was not okay with this but I have now read that 2012 is fine with it.

We want to maintain this configuration but could not with SQL 2008 and below.  Alegedly, in 2012 you can set something up to synchronize data/databases on disparate nodes.  I have found instructions on this that are too minimal or too convoluted.

Have any of you set this up?  Anyone find a really good set of instructions?  I am still trying to Google but my search combinations have not revealed anything overwhelmingly helpful.
0
 
DBAduck - Ben MillerPrincipal ConsultantCommented:
I believe you are speaking about Availability Groups which is groups of databases that have windows nodes that are clustered. The SQL Servers don't need to be clustered, but the Windows Servers do.

You can start here and it will take you into the space of AG.

http://www.mssqltips.com/sqlservertip/2519/sql-server-alwayson-availability-groups--part-1-configuration/
0
 
yccdadminsAuthor Commented:
That's just about right -  got me started on the right track for sure.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now