Restoring with Multi-Stream - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

When archiving/restoring database DBC, the recommendation is to run both archive and restore as single-stream jobs. This recommendation was not enforced in versions previous to Teradata ARC 14.00. Beginning with Teradata ARC 14.00, the user can no longer create multi‑stream archives of database DBC. However, multi‑stream restores of database DBC still support restores from older archives that used multiple streams. For more information, see “Archiving DBC with Multi-Stream” on page 47.

If a multi-stream restore includes database DBC, use the procedure in Table 4 on page 56. When restoring database DBC, use the same number of streams during the restore that were used during the archive.

Note: Using multiple streams to restore database DBC can have unpredictable results, using fewer streams than were used during the archive can cause the DBC restore to fail.

When restoring user data, the same number of streams should also be used during the restore that were used during the archive (single-stream or multi-stream). If the same number of streams (for example, tape drives) are not available on the target system, then you must break up your user data restore job into multiple jobs with fewer streams and run Partial-AMPs restores. For more information, see “Restoring with Partial-AMPs” on page 73.

Whenever database DBC is restored, the post_dbc_restore script must be run to perform conversion activities against the data in database DBC and SYSUDTLIB. To enforce this requirement, Teradata ARC terminates any restore job which includes database DBC after restoring databases DBC and SYSUDTLIB. By terminating the job, Teradata ARC allows the user to run the post_dbc_restore script before restoring any user data.