16.10 - Backing Up the DSC Repository and Configuration When Upgrading - Data Stream Architecture - Data Stream Extensions

Data Stream Extensions Installation, Configuration, and Upgrade Guide for Customers

Data Stream Architecture
Data Stream Extensions
August 2017

The DSC repository stores all DSA data, including configuration definitions and settings, job definitions, job status, and job history. Protecting the data in the DSC repository is critical. Without the DSC repository, database backup data sets cannot be restored.

It is very important to save copies of the following configuration information before performing an upgrade.
  • The backup repository configuration
  • The information prompted by the installation scripts for the DSC, ClientHandler, and BARCmdline
  • The information required by the /tmp/dsainputs template if you are using PUT
Most of this information is in the properties files saved in /etc/opt/teradata/dsa.
Important: If you change the DSC name during the upgrade you must repeat the backup when you are done.

Use the following procedure to back up the DSC repository.

  1. Run the config_repository_backup command followed by the parameters to configure a target group for the DSC repository backup and schedule a DSC repository backup.
    Parameter Description
    f|file filename The full path and name of the file containing the necessary configuration parameters.
    u|user_authentication User Required when security management is enabled. Supplies the command with the Viewpoint user, and triggers a password prompt for authentication.
  2. Type dsc export_repository_backup_config -f export_repository_backup_config.xml .
    You need to run export_repository_backup_config every time the configuration for repository backup is changed.
    Keep export_repository_backup_config.xml in a safe, known location to be imported back into DSC in case of a disaster.
  3. Type dsc run_repository_job -t backup, and press Enter to run a DSC repository backup.
    The run_repository_job command can only be initiated if no operational jobs are running.