|
||
|
|
Overview
Tracker integrates with either Microsoft Access, MySQL, Microsoft SQL Server, or Oracle databases using a standard OLE-DB interface. Utilities are included with Tracker to provide some basic operations (e.g. initialization) which may be required in order to use a database with Tracker. However, backups and other database administration should be performed using the tools that come with the database.
Topics Covered In This Section
Workgroup Management System
Regardless of the database type being used for the workgroups in your Tracker installation, the Workgroup Management System is in Access format and must be backed up on a regular basis.
By default, the Workgroup Management System database file is located at:
installDir\ptadmin\Database\ptadmin.mdb
where installDir is the directory where Tracker was installed (by default, C:\Inetpub\wwwroot\NetResultsTracker).
User Management System
Regardless of the database type being used for the workgroups in your Tracker installation, the User Management System is in Access format and must be backed up on a regular basis.
By default, the User Management System database file is located at:
installDir\ptcommon\Database\ptcommon.mdb
where installDir is the directory where Tracker was installed (by default, C:\Inetpub\wwwroot\NetResultsTracker).
Each workgroup has a database which can be in Access, MySQL, SQL Server or Oracle format. Each workgroup also has an Attachments folder, containing the files attached to the Tracker records. Both the database and the Attachments for each workgroup must be backed up on a regular basis.
Workgroups with Microsoft Access Databases
By default Tracker uses a Microsoft Access database file located at:
installDir\workgroup\Database\Bugtrack.mdb
where installDir is the directory where Tracker was installed (by default, C:\Inetpub\wwwroot\NetResultsTracker), and workgroup is the name of the Tracker workgroup that was installed. There is one database per workgroup.
It is recommended that you back up the database file on a regular basis (e.g. daily) and at a time when it is highly unlikely to be in use (e.g. backups are commonly run early mornings). As with any other Windows file, if the file is open, it cannot be backed up until it is closed. Tracker only accesses the database (opens the file) briefly to handle each request (it is only opened between the time a user clicks on a link or button and the requested web page is returned, it is not left open).
To back up the Access database for a workgroup, copy the file installDir\versionDir\Database\Bugtrack.mdb (as described above) for each workgroup.
You also need to back up the Attachments folder which is located at installDir\workgroup\Attachments for each workgroup.
Over time this file may become quite large. You can attempt to compact this file by using Microsoft Access. It is strongly recommended that you backup the file before attempting this operation.
Workgroups with MySQL Databases (Schemas)
If you are using Tracker with a MySQL database (schema), please refer to the MySQL documentation on recommended administration procedures, such as regular scheduled backups, etc. MySQL databases are not standard files, therefore, a simple file copy or file backup to tape is not sufficient for backing up a MySQL database.
There is one MySQL database (schema) for each Tracker workgroup. By default, the database name is the same as the workgroup name. If the database name is different than the workgroup name, the database name can be found by viewing a workgroup in the Workgroup Management System.
By default, Tracker uses a login with the name NRTracker to access these databases for Tracker operations.
You also need to back up the Attachments folder which is located at installDir\workgroup\Attachments for each workgroup where installDir is the directory where Tracker was installed (by default, C:\Inetpub\wwwroot\NetResultsTracker), and workgroup is the name of the Tracker workgroup that was installed.
Workgroups with Microsoft SQL Server Databases
If you are using Tracker with a SQL Server database, please refer to the SQL Server documentation on recommended administration procedures, such as regular scheduled backups, etc. SQL Server databases are not standard files, therefore, a simple file copy or file backup to tape is not sufficient for backing up a SQL Server database.
There is one SQL Server database for each Tracker workgroup. By default, the database name is the same as the workgroup name. If the database name is different than the workgroup name, the database name can be found by viewing a workgroup in the Workgroup Management System.
By default, Tracker uses a login with the name NRTracker to access these databases for Tracker operations.
You also need to back up the Attachments folder which is located at installDir\workgroup\Attachments for each workgroup where installDir is the directory where Tracker was installed (by default, C:\Inetpub\wwwroot\NetResultsTracker), and workgroup is the name of the Tracker workgroup that was installed.
Workgroups with Oracle Databases
If you are using Tracker with an Oracle database, please refer to the Oracle documentation on recommended administration procedures, such as regular scheduled backups, etc. Oracle databases are not standard files, therefore, a simple file copy or file backup to tape is not sufficient for backing up an Oracle database.
There is one Oracle database for each Tracker workgroup. By default, the database name is the same as the workgroup name. If the database name is different than the workgroup name, the database name can be found by viewing a workgroup in the Workgroup Management System.
By default, Tracker uses a login with the name NRTracker to access these databases for Tracker operations.
You also need to back up the Attachments folder which is located at installDir\workgroup\Attachments for each workgroup where installDir is the directory where Tracker was installed (by default, C:\Inetpub\wwwroot\NetResultsTracker), and workgroup is the name of the Tracker workgroup that was installed.
Direct Database Edits are Not Supported
Although Tracker uses a standard database, it is recommended that you do not directly modify (or even open) the database(s). Doing so may result in serious and perhaps unrecoverable damage to your Tracker data. Directly accessing the database may also lock users out of the system. Support is not provided for Tracker installations in which the database(s) have been modified using anything other than the (unmodified) Tracker web pages that are shipped with the product (unless you were directed to do so by NetResults Technical Support or NetResults Professional Services). If NetResults Technical Support discovers that your data has been directly modified (or your Tracker web pages have been modified), they may require that you reinstall the product and reinitialize the database(s) before providing any further support.
Direct modification of a Tracker database or source pages by users is not supported by NetResults.
NetResults Tracker © 1997-2018 NetResults Corporation. All rights reserved.
Need Support? Chat now...
NetResults Tracker Help
