Full System Restore Using the Command Line - BAR - Data Stream Architecture - Follow these steps to do a full system restore of DBC and user data, using the command line.

Prerequisite

When restoring an archive made on a source system with hardware block-level compression, you must install the hardware compression driver package (teradata-expressdx) on all TPA nodes of the destination system. The installation requires a reboot of these nodes. Because it allows the destination system to read the compressed archive, this requirement applies even if the destination system is not set up for hardware compression.

The teradata-expressdx driver package is provided with systems that are equipped with compression hardware.

For additional information, see the Teradata Vantage™ - Advanced SQL Engine Node Software Migration Guide or Teradata® Database Node Software Migration Guide specific to your database version.

These steps wipe the system. Use these steps for a full system restore.

Before you create a restore job, a backup job must have completed either successfully or with a warning.

You must create four restore jobs, one for DBC only and three from the all DBC user data backup (SYSLIB, TD_Server_Database, and all other data).

On the destination system, run SYSINIT with options appropriate to your system.
On the destination system, check the Time Zone setting status , and disable the setting if it is enabled.
On the destination system, start the DBS Database Initializing Program (DIP) and run the following:
- [Advanced SQL Engine / Teradata Database 15.0 and later] Run the DIPMIG script, which runs DIPERRS, DIPDB, DIPVIEWS, DIPVIEWSV, and DIPBAR.
- [Teradata Database 14.10] Run the DIPERRS, DIPVIEWS, and DIPBAR scripts (1, 4, and 21).

Check the activation status of the destination system using the dsc list_components command, dsc list_components -t system, and do one of the following: [DSA 16.10 and later]

If the destination system is configured and enabled, run a config_systems command with the skip parameter set to selector, dsc config_systems -f configsystem.xml -s selector.

If the destination system is not configured, add the system using the config_systems command, dsc config_systems -f configsystem.xml. See the following sample configsystem.xml file.

<?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>

[Prior to DSA 16.10]

If the destination system is already configured and activated in DSA, deactivate the system, add the system again, and reactivate the system. Re-adding the system repopulates the connectinfo macro in the SYSBAR database with the JMS connection information. See Disabling a System or Target Group, Configuring a System, and Enabling a System or Target Group.
If the destination system is not configured in DSA, the system must be added and activated before the restore can proceed. See Configuring a System and Enabling a System or Target Group.

On the destination system, start DSMain from the Database Window (DBW) console supervisor screen by entering: start bardsmain -d DSCName , where DSCName is the unique name of your DSC server
[DSA 16.0 or earlier] After DSMain starts, activate the system with this command: dsc enable_component – n DBSsystemName –t SYSTEM
Enable logons for the DBC user only. On the destination system, enter the following from the DBW console supervisor screen: enable dbc logons

Create a DBC-Only restore job, excluding all children of DBC, for example: dsc create_job -n Restore-DBC-Only -f RestoreDBCOnlyJob.xml

Sample RestoreDBCOnlyJob.xml file:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dscCreateJob xmlns="http://schemas.teradata.com/v2012/DSC">
  <job_instance>
    <job_name>Restore-DBC-Only</job_name>   
    <job_description>Restore DBC only and exclude all child objects</job_description>
    <job_type>RESTORE</job_type>
    <job_state>ACTIVE</job_state>
    <auto_retire>false</auto_retire>
    <backup_name>DBC-Only</backup_name>
    <backup_version>0</backup_version>
    <all_backup_objects>true</all_backup_objects>
  </job_instance>
  <source_media>1_5_drives </source_media>
  <target_tdpid>systemname</target_tdpid>
  <job_options>
    <enable_temperature_override>false</enable_temperature_override>
    <temperature_override>DEFAULT</temperature_override>
    <block_level_compression>DEFAULT</block_level_compression>
    <disable_fallback>false</disable_fallback>
    <query_band></query_band>
    <dsmain_logging_level>Debug</dsmain_logging_level>
    <reblock>false</reblock>
    <run_as_copy>false</run_as_copy>
  </job_options>
</dscCreateJob>

When prompted, enter logon credentials:

Option	Description
Target username	Current DBC user for the target DBS.
Target password	Current DBC password for the target DBS.
Is this Restore job a DBC restore?	y
Password for the backup	DBC password of the source system at the time the backup save set was generated.

Run the job. dsc run_job -n Restore-DBC-Only After the DBC restore job is complete, the DBC password is set to the DBC password of the source system. The DBC database must restore successfully before you can restore user data.

Create a restore job for SYSLIB only: dsc create_job -n Restore-SYSLIB -f R-Syslib.xml

