Comments on: BizTalk DR: Configuring BizTalk Backup for Disaster Recovery – Part 2

By: Configuring BizTalk Backup for Disaster Recovery – Part 2 | SOA Governance - Service Oriented Architecture - SOA Business - SOA Design - SOA Services - SOA Software - SOA Solutions - SOA Security - SOA Web Service

Tue, 05 Jan 2010 07:03:16 +0000

[...] Originally posted by Nick Heppleston at: http://www.modhul.com/2009/09/04/configuring-biztalk-backup-for-disaster-recovery-part-2/ [...]

By: Gordon

Gordon — Tue, 01 Dec 2009 05:38:48 +0000

Great set of articles about BizTalk log-shipping, how does this all work though with a stand-by BizTalk host server? Currently we run a seperate Biztalk host server at our DR site with it’s own set of BizTalk databases and seperate service accounts/domain groups. I am about to redesign this, would it be best to chnage our DR installation of BizTalk to use the same service accounts and domain groups as production? I’d like to implement the BizTalk log-shipping process but we also want to keep our DR installation independent for DR testing.

By: Nick Heppleston

Nick Heppleston — Mon, 30 Nov 2009 10:52:30 +0000

Part 3 is in the pipeline – unfortunately, a new client, family etc. have come in the way…

By: Earl Cooper

Earl Cooper — Fri, 27 Nov 2009 19:39:13 +0000

How do we find out when Part 3 is available….

By: mamata

mamata — Wed, 28 Oct 2009 18:16:30 +0000

Hi Nick,

please post your PART3 for BizTalk Log shipping

thanks

By: kln

kln — Wed, 23 Sep 2009 00:08:40 +0000

Hi Nick,

Can we take the Differential backup, if the BizTalk Log shipping is configured and its Taking Daily full backups and every 15 mins Log backups?

What happens if we schedule the Differential backup every 6 hrs? Is that supported?

Please advice

thanks
Kln

By: kln

kln — Tue, 22 Sep 2009 16:47:37 +0000

Hi Nick,

I have a SQL server 2005, Server A and BizTalk Server 2006 R2, Server B on Primary location. Similarly, we have a SQL Server 2005, Server C, BizTalk Server 2006 R2, Server D on Secondary/Stand-by location.

BizTalk application is deloyed on Primary & it is a Production Server. On Secondary/Stand-by, SQL Server is installed, BizTalk is installed but the developed application is NOT deployed.

Now, we configured BizTalk Logshipping between Primary & Secondary. While configuring BizTalk Logshipping:

1. Took the backup of current databases on Secondary SQL Server.
2. Deleted the databases on Secondary
3. Configured the BizTalk Log shipping
4. All the databases are in Restoring mode.
5. BizTalk Log shipping Test is completed succesfully.
6. Now, we want to Disable the Configured Log shipping and want to restore the databases of Step1.
7. Then Deploy the BizTalk Appliccation on Secondary BizTalk Server Server D.
8.Then Reconfigure the BizTalk Log shipping again, which will be a full fledged Production configuration

In-order to achieve the above, what is the best method to Disable Log Shipping, to freshly re-configure Log shipping configuration??

thanks

By: Garyreeds

Garyreeds — Tue, 22 Sep 2009 16:30:11 +0000

Yes, the above method worked!!!

By: Garyreeds

Garyreeds — Mon, 21 Sep 2009 23:36:44 +0000

Do we need to run the below 3 scripts in each Stand-by SQL instance as below:

STEP3: Connected to SQL2\INS3 and executed the scripts 1)LogShipping_Destination_Schema.sql & 2)LogShipping_Destination_Logic.sql

STEP4:Connected to SQL2\INS3 & executed the below script:

exec bts_ConfigureBizTalkLogShipping @nvcDescription = ‘Logshipping’,
@nvcMgmtDatabaseName = ‘BizTalkMgmtDb’,
@nvcMgmtServerName = ‘SQL2\INS3′,
@SourceServerName = SQL2\INS3, — null indicates that this destination server restores all databases
@fLinkServers = 1 — 1 automatically links the server to the management database

STEP3: Connected to SQL2\INS2 and executed the scripts 1)LogShipping_Destination_Schema.sql & 2)LogShipping_Destination_Logic.sql

STEP4:Connected to SQL2\INS2 & executed the below script:

exec bts_ConfigureBizTalkLogShipping @nvcDescription = ‘Logshipping’,
@nvcMgmtDatabaseName = ‘SSODB’,
@nvcMgmtServerName = ‘SQL1\INS3′,
@SourceServerName = SQL1\INS3, — null indicates that this destination server restores all databases
@fLinkServers = 1 — 1 automatically links the server to the management database

STEP3: Connected to SQL2\INS1 and executed the scripts 1)LogShipping_Destination_Schema.sql & 2)LogShipping_Destination_Logic.sql

STEP4:Connected to SQL2\INS1 & executed the below script:

exec bts_ConfigureBizTalkLogShipping @nvcDescription = ‘Logshipping’,
@nvcMgmtDatabaseName = ‘BizTalkMsgBoxDb’,
@nvcMgmtServerName = ‘SQL1\INS1′,
@SourceServerName = SQL1\INS1, — null indicates that this destination server restores all databases
@fLinkServers = 1 — 1 automatically links the server to the management database

STEP3: Connected to SQL2\INS2 and executed the scripts 1)LogShipping_Destination_Schema.sql & 2)LogShipping_Destination_Logic.sql

STEP4:Connected to SQL2\INS2 & executed the below script:

exec bts_ConfigureBizTalkLogShipping @nvcDescription = ‘Logshipping’,
@nvcMgmtDatabaseName = ‘BizTalkMsgBoxDb’,
@nvcMgmtServerName = ‘SQL1\INS2′,
@SourceServerName = SQL1\INS2, — null indicates that this destination server restores all databases
@fLinkServers = 1 — 1 automatically links the server to the management database

By: Garyreeds

Garyreeds — Mon, 21 Sep 2009 21:49:05 +0000

Hi Nick,

Could you see the Answer from Alex http://social.msdn.microsoft.com/Forums/en-US/biztalkgeneral/thread/293a0c5d-95cb-47ec-be33-3cf0fdb9265d

and advice what exactly we should do when having multiple SQL instances in Stand -by server?