Created By: Jason Painter

Manufacturer: Numara Software

Product: Track-It!

Module: Restore

Version(s): 9, 10

Issue Type: Procedure

Effective as of 9 Mar. 2012

Related: TSA000080 

Restore Procedure


Restoring your database is more involved than simply restoring using Management Studio. A full Track-It! backup set includes a number of files that have been changed or created by the user, e.g. configuration files, attachments. This procedure will result in the full backup set being restored to the destination Track-It! server.


Copy the backup set, named Track-It! Backup yyyymmddhhmmss to a local drive on the Track-It! server. 

Download and unzip the TIServerRestore.bat  file to the following directory on the Track-It! Server (default):

C:\Program Files\Numara Software\Numara Track-It!\Track-It! Services\

Open the TIServerRestore.bat file in Notepad.


:: ------------------------------------------------------------------

:: Change the values for the DESTINATION system as needed below:


SET IntegratedSecurity=false


SET TablespaceName=TRACKIT9

SET EnvironmentSuffix=_2


SET DBType=SQLServer

SET DBAdminUser=sa

SET DBAdminPassword=TI_DB_P@ssw0rd

SET DBServer=Server01


SET TISystemRoot=C:\Program Files\Numara Software\Numara Track-It!

SET BackupSetLocation=C:\Backups\Track-It! Backup 20110503012734

:: ------------------------------------------------------------------

Within the dashed lines, make sure the parameter values are correct for your environment:

IntegratedSecurity (MSSQL only): true or false. When true, connect to the database server using the current logged on credentials (must be logged on as an administrator of the database server). When false, the database administrator user name and password must be specified.

TableSpaceName (Oracle only): Name of the Oracle tablespace where the database will be restored.

EnvironmentSuffix (Oracle only): Underscore and number of a schema that is not being used in the Oracle tablespace where the database will be restored.

DBType: SQLServer or Oracle.

DBAdminUser: The current database server's database administrator account.

DBAdminPassword: The current database server's database administrator password. The default is shown if Track-It! installed the instance of MSSQL.

NOTE: The backup may fail with an "Invalid Syntax" error if the specified DBAdminPassword contains special characters, such as ^, $, %, etc.

DBServer: The name of the new database server, or DatabaseServerName\InstanceName if using a named instance of Microsoft SQL Server (where DatabaseServerName\InstanceName is the actual name of the server and the instance), where the database will be restored. 

DBorSIDName: See below, depending on the database back-end being used:

MSSQL: The name of the new database that will be restored. The new database name must not already exist on the destination system, or in the specified named instance.

Oracle: The name of the SID of an existing Oracle database.

TISystemRoot: Make sure the path is correct for your installation of Track-It!.

The path should be the location where the Track-It! Server and Track-It! Services directories are located on the server. By default, it is set to C:\Program Files\Numara Software\Numara Track-It!.

Please note that if Track-It! is installed on a 64-bit server, the path will contain "(x86)" in it, such as C:\Program Files (x86)\Numara Software\Numara Track-It!.

BackupType: If Full is specified, the applications, configuration files, attachments, and the database will be included. Change this to Database if you only want the database to be included in the backup set. If Components is specified, only the applications, configuration files, and attachments are included.

BackupSetLocation: The full path of the backup set, including the name of the backup set folder. Backup sets are named like Track-It! Backup yyyymmddhhmmss. 

Make any necessary changes and then save the batch file.

Before beginning the backup make sure everyone has exited out of Track-It!.

 Double-click to run the batch file.


  • If you see a "System error 1060" in regards to a service not existing, you can disregard this error. The batch file attempts to stop and start two services, one of which may not exist on the server, depending on the installation.
  • If other errors occur, a Track-It-Backup.log file, located under the logged on user's %TEMP% directory, can be reviewed.

Run Technician Client on the server to make sure it logs in properly.