BizTalk Server 2013 R2 BHM toolBizTalk 2013 R2 ships with a new tool called as “BizTalk Health Monitor”. BHM is freely available for all BizTalk 2013 R2 users. More about BHM tool at BizTalkHealthMonitor
Of late we see a lot of incidents in which customers face issues with LogShipping. Either they are not able to properly configure the BizTalk LogShipping or while they are able to configure Logshipping, they face an issue getting the DR(Disaster Recovery) server up and running or encounter trouble pointing the BizTalk server to the DR SQL server. I have put down the steps to be followed for BizTalk Log Shipping. The steps mentioned are not detailed but have been broken down into simpler ones. If you need detailed information please refer to the corresponding MSDN article.
In case of disaster recovery and database restoration, Log Shipping in the only supported method for BizTalk databases.
Planning for Disaster Recovery:
Configuring Log Shipping:[Refer Configuring LogShipping for detailed information]
exec bts_ConfigureBizTalkLogShipping @nvcDescription = '<MyLogShippingSolution>',@nvcMgmtDatabaseName = '<BizTalkServerManagementDatabaseName>',@nvcMgmtServerName = '<BizTalkServerManagementDatabaseServer>',@SourceServerName = null, -- null indicates that this destination server restores all databases@fLinkServers = 1 -- 1 automatically links the server to the management database
Your Log Shipping is configured now and you should see BizTalk DBs in restoring state on the DR site
Update “SampleUpdateInfo.xml” on the BizTalk Server so that all database server information is updated with DR SQL server details.
Recovering from failure:
Once this job is completed, go to the next step for pointing the BizTalk server to the newly restored BizTalk DB.
How to reconfigure Destination Database server for LogShipping:
Note: This will clean everything from the DR DB site
Below is simple illustration on what we do in BizTalk Logshipping:
Written by: Anand Singh
Reviewed By: Chirag Pavecha