 |
 |
Archives of the TeradataForum
Message Posted: Thu, 13 Apr 2006 @ 17:46:56 GMT
| Subj: | | Re: Experiences with TSM and Teradata |
| |
| From: | | Gregg, Bill |
| | "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." | |
We have seen that the small jobs spend more time mounting tapes than running the archive.
The jobs that piqued my interest involved cluster archiving a 1+TB table. The job was divided into 8 cluster jobs; each ends up archivng a very
similar number of rows/volume to its respective tape. One of the tapes is running at 80% the thruput of its siblings. Other jobs that cluster
archive 3-400 gb volumes show this same phenomenon.
Rgrds,
Bill Gregg
Ford Teradata DBA Team
| |
