Backup and Restore

Different artifacts should be backed up depending on the scenario:

  • Setting up an alternative server computer. This is useful when you want to set up an alternative server computer, for example in case of disaster recovery scenarios. In such a case, the server can be in a different location with network access to the devices.

  • Reproducing the same environment from one computer to another for testing / debugging.

  • Regular operational activities. Backing up log files and RFIDsink data. This backed-up data might be needed as part of operational / maintenance activities and useful during the debugging of issues on another computer.

In the case of setting up an alternative server computer, we recommend that you perform all the following operations to make sure that the environments are identical.

In most cases, the configuration files need no modification. Therefore there is no need to back them up unless some value has been explicitly changed. The following table lists the configuration files, their locations, and how they are used. You should back up these files depending on the changes made to them and on their relevance to the scenario.

File Location Usage



Used during server bootstrapping.

Contains the RFIDstore location.

Contains the logging information for particular server components.



For most scenarios, this file does not need to be modified. The only time when it may become necessary to modify the rfidservices.exe.config file is in rare situations where users need to troubleshoot Windows Communication Framework (WCF) connectivity issues in the BizTalk RFID service.



BizTalk Server RFID uses the web.config file to configure the interaction between the BizTalk RFID service and Internet Information Services (IIS). (This file is not relevant for non-Windows Server installations.)

A master copy of the web.config file exists in the %RFIDINSTALLDIR%\bin folder. You should not modify the master copy in any way because it is used as the source file for all new RFID processes and device providers. When you create a process or register an RFID provider, the master file is copied to the specific folder that is created for each process under the Processes folder or RFID provider under the Providers folder.

There is no need to back up this file unless it has been modified. See web.config File ( for more details.



This config file contains the settings for the tools: RFID Manager, RFID Client Console, and the RFID tray application.

Modifications to this file are usually done to the client connection time-outs and log mode.

This affects only the client computers.

This section discusses the RFID device-related information (assemblies and configuration settings) that can be backed up from one computer and re-used on another computer.

Name Operation description Action

Device provider

Backing up all required device provider-related assemblies

Obtaining the device provider settings

Adding a provider on the new computer

Back up contents from the %RFIDINSTALLDIR%\Providers folder.

If the provider runtime or initialization properties have been changed, they need to be re-applied.

Use RFID Manager or the object model (OM) to load the provider.

Device settings

Backing up device settings (properties)

Re-creating the device information on the new computer

Export device settings.

Use RFID Manager to import the device information. If the IP address needs to be modified, this can be done by changing the device properties from RFID Manager.

This section discusses the RFID process-related information (assemblies and configuration settings) that can be backed up from one computer and re-used on another computer.

Name Operation description Action

RFID process

Backing up the RFID process properties – mode, components, binding

Export RFID process settings by using RFID Manager, RFIDClientConsole. Refer to Export and Import of RFID Processes.

Event handler assemblies

Backing up the set of event handler assemblies added as components in the RFID process pipeline

Back up contents from the %RFIDINSTALLDIR%\Processes folder.

The event handler private assemblies for each RFID process are found in the subfolder: \Processes\<RFID Process>\bin

Copy the event handler private assemblies after the RFID process has been imported to the new server.

This section discusses the SQL Server information that can be backed up from one computer and re-used on another computer.

RFIDstore database

Database creation should be handled by installer.

Importing the devices and processes automatically populates the tables.

Backing up the device versions table will be useful to track any device property changes.

RFIDsink database

Back up the data from the TagEvents, TagListEvents, and GenericEvents tables.


The policies and vocabularies should be backed up.

Custom databases

Any custom databases used in the context of your application or event handlers should be backed up.

This section discusses log files that should be backed up from one computer for troubleshooting or debugging analysis at a later time. Usually the log files for a two-week period will be useful to maintain for troubleshooting issues.

RFID service logs

Back up the logs from %RFIDINSTALLDIR%\Logs.

RFID process logs

Back up the log file for each RFID process from \%RFIDDATADIR%\Processes\<ProcessName>.

Provider logs

Back up the log files for each device provider from %RFIDDATADIR%\Providers\<ProviderName>.