none
Configuring BizTalk jobs in a clustered environment RRS feed

  • Question

  • Hi,

    I've a configuration wherein I've two SQL server nodes clustered using a windows failover cluster and BizTalk DB's sit on the SQL instance being shared on this SQL cluster. BizTalk Server nodes(two) point to the SQL cluster.

    https://docs.microsoft.com/en-us/biztalk/core/sample-biztalk-server-high-availability-scenarios

    Please refer to 'Small BizTalk Server Deployment' figure in the link stated above to understand the configuration.

    In this case, I believe we're supposed to configure BizTalk jobs on both the servers. I want understand what the official recommendation is, couldn't find any help online specific to this point.
    Any Suggestions/Recommendations are welcome.



    Wednesday, October 10, 2018 10:19 AM

All replies

  • I assume you have an active/passive SQL cluster with two nodes?

    As other services the job agent service needs to be a clustered ressource and will be running on the active node
    Thus the jobs needs to be deployed on both nodes

    EDIT: Correction: jobs are stored in MSDB and will be visible on the node which actively has control of the SQL Instance

    /Peter


    When asking a question please be as thoroughly as possible this will make it easier to assist you http://www.catb.org/esr/faqs/smart-questions.html


    Wednesday, October 10, 2018 10:42 AM
  • Yes, it's an active/passive SQL cluster. We've created an availability group to which I've added BizTalk Db's which are 'READONLY' on one of the server(secondary/passive) and 'READWRITE' on the other(primary/active).

    I'm not sure on how to replicate BizTalk system jobs on both the servers and constraint it to run only on the active one.

    Do I need to explicitly add job agent as a resource in the cluster? 

    Wednesday, October 10, 2018 1:24 PM
  • Do you have a standard active/passive clustered mssql or do you have an Always On configuration?

    /Peter


    When asking a question please be as thoroughly as possible this will make it easier to assist you http://www.catb.org/esr/faqs/smart-questions.html

    Wednesday, October 10, 2018 1:35 PM
  • For clarity, you don't need to do anything.

    BizTalk Configuration will add the appropriate Jobs to the Agent wherever the target database is.

    So, depending on how you're splitting the DB's, some Jobs will be on Instance A, some will be on Instance B.  And very important, you can't change this even if you wanted to.

    Basically, you're pre-worrying about something that you don't need to.

    Wednesday, October 10, 2018 2:10 PM
    Moderator
  • Ahh yes my bad, SQL Server Agent Job configuration are stored in MSDB

    /Peter


    When asking a question please be as thoroughly as possible this will make it easier to assist you http://www.catb.org/esr/faqs/smart-questions.html

    Wednesday, October 10, 2018 2:32 PM
  • For clarity, you don't need to do anything.

    BizTalk Configuration will add the appropriate Jobs to the Agent wherever the target database is.

    So, depending on how you're splitting the DB's, some Jobs will be on Instance A, some will be on Instance B.  And very important, you can't change this even if you wanted to.

    Basically, you're pre-worrying about something that you don't need to.

    Hi,

    Apparently, target server is a SQL cluster, attempting to configure BizTalk on an SQL cluster, it creates BizTalk Db's and BizTalk jobs on the primary server itself. Next step is to add these db's to the availability group which will create a replica of these db's in a secondary database.
    I could find the jobs on the primary server itself, and I believe it must be on both the servers to be running when the respective server is active.
    I'm not clear if I've to manually replicate the jobs on the secondary server and let the jobs run on both the servers without having a technical impact.


    Thursday, October 11, 2018 11:15 AM
  • Do you have a standard active/passive clustered mssql or do you have an Always On configuration?

    /Peter


    When asking a question please be as thoroughly as possible this will make it easier to assist you http://www.catb.org/esr/faqs/smart-questions.html

    I've Always On configuration having the two SQL servers clustered over Windows Failover Cluster.
    Thursday, October 11, 2018 11:19 AM
  • Haven't used Always On configuration
    But as the soeconday databases are Replicas I will assume you should only run BTS Jobs on the Primary DB

    Please check with a DBA

    /Peter


    When asking a question please be as thoroughly as possible this will make it easier to assist you http://www.catb.org/esr/faqs/smart-questions.html

    Thursday, October 11, 2018 11:46 AM
  • Unless you have no other choice, don't use AOAG.  It adds a lot of complexity with no incremental value to BizTalk Server over regular Failover Clustering.

    If you have to use AOAG, it's just the same as regular Failover Clustering.  You must configure the SQL Instances on the cluster first, then point to which ever instance during BizTalk Configuration.

    Very important point, you really don't have to do anything special.  The SQL Clustering is completely unknown to BizTalk.

    But again, regular Failover Clustering, not AOAG, is still a better option for BizTalk Server.

    Thursday, October 11, 2018 2:01 PM
    Moderator