locked
BizTalk Backup - Destination Server question RRS feed

  • Question

  • Hi,

    I have configured the "BizTalk Backup Server" successfully and now it's creating the "backup files" regularly (including full and log backups)

     

    My question is related to "Destination Server" for Backup Restore purpose.  
    We have installed SQL Server on new Server with all the same versions and paths as UAT Server.

    Question:- Do I need to install any BizTalk component on new Destination Server? If not then "Should I copy sql files (LogShipping_Destination_Schema.sql) to destination server"?  Because obviously I don't have any BizTalk SQL Jobs on the Destination Server. 

    http://msdn.microsoft.com/en-us/library/aa560961(v=bts.70).aspx

     

    Regards,

    Lucky Ray


    Wednesday, July 13, 2011 10:43 PM

Answers

  • You will need to copy LogShipping_Destination_Schema.sql and LogShipping_Destination_Logic.sql to the destination SQL Server and then follow the instructions that you have in your post.

    As prt of the log shipping process it will also copy over the BizTalk jobs the only thing I normall also do is create a SSIS package to copy of the login from the production BizTalk SQL Server.


    Bill Chesnut | BizTalk Server MVP | Mexia Consulting | Melbourne Australia
    http://www.biztalkbill.com
    Please indicate "Mark as Answer" if this post has answered the question.
    Wednesday, July 13, 2011 11:14 PM
  • Yes, the scripts will create 3 jobs in the destination SQL Server

    These are the jobs:

    • copy the backup info from the production BizTalk SQL Server,
    • restore full backup (if necessary) and logs to n-1
    • restore final log to log mark (this is disable until you run it manually when you switch to dr)

    As part of this process (3rd job) also creates the BizTalk jobs that are on the Production BizTalk SQL Server.


    Bill Chesnut | BizTalk Server MVP | Mexia Consulting | Melbourne Australia
    http://www.biztalkbill.com
    Please indicate "Mark as Answer" if this post has answered the question.
    • Marked as answer by Lucky Ray Thursday, July 14, 2011 7:08 PM
    Thursday, July 14, 2011 1:03 AM

All replies

  • You will need to copy LogShipping_Destination_Schema.sql and LogShipping_Destination_Logic.sql to the destination SQL Server and then follow the instructions that you have in your post.

    As prt of the log shipping process it will also copy over the BizTalk jobs the only thing I normall also do is create a SSIS package to copy of the login from the production BizTalk SQL Server.


    Bill Chesnut | BizTalk Server MVP | Mexia Consulting | Melbourne Australia
    http://www.biztalkbill.com
    Please indicate "Mark as Answer" if this post has answered the question.
    Wednesday, July 13, 2011 11:14 PM
  •  

    You will need to copy LogShipping_Destination_Schema.sql and LogShipping_Destination_Logic.sql to the destination SQL Server and then follow the instructions that you have in your post.

    As prt of the log shipping process it will also copy over the BizTalk jobs the only thing I normall also do is create a SSIS package to copy of the login from the production BizTalk SQL Server.


    Bill Chesnut | BizTalk Server MVP | Mexia Consulting | Melbourne Australia
    http://www.biztalkbill.com
    Please indicate "Mark as Answer" if this post has answered the question.
    When you said "As prt of the log shipping process it will also copy over the BizTalk jobs" do you mean... those two sql scripts will create SQL jobs for restoring backups?

     

    • Marked as answer by Lucky Ray Thursday, July 14, 2011 7:08 PM
    • Unmarked as answer by Lucky Ray Thursday, July 14, 2011 7:08 PM
    Wednesday, July 13, 2011 11:51 PM
  • Yes, the scripts will create 3 jobs in the destination SQL Server

    These are the jobs:

    • copy the backup info from the production BizTalk SQL Server,
    • restore full backup (if necessary) and logs to n-1
    • restore final log to log mark (this is disable until you run it manually when you switch to dr)

    As part of this process (3rd job) also creates the BizTalk jobs that are on the Production BizTalk SQL Server.


    Bill Chesnut | BizTalk Server MVP | Mexia Consulting | Melbourne Australia
    http://www.biztalkbill.com
    Please indicate "Mark as Answer" if this post has answered the question.
    • Marked as answer by Lucky Ray Thursday, July 14, 2011 7:08 PM
    Thursday, July 14, 2011 1:03 AM
  • You don't need to install any BizTalk component on the SQL server and you can manually copy and run these scripts(LogShipping_Destination_Schema.sql, LogShipping_Destination_Logic.sql) on the master database (msdb) on SQL server.

     

    As an additional reference have a look at this post.


    Mark As Answer or Vote As Helpful if My Reply Does, Regards, -Rohit
    Thursday, July 14, 2011 5:49 AM
    Moderator