1

We have a Production BizTalk Environment and our Test Environment went Kaput, so we are trying to copy the production environment server image and setup another Test environment.

Our Server Team successfully copied the Image of the Production server and setup the TEST Servers and the DBA's successfully backed up the Production SQL Server Database and restored in the Test SQL Server Instance.

But now when we add to the BizTalk group from the Test SQL Server Database it is still pointing to Production instance, if we stop/disable Receive Locations, Send Ports it is also stopping in Production. Please help on how to make this to work?

We also want to do the similar settings for our Disaster Recovery environment.

Barathan K
  • 13
  • 3
  • 2
    Wow this sounds very dangerous! I think that during the BizTalk configuration process a lot of stuff is stored in the various databases that points to other databases, servers etc. Did you try unconfigure and then reconfigure? Personally I don't think I'd take the risk. – Sir Crispalot Oct 25 '13 at 21:57
  • 3
    It would be safer to do a clean install of BizTalk and then export the applications in binding files from Prod and import them into your new test environment. – Dijkgraaf Oct 26 '13 at 21:25

1 Answers1

0

If you still want to do this (even with lots of people advising you not too). The steps you need to take can be found here How to Move the BizTalk Server Databases (BizTalk 2006R2) The steps you have to do to point to the new Test BizTalk server to your restored databases, which is the step that you've missed out and why it is still pointing to your Production database.

For BizTalk 2010 it would be How to Restore Your Databases and you will also want to read Moving the BizTalk databases (part 2).

Dijkgraaf
  • 11,049
  • 17
  • 42
  • 54