Purpose
The config_systems command configures the DSC settings for the Teradata system and nodes used for backup and restore jobs. It also sets the selector in the targeted system for ActiveMQ. Nodes are configured automatically after restarting DSMain on the system.
Syntax
config_systems -f|-file File -s|skip_system_config SkipSystemConfiguration
Example
dsc config_systems -f configSystem.xml -s system
Parameters
- f|file filename
- The full path and name of the file containing the necessary configuration parameters.
- s|skip_system_config SkipSystemConfiguration
-
[Optional] Flag indicating whether the systems and node configuration or selector setting is skipped when you run the command. If this option is not specified, then both parts of the configuration (system and selector) are run. Enter one of the following:
- system to avoid configuring Teradata systems and nodes
- selector to avoid setting the selector in the targeted system for ActiveMQ
If you choose the selector option with this parameter, restart Teradata Database using a DSMain restart. - u|user_authentication User
- Required when security management is enabled. Supplies the command with the Viewpoint user, and triggers a password prompt for authentication.
Usage Notes
System nodes are configured by auto discovery.
Item | Description |
---|---|
Component names |
The component name can only use the following characters: 'A-Z', 'a-z', '0-9' and '_'. |
The first character of the component name cannot be '_'. | |
Allowing Incremental Jobs Based on Full or Cumulative Backup Jobs Completed with Errors |
By setting the skip_force_full option in the XML file, you can run an incremental backup job that is based on a prior full or cumulative backup job that completed with errors.
|
By default, the skip_force_full option is false. | |
The skip_force_full option is set system-wide. You cannot use this option on a single-job basis. | |
System Configuration Attributes | The following XML file example shows some system configuration attributes. System configuration is subject to the following restrictions and requirements. |
Setting reset_node_limit to true overwrites node limits with the system's hard and soft limits. | |
Soft and hard limits for insertion of new nodes:
|
|
Soft and hard limits when updating existing nodes:
|
XML File Example
A representative XML file containing system configuration information is shown below.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--****The command below must be on one line.****-->
<dscConfigSystems xmlns="http://schemas.teradata.com/v2012/DSC"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="DSC.xsd">
<system>
<!-- 'system_name' - Required, max 32 characters -->
<system_name>system7</system_name>
<!-- 'tdpid' - Required (unless skipped by option)-->
<tdpid>system7</tdpid>
<!-- 'database_query_method' - Required, accepted values: BASE_VIEW/EXTENDED_VIEW -->
<database_query_method>BASE_VIEW</database_query_method>
<!-- 'streams_softlimit' - Required, number of streams per node per job -->
<streams_softlimit>20</streams_softlimit>
<!-- 'streams_hardlimit' - Required, max number of streams per node-->
<streams_hardlimit>20</streams_hardlimit>
<!-- 'reset_node_limit' - Optional, accepted values: true/false -->
<reset_node_limit>false</reset_node_limit>
<!-- 'skip_force_full' - Optional, accepted values: true/false -->
<skip_force_full>false</skip_force_full>
</system>
</dscConfigSystems>