Stopping Application Processing on the Source System

Application processing should be stopped when the source BizTalk Server runtime servers are still able to participate in document processing using the existing database servers. In this scenario, processing activity must be stopped so that a consistent restore operation can be completed.

To stop application processing on the source system, ensure that no connections are open between the production BizTalk Server runtime computers and the SQL Server computers that house the BizTalk Server databases. Follow these steps to stop application processing on the production BizTalk Server runtime computers:

  1. Disable all receive locations on the BizTalk Server computers in the BizTalk group. Make a note of all receive locations that are disabled so that these receive locations can be re-enabled later. This will stop BizTalk Server from processing incoming messages.

  2. Stop all host instances from running on the BizTalk Server computers in the group. This can be done from the BizTalk Server Administration console. Make a note of all the host instances that were stopped so that these host instances can be restarted later.

  3. Stop all SQL Server Agent jobs related to BizTalk Server on the SQL Server computers that house BizTalk Server databases.

  4. If BAM is in use, disable any BAM cube update and data maintenance DTS packages. This can be done by using SQL Server 2000 Enterprise Manager or SQL Server 2005 Management Studio.

  5. Stop Analysis Services on the SQL Server computers that house BizTalk Server databases. This can be done by stopping all instances of MSSQLServerOLAPService on the SQL Server computers where Analysis Services is installed.

  6. Stop any other BizTalk Server services in Services Manager that may be running on the BizTalk Server computers in the group, for example, the Enterprise Single Sign-On Service and the Rule Engine Update Service. Make a note of the services that are stopped so that they can be restarted later.

  7. Close all applications that connect to the SQL Server computers that house BizTalk Server databases. This includes instances of the BizTalk Server Administration console, Visual Studio 2005, the Health and Activity Tracking reporting application, and any other installed BizTalk applications.

  8. Verify that there is no database activity generated by BizTalk Server. Use SQL Server Enterprise Manager or SQL Server 2005 Management Studio to see what processes are connected to the SQL Server computers that house BizTalk Server databases. This can be done by clicking to expand Management, Current Activity in SQL Server Enterprise Manager or by clicking to expand Management and Activity Monitor in SQL Server 2005 Management Studio. Then click to select Process Info. Alternatively use the system stored procedures sp_who or sp_who2 to identify any open connections to the SQL Server computers that house BizTalk Server databases. If there are any processes connected, locate them and terminate them normally; or as a last resort, right-click each process in the Process Info pane in SQL Server Enterprise Manager or SQL Server 2005 Management Studio and click Kill process to terminate the connection.

  9. Additional database processing may be occurring in application databases. If these databases will be restored, ensure that all processing is stopped.

Show: