none
HA solution??

    Domanda

  • I have 2 servers and 2 SAN storages   HA requirement as below:

    a) Must have automatic failover.

    b) Primary database must replicate to secondary server.

    c) Both Primary and secondary  database must always as real time in synchronized.

    d) database will alocate at SAN storage

    e) Server A is production server with 1 production database.

    How can I plan the HA solution for this scenario?

    Can it be configurate as Clustering 1st then later with SAN replication? Do i need to add extra server or SAN staroge to be able for this setup? my assumption as below:

    server A and server B connect to SAN A for the clustring and  server B at also connect to SAN B where database at server B will replicate from SAN A to SAN B. 

    However as I understand let said clustring faolover, then user still need to manualy bring the Server B and SAN B up right? How to configute the HA solution as I mentioned above? I not familiar with this solution. Hope to get advice.

    mercoledì 25 aprile 2012 03:22

Risposte

  • Hello,

    If you didn't want the SAN being the single point of failure, synchronous mirroring with a witness could be a solution. If you can use SQL 2012, Availability groups may also work for you. If the SAN single point of failure is fine, clustering would meet the requirements.

    While there are multiple different technologies that can be dropped in, don't forget you can mix and match! If SQL Server 2012 is out of the question, you could always do clustering on the first SAN and then do mirroring from the cluster to a box on the second SAN.

    -Sean


    Sean Gallardy, MCC | Blog

    mercoledì 25 aprile 2012 03:32
  • SQL Server 2012 Always ON requires Windows clustering  installed on the server

    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

    venerdì 27 aprile 2012 08:09

Tutte le risposte

  • Hello,

    If you didn't want the SAN being the single point of failure, synchronous mirroring with a witness could be a solution. If you can use SQL 2012, Availability groups may also work for you. If the SAN single point of failure is fine, clustering would meet the requirements.

    While there are multiple different technologies that can be dropped in, don't forget you can mix and match! If SQL Server 2012 is out of the question, you could always do clustering on the first SAN and then do mirroring from the cluster to a box on the second SAN.

    -Sean


    Sean Gallardy, MCC | Blog

    mercoledì 25 aprile 2012 03:32
  • Assuming you want to have full redundancy so that you can withstand the failure of a server or a SAN I suggest you investigate one of the following:

    SQL 2012 Always On Availability Groups - in this configuration ServerA is attached to SAN1 and ServerB is attached to SAN2

    SQL 2008 Database Mirroring -  in this configuration ServerA is attached to SAN1 and ServerB is attached to SAN2

    Multisite Clusters with Array or Host based replication -  in this configuration ServerA is attached to SAN1 and ServerB is attached to SAN2

    Have a look at those solutions and let us know if you have any questions.


    David A. Bermingham, MVP, Senior Technical Evangelist, SIOS Technology Corp

    giovedì 26 aprile 2012 05:02
  • Hi SQLMAN,

    Use SQL failover clustering with database mirrooing .i think indirectly you are asking high availability and database level disaster recovery.

    http://www.sqlskills.com/BLOGS/PAUL/category/Failover-Clusters.aspx check this white paper you will get full idea.


    Thanks&Regards Siva G

    giovedì 26 aprile 2012 11:23
  • SQL Server 2012 Always ON requires Windows clustering  installed on the server

    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

    venerdì 27 aprile 2012 08:09
  • Based on these requirements, I'd suggest db mirroring, with a witness.  However, keep in mind, the mirror database is 'closed' for any user activity.  SQL 2012 Availability Groups would give you the elegance of mirroring, but with an 'open' read-only copy of your primary database for reporting/etc to offload performance from ServerA.  It works very well.

    Roz

    lunedì 30 aprile 2012 20:32