Important: all_backup_objects must be false when processing individual object restore or copy. If all_backup_objects is false and an objectlist is not provided, tables can be lost.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dscCreateJob xmlns="http://schemas.teradata.com/v2012/DSC">
    <job_instance>
        <job_name>R-Syslib</job_name>
        <job_description></job_description>
        <job_type>RESTORE</job_type>
        <job_state>ACTIVE</job_state>
        <auto_retire>false</auto_retire>
        <objectlist>
            <objectinfo>
                <object_name>SYSLIB</object_name>
                <object_type>DATABASE</object_type>
                <parent_name>DBC</parent_name>
                <parent_type>USER</parent_type>
                <object_attribute_list>
                    <includeAll>false</includeAll>
                </object_attribute_list>
            </objectinfo>
        </objectlist>
        <backup_name>DBC-ALL</backup_name>
        <backup_version>0</backup_version>
        <all_backup_objects>false</all_backup_objects>
    </job_instance>
    <source_media>target1</source_media>
    <target_tdpid>sdt12687</target_tdpid>
    <job_options>
        <enable_temperature_override>true</enable_temperature_override>
        <disable_fallback>false</disable_fallback>
        <query_band></query_band>
        <dsmain_logging_level>Error</dsmain_logging_level>
        <reblock>false</reblock>
        <run_as_copy>false</run_as_copy>
        <skip_archive>false</skip_archive>
        <skip_stats>false</skip_stats>
        <concurrent_bld_per_tbl>5</concurrent_bld_per_tbl>
    </job_options>
</dscCreateJob>

Run the job. dsc run_job -n R-Syslib

Create a DBC-All restore job for user data, including all children of DBC except SYSLIB and TD_SERVER_DB: dsc create_job -n Restore-DBC-All -f RestoreDBCAllJob.xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dscCreateJob xmlns="http://schemas.teradata.com/v2012/DSC">
    <job_instance>
        <job_name>Restore-DBC-All</job_name>
        <job_description></job_description>
        <job_type>RESTORE</job_type>
        <job_state>ACTIVE</job_state>
        <auto_retire>false</auto_retire>
        <objectlist>
            <objectinfo>
                <object_name>DBC</object_name>
                <object_type>DATABASE</object_type>
                <object_attribute_list>
                    <includeAll>false</includeAll>
                </object_attribute_list>
                <exclude>
                    <excludeobjectinfo>
                        <object_name>SYSLIB</object_name>
                        <object_type>DATABASE</object_type>
                    </excludeobjectinfo>
                    <excludeobjectinfo>
                        <object_name>TD_SERVER_DB</object_name>
                        <object_type>DATABASE</object_type>
                    </excludeobjectinfo>
                </exclude>
            </objectinfo>
        </objectlist>
        <backup_name>DBC-ALL</backup_name>
        <backup_version>0</backup_version>
        <next_incremental_restore>false</next_incremental_restore>
        <all_backup_objects>true</all_backup_objects>
    </job_instance>
    <source_media>target1</source_media>
    <target_tdpid>abutera</target_tdpid>
    <job_options>
        <enable_temperature_override>true</enable_temperature_override>
        <disable_fallback>false</disable_fallback>
        <query_band></query_band>
        <dsmain_logging_level>Debug</dsmain_logging_level>
        <nowait>true</nowait>
        <reblock>false</reblock>
        <run_as_copy>false</run_as_copy>
        <skip_archive>false</skip_archive>
        <skip_stats>false</skip_stats>
        <concurrent_bld_per_tbl>5</concurrent_bld_per_tbl>
    </job_options>
</dscCreateJob>

When prompted, enter logon credentials and run the job. dsc run_job -n Restore-DBC-All

Create a restore job for the TD_SERVER_DB database: dsc create_job -n R-TDSERVER -f R-TDSERVER.xml

Important: all_backup_objects must be false when processing individual object restore or copy. If all_backup_objects is false and an objectlist is not provided, tables can be lost.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dscCreateJob xmlns="http://schemas.teradata.com/v2012/DSC">
    <job_instance>
        <job_name>R-TDSERVER</job_name>
        <job_description></job_description>
        <job_type>RESTORE</job_type>
        <job_state>ACTIVE</job_state>
        <auto_retire>false</auto_retire>
        <objectlist>
            <objectinfo>
                <object_name>TD_SERVER_DB</object_name>
                <object_type>DATABASE</object_type>
                <parent_name>DBC</parent_name>
                <parent_type>USER</parent_type>
                <object_attribute_list>
                    <includeAll>false</includeAll>
                </object_attribute_list>
            </objectinfo>
        </objectlist>
        <backup_name>DBC-ALL</backup_name>
        <backup_version>0</backup_version>
        <all_backup_objects>false</all_backup_objects>
    </job_instance>
    <source_media>target1</source_media>
    <target_tdpid>sdt12687</target_tdpid>
    <job_options>
        <enable_temperature_override>true</enable_temperature_override>
        <disable_fallback>false</disable_fallback>
        <query_band></query_band>
        <dsmain_logging_level>Error</dsmain_logging_level>
        <reblock>false</reblock>
        <run_as_copy>false</run_as_copy>
        <skip_archive>false</skip_archive>
        <skip_stats>false</skip_stats>
        <concurrent_bld_per_tbl>5</concurrent_bld_per_tbl>
    </job_options>
</dscCreateJob>

Run the job. dsc run_job -n R-TDSERVER
On the destination system, start the DIP and run the DIPALL script.
If you disabled the Time Zone setting on the destination system, enable it .
On the destination system, from the DBW console supervisor screen, enable logons for all users. enable logons