Windows
- Stop Parasoft DTP Server and Data Collector services, see Stopping DTP Services.
- Run the <DTP_HOME>/bin/backup_config.cmd batch script file.
The script file will generate a backup directory that contains the backed up content at <DTP_HOME>/backup/backup_config-<TIMESTAMP>. The following content is backed up:
- XML configuration files associated with your DTP deployment
- license for DTP and tools
- Team Server configuration
- Custom processors, widgets, and dashboards
- Test configuration files
- [DTP_INSTALL]/tomcat/webapps/grs/custom/* directory
Backing up Custom Configuration Files
In addition to the default content, you can include custom configuration files with the backup by creating a file called backup_config_list_custom.txt and adding it to the [DTP_HOME] directory. This file must explicitly contain relative paths to the configuration files you want to back up--not just to folders.
Linux
- Run <DTP_HOME>/bin/dtpconsole.sh to access the DTP console
- Stop Parasoft DTP Server and Data Collector services, see Stopping DTP Services.
- Run the <DTP_HOME>/bin/backup_config.sh batch script file.
The script file will generate a backup directory that contains the backed up content at <DTP_HOME>/backup/backup_config-<TIMESTAMP>.tar.gz. The following content is backed up:
- XML configuration files associated with your DTP deployment
- license for DTP and tools
- Team Server configuration
- Custom processors, widgets, and dashboards
- Test configuration files
- [DTP_INSTALL]/tomcat/webapps/grs/custom/* directory
Backing up Custom Configuration Files
In addition to the default content, the backup shell script will also back up files and folders specified in the [DTP_INSTALL]/backup_config_list_custom backup file.This file should contain relative paths to files and folders you want to include in the backup. The default list of backed up files and folders are specified in a hidden file at [DTP_HOME]/.backup_config_list.
