Archives of the TeradataForum
Message Posted: Thu, 13 Apr 2006 @ 12:24:49 GMT
Subj: | | Re: Experiences with TSM and Teradata |
|
From: | | Harold D. Kleven |
Bill Gregg was wondering why one job runs a little slower than the others, given his physical configuration of BAR servers, etc. Sometimes
factors beyond the physical configuration affect the backup "speed," like the number of "open/close" operations ARCMAIN is performing during the
job. We noticed that our one job that picks up all the "small" tables in our system can't run at the 100GB rate that our jobs that backup the big
tables can: it's simply spending extra time in the 100's of open/close operations.
Hock Lim makes some excellent points regarding open systems backups, and particularly TSM. We were one of the first TSM users in Teradata and
have found that every one of his points is valuable. You do have to have all the technical i's dotted and t's crossed or things simply won't work
well, and sometimes won't work at all, but it's an otherwise very easy implementation and works well. From time to time we spend some (manual)
time reviewing the sequencing and scheduling of jobs to maximize the BAR server utilization but otherwise survive with pretty much a hands-off
approach.
Harold D. Kleven
SUPERVALU - Data Administration
|