Should we consider a process to transfer blob storage as part of our DR or BC plan?


  • Hi all,

    quasi-programming / policy question. 

    we're looking at our biz continuity and DR plans.  we have plans to migrate web apps and databases to other regions (geo restore, etc.) if there is an issue in our primary DC but we have no plans around our storage accounts.   If we are using LRS storage should we have a plan to be backing this up somewhere else? or would using GRS eliminate this?  

    I guess what i'm trying to ask is what does a DR plan that involves blob storage look like?  what do we need to consider (if anything) when using large amounts of blob storage.  



    Thursday, January 19, 2017 8:05 PM


  • geo redundant databases (azure SQL databases) will do the trick, but the data will only be made availble in case of a disaster at the primary DC

    geo redundant databases (azure SQL databases) with read access will make these endpoints available to read out (you can use that for reporting services and so on)

    do note that you can have up to 4 additional endpoints in different regions, but you will have to multiply the costs with the additonal endpoints.

    if you are talking about IaaS databases, use the SQL replication mechanisms, with using geo redundant storage, this will not help you for application consistancy

    for the webapps, in standard and premium, geo distributed deployments are supported. in this case put a load balancer in front of them:

    - Traffic Manager can load balance on DNS

    - Azure external load balancers can be used (with different rule sets)

    - Application gateway can be used

    Cheers Christophe

    Kindly click Mark as Answer on the post that helps you, this can be beneficial to other community members reading the thread and Vote as Helpful

    Azure Fanatic!

    • Edited by Cloud_Crusader Friday, January 20, 2017 1:04 AM
    • Marked as answer by Mike_BFN Monday, January 23, 2017 3:03 PM
    Friday, January 20, 2017 12:59 AM