none
mirrored database - options for replicating to a remote site

    Question

  • We've got a site that is running a mirrored database based on SQL 2008 R2 Enterprise nodes. SQL #1 being the primary for applicaiton to access and SQL #2 being a mirrored partner with a witness SQL running on site.

    we've got a requirement now to raise a remote georgaphical site (we're talking WAN, 10 - 20 Mbit/Sec link)  that would contain a copy of the database in case of primary site complete failure.

    i am trying to udnerstand what are our options in replicating database data to the remote site with least data loss period.

    any brilliant ideas on the issue are much appreciated.:)

    rgds,

    yan


    Yan Doldonov Crucel


    • Edited by Crucel Thursday, February 16, 2012 7:23 PM
    Thursday, February 16, 2012 7:22 PM

Answers

  • Hello,

    We use Database Mirroring between two different Datacenters, one on each coast, and it works perfectly fine

    Regards


    Javier Villegas | @javier_villhttp://sql-javier-villegas.blogspot.com/

    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

    • Marked as answer by Peja Tao Monday, February 20, 2012 3:06 AM
    Thursday, February 16, 2012 7:42 PM
  • You can use Log-shipping / SAN snapshot replications onto new data center ... I hope you have already configured db mirroring wirth in primary data center databases.

    http://uk.linkedin.com/in/ramjaddu

    • Marked as answer by Peja Tao Monday, February 20, 2012 3:06 AM
    Thursday, February 16, 2012 9:08 PM
  • As long as you have mirroring in your local datacenter already (and need it for HA purposes) you should maybe consider migrating to SQL 2012 and AlwaysOn. If this is not an option I agree with RamJaddu to go for Log-Shipping.
    • Marked as answer by Peja Tao Monday, February 20, 2012 3:06 AM
    Friday, February 17, 2012 6:23 AM

All replies

  • Hello,

    We use Database Mirroring between two different Datacenters, one on each coast, and it works perfectly fine

    Regards


    Javier Villegas | @javier_villhttp://sql-javier-villegas.blogspot.com/

    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

    • Marked as answer by Peja Tao Monday, February 20, 2012 3:06 AM
    Thursday, February 16, 2012 7:42 PM
  • You can use Log-shipping / SAN snapshot replications onto new data center ... I hope you have already configured db mirroring wirth in primary data center databases.

    http://uk.linkedin.com/in/ramjaddu

    • Marked as answer by Peja Tao Monday, February 20, 2012 3:06 AM
    Thursday, February 16, 2012 9:08 PM
  • As long as you have mirroring in your local datacenter already (and need it for HA purposes) you should maybe consider migrating to SQL 2012 and AlwaysOn. If this is not an option I agree with RamJaddu to go for Log-Shipping.
    • Marked as answer by Peja Tao Monday, February 20, 2012 3:06 AM
    Friday, February 17, 2012 6:23 AM
  • thank you all! very useful.

    we're picking up a client site which has been setup already by someone else prior to our involvement. unfurtunately it's already now in full production phase with external clients accessing realtime database.

    a requirement now is to build a reserve remote site to pick up as part of a disaster recovery plan.

    we are now in process of investigating topology trying to fully understand existing configuration.

    SQL 2012 is not an option as it's a a custom software product which has been developed by a 3-d party and the SQL config has been specified as part of the underlying platform.

    appreciate all the feedback.


    Yan Doldonov Crucel

    Friday, February 17, 2012 8:56 AM
  • Can you pls mark it answer - If it answer your question and help others to find the solution quickly

    http://uk.linkedin.com/in/ramjaddu

    Friday, February 17, 2012 11:02 AM