Project Description
This tool backs up the configuration of the BizTalk 'application' servers (not databases). It copies/export settings so the BizTalk app (front-end) servers can be rebuild quickly. This includes config files, application MSIs, binding files, pipeline components etc.

Goal of this tool

This tool was created to ease the process of backing up and restoring a BizTalk group or even to just add a new node to a group.

Latest version

Version 2.0 now supports BizTalk 2013 R2

How does it work?

The tool is simply a command line utility that takes several parameters depending on what you want to back up. It utilize both WMI and the BizTalk
ExplorerOM library to do its work. The following things are 'backed up':

  • BTSNTSvc.exe.config files (both 32 and 64-bit if present)
  • Messaging and Pipeline Component directories
  • Generates a BtsAdminConfiguration.xml file with which hosts, instances, adapters and handlers can be recreated (see
  • Export all current applications to MSIs so they can be restored as needed
  • Export all current application binding files
  • Tracking directory (only custom files like xls, xml, btt etc.

Command line parameters

The following is an explanation of the parameters.

Usage: BTSBackup.exe [-config:path] [-comp:path] [-envconfig:path] [-apps:path] [-bind:path] [-track:path] [-log] [-btsdir:installdir]
    config    - Back up BTSNTSvc.exe.config files to path
    comp      - Back up components (pipeline and messaging)
    envconfig - Generate BtsAdminConfiguration.xml file to path
    apps      - Export all application MSI's to path
    bind      - Export all application binding files to path
    track     - Back up custom tracking(BAM) related files to path
    log       -  Write outout to log file (BTSBackup.log)
    btsdir    - Installation directory of BizTalk
  Path details
    path      - May contain macros like {yyyy-MM-dd}
    Allowed macros
 Sample usage: BTSBackup.exe "-config:c:\backups\{yyyy-MM-dd}\config"

.Net framework

Version 2.0 add support for BizTalk 2013 but that requires .Net 3.5. This might be an issue for any BizTalk 2006 servers that only supports .Net 2.0. Use version 1.x for those situations.


As with all other tools that use the BizTalk ExplorerOM library this tool must be compiled to x86 code. It will run on a 64-bit OS but in 32-bit mode.
Also, it needs to run under an account that has the proper privileges.

Last edited Mar 31, 2016 at 9:20 AM by RudolfHenning, version 9