No RESTART During Write - Tivoli

Teradata Extension for Tivoli Storage Manager Administrator Guide

Product
Tivoli
Release Number
16.20
16.10
Published
May 2017
Language
English (United States)
Last Update
2019-03-22
dita:mapPath
beb1489436039198.ditamap
dita:ditavalPath
beb1489436039198.ditaval
dita:id
wkq1486409855180
Product Category
Teradata Tools and Utilities

Teradata Access Module for Tivoli uses a transactional model when creating new storage objects. This means that all changes are lost (with the exception of file segment zero, F0000) if an ARCMAIN job abnormally terminates before committing the transaction. The result is a rollback, meaning that the backup job cannot be restarted from the point of failure. Rollbacks also occur if the Teradata Database resets during a backup operation because the Teradata Access Module for Tivoli and ARCMAIN are unable to coordinate checkpoint and repositioning activities. For example, a tpareset on the Teradata Database causes in-progress backup jobs to fail.

This limitation does not apply to READ operations, such as restore jobs (ARCMAIN RESTORE or COPY statements). If an ARCMAIN restore job ends abnormally, the RESTART and RESTARTLOG options restart the job at the point of failure, provided no other complications occurred.