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

By: Tigger's Lair » links for 2010-11-09

Tigger's Lair » links for 2010-11-09 — Tue, 09 Nov 2010 20:06:42 +0000

[...] Configuring BizTalk Server Log Shipping and Backup for Disaster Recovery – Part 1 | Nick Hepplesto… Leave a comment | Trackback No comments yet. [...]

By: Lex Hegt

Lex Hegt — Fri, 18 Jun 2010 20:14:00 +0000

Hi Nick,

Great explanation. I’ll forward your articles to our system engineers, hoping they get a better understanding of how Marked Backups work in BizTalk.

Regards,
Lex

By: SCOM can cause Unchecked Growth in SSODB | Service Oriented Architecture - SOA

Wed, 16 Jun 2010 06:59:33 +0000

[...] If you’re looking for more information on the Backup BizTalk Server Job, take a look at my series of posts on the topic: http://www.modhul.com/2009/06/29/configuring-biztalk-for-disaster-recovery-part-1/ [...]

By: SCOM can cause Unchecked Growth in the SSODB | Nick Heppleston's BizTalk Blog

Tue, 15 Jun 2010 09:32:49 +0000

By: Nick Heppleston

Nick Heppleston — Tue, 18 May 2010 07:47:08 +0000

Cyril,

I’ll be detailing these in the Part 3, if I ever get around to writing it…..

Nick.

By: Cyril Grant

Cyril Grant — Thu, 13 May 2010 07:45:45 +0000

Hi Nick, excellent post….

You’ve mentioned several scripts in this post and in part. Particularly interested in those that need to be run, after the recovery to ensure the secondary node is being referenced and not the primary.

Thanks
Cyril

By: Lee Graber

Lee Graber — Fri, 09 Apr 2010 17:13:25 +0000

BizTalk does not copy the log files, it simnply restores them. If you would like to copy them to a central share that is totally supported. If you do this, follow the instructions at http://msdn.microsoft.com/en-us/library/aa546753.aspx.

The relevant section is:

“If you move the full or log backups for a source database from the location in which the Backup BizTalk Server job put them, you should update the associated row for that database in the bts_LogShippingDatabases table on the destination system by setting the LogFileLocation or DBFileLocation to the new location where the destination system should read the full/log backup files. This table is populated when you run the bts_ConfigureBtsLogShipping stored procedure. By default, these columns are set to null, which indicates that the destination system should read the backup files from the location stored in the adm_BackupHistory table.”

HTH
Lee

By: gary

gary — Thu, 18 Mar 2010 06:52:07 +0000

Hi,

I have configured BizTalk Backup job, we created a backup share on Primary server and then configured the BizTalk log shipping.

Now, I did not see any log backups copied to DR server. It’s just restoring the logs on DR server directly from the share on Primary.

But in normal Log shipping, the copy job, copies the log back files to DR server? But BizTalk log shipping won’t!!

By design, Is the BizTalk Log shipping copies the log backup files to DR server or NOT?

If NOT, how can we copy and tell the Restore job to pick the log files from the share created on DR Server? I did NOT find about this in BOL documentation that we need to move the log files to DR server. Could you please point me to the link where it addresses this?

thanks

By: Nick Heppleston

Nick Heppleston — Tue, 02 Feb 2010 15:07:53 +0000

Shipping-Fivezoom,

WordPress thought you were spam so apologies for not getting back to you sooner. Can you drop me an e-mail at nick@nospam (replace ‘nospam’ with ‘modhul.com’) and we’ll talk more.

Cheers, Nick.

By: shipping-fivezoom

shipping-fivezoom — Tue, 02 Feb 2010 10:47:26 +0000

Hello! Your post (Configuring BizTalk Server Log Shipping and Backup for Disaster Recovery – Part 1 | Nick Heppleston’s BizTalk Blog) does so well that I would like to translate it into French, publish on my french blog and link to you. You have something against it? Regards