BizTalk Production and DR setup

Home Page Forums BizTalk 2004 – BizTalk 2010 BizTalk Production and DR setup

Viewing 1 reply thread
  • Author
    Posts
    • #25899

       

       

      PROD
      ABC

      BizTalk Server

      Sql Server
      DR               
      XYZ
      BizTalk Server
      Sql Server

      Dear Gurus,

      I need your help very badly. Our
      client has a BizTalk environment like above under the same domain.

      Everything BizTalk and SQL
      installed on configured on machine(I know it’s a bad design, but client is not
      ready for more severs). Please note that PRODUCTION and DR has different names.

      Now client is asking us for DR
      practice, meaning they want to shutdown the PROD and make the DR ready. Everything
      in PRODUCTION site is mounted in SAN, they simply replicated all the BizTalk
      and custom databases to DR site.  Obviously
      this solution is not working as all the DB contains PROD server name. Now they need
      immediate solution.

      I am not a Infra guy not BizTalk
      admin, but I suggested  hem for two
      solutions.

      1. Rename the SQL-Server to point
      its own DB.

      – Remove server from the list of known remote
      and linked servers on the local instance of SQL Server.
      EXEC master.dbo.sp_dropserver ‘[SERVER NAME]‘

      – Define the name of the local instance of SQL
      Server.
      EXEC master.dbo.sp_addserver ‘[NEW SERVER NAME]‘, ‘local’

      In the above case I will pass DR server name as a parameter, so the
      change will happen in low level. In fact that’s what I needed. After that I
      will also change the master secret sever as per the recommendation from
      microsoft(http://msdn.microsoft.com/en-us/library/aa559842.aspx)

      We have a risk here,  remember they replicated all DB info from
      production to DR site, still the DB holds the value of PROD server. So we ask
      them to turn off the production(down time) and proceed with the server name.

      2. We create a new DR environment
      like DR, later we change the server name.

      Please advise me, really I am not
      sure on how to resolve the above issue.

    • #25901

      Hi,

      Are the PRD and DR site on different physical locations? If no, then it’s maybe better to use a sql cluster together with a biztalk farm. You will have the same number of machines but when sql A goes down (not the site), there is a lot less down time using a cluster.

      If you have different sites for PRD and DR, then you could use BizTalk log shipping. Using BizTalk log shipping, the database backups will be copied towards the DR site. If the PRD site goes down, then you have execute some steps in order to fire up the DR site.

      There is a complete documentation from Microsoft how you can configure BizTalk log shipping and which steps you must follow in order to fire up the DR site.

      Regards

      • #25902

        * forgot to log in *

        Hi,

        Are the PRD and DR site on different physical locations? If no, then it's maybe better to use a sql cluster together with a biztalk farm. You will have the same number of machines but when sql A goes down (not the site), there is a lot less down time using a cluster.

        If you have different sites for PRD and DR, then you could use BizTalk log shipping. Using BizTalk log shipping, the database backups will be copied towards the DR site. If the PRD site goes down, then you have execute some steps in order to fire up the DR site.

        There is a complete documentation from Microsoft how you can configure BizTalk log shipping and which steps you must follow in order to fire up the DR site.

        Regards

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.