16.20 - Restore Compared to Copy - Teradata Vantage NewSQL Engine

Teradata Vantage™ NewSQL Engine Node Software Migration Guide

prodname
Teradata Database
Teradata Vantage NewSQL Engine
vrm_release
16.20
created_date
March 2019
category
Administration
Configuration
Installation
featnum
B035-5942-162K

RESTORE and COPY are the two ARC commands that move data from an archive to a Teradata Database system. However, only the RESTORE command can be used for full-system migrations.

Restoration of database DBC prepares the destination system to expect all user data from the source system with the database and table IDs contained in the original archive. Use the RESTORE command for user data only after the first restoration of database DBC and only once. After restoring user data from the archive, run the post_data_restore script.
Creating new databases or tables after executing the RESTORE command yields new IDs that did not exist in the original archive. In such cases, you cannot use the RESTORE command again to move the additional databases, because the database and table IDs no longer match. Instead, you must use the COPY command followed by the post_data_restore script. For information about using the COPY command to perform a partial data migration without restoration of database DBC, see Teradata® Archive/Recovery Utility Reference, B035-2412.

RESTORE Job Scripts

The following table provides some examples of the commands that might be included in your restore job scripts. These are only the ARC commands and are not complete scripts.

You must revalidate referential constraints.
Example Commands
If you have permanent journals, re-create the journal dictionaries using these commands that exclude database DBC. The journal data is not restored. RESTORE DICTIONARY TABLES ALL FROM ARCHIVE,

RELEASE LOCK,

FILE=JNLARCH:

Commands to restore the data tables without restoring database DBC and other databases that are recreated by DIP scripts.

These commands restore user databases, secondary indexes, and fallback.

RESTORE DATA TABLES (DBC) ALL,

EXCLUDE(DBC), EXCLUDE(TD_SYSFNLIB), EXCLUDE(CRASHDUMPS), EXCLUDE(DBCEXTENSION), EXCLUDE(SYSBAR), EXCLUDE(SYSLIB), EXCLUDE(SYSSPATIAL), EXCLUDE(SYSUDTLIB),

RELEASE LOCK,

FILES=ARCHIVE;

Release the host utility locks with this command. RELEASE LOCK (DBC) ALL;
You must revalidate referential constraints with these commands. REVALIDATE REFERENCES FOR (DBC) ALL,

EXCLUDE (DBC), (TD_SYSFNLIB)

RELEASE LOCK;