sql disaster recovery

  • hi all,

    my server is sql 2005 sp3 standard edition.

    i want to implement kind of disaster recovery between to 2 sites.

    i plaaned to do log shipping between the sites

    ( mean backup tlog copy and restore in second site - and nothnig will happen if i lose some data

    in case of crises in the main site)

    untill here every thing is ok 🙂

    my it manger come to me and say i cant promise you that copy file operation

    will succed , and i have probloem to monitor this kind of opertion.....

    he told me : " i need tcp ip between the 2 sites"

    so i read in google and db mirror will do the job ,

    the probloem i will need to buy enterprise edition if i want to read data from

    db in mirror state via db snapshoot.

    anthoer problem :

    if devloper write transation with 5 giga its mean ( in mirror all transaction go to move

    to mirror)

    it going to stuck my network ? ( in log shiping i can check the log size before any move...)

    does mirror know to mange it self ( move transaction with any logic except asincrony or suncrhony)

    any tips trick , shourt cut to articles will be vary good for me

    thank you very much

    for your help

    sharon

  • I would look at implementing asynchronous mirroring between your site and your DR site.

    The data will be sent to your dr site, but your primary system won't wait for the transactions to be committed at your DR Site.

    Fail over to the DR site will be done manually.

    You might look into any encryption requirements between your site and your DR site.

    This will depend highly on bandwidth to your DR site. You might want to verify the bandwidth before moving down this road.

    You also need to be able to initialize the secondary database at your DR Site. Make sure you can get to the site remotely.

    As for how to and instructions:

    I would read the overview on Technet http://msdn.microsoft.com/en-us/library/ms190941(v=sql.90).aspx

    There are numerous samples on websites and google videos that are step by step.

    Good Luck

    -Erich

  • You really need to think about what you're solving here. If it's DR, then you can't worry about reading data from the secondary. If it's scale out, that's separate.

    In either mirroring or log shipping, if a large transaction comes through, it needs to move to the secondary site. If you don't move it because it's too large in Log Shipping (LS), then what will you do? Move another backup instead and reset things? You have to move it somehow.

    One thing with LS, you can set up two separate restores from the same files being copied. So you could have a DR one that restores every 15 minutes, and another that is readable and restores on a different schedule (maybe all logs every 4 hours). That would give you a decent window to continue to read data from the secondary.

    If you search Log Shipping or Mirroring, there are some articles on this site as well that might help you get started.

    http://www.sqlservercentral.com/articles/104391/

    http://www.sqlservercentral.com/articles/62676/

    http://www.sqlservercentral.com/articles/72774/

    http://www.sqlservercentral.com/articles/72009/

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

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