Restarting an restore operation causes Teradata ARC to:
- Reposition the input archive file at the data block indicated in the last restart point recorded in the restart log before the failure occurred.
- If the AMP configuration changed (AMPs are online before the failure but offline afterward), restart begins with the last table being archived before the failure.
- Rebuilding the deferred build list is unnecessary, because the deferred build list remains intact after a Teradata Database restart.
If the failure occurred during a restore of database DBC, repeat the entire restore operation, including reinitializing the Teradata Database. Some options (for example, ABORT, HALT, and PAUSE) can affect whether Teradata ARC stops, but the default is to try again after the system recovers.