Archives of the TeradataForum

Message Posted: Thu, 25 May 2006 @ 20:46:19 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Thursday, May 25, 2006 16:30 -->

We are in the process of moving from an MVS-mainframe BAR solution for Teradata to the Veritas NetBackup-Teradata Extension (NBU-TE) solution. I know the benefits will be extremely shorter backup and restore times with the NBU solution due to infrastructure differences.

However, compared to the ease provided by CA-View on the mainframe, it seems considerably more difficult in the NBU-TE environment to determine after the fact what backup job scripts have completed, what database schemas were archived, and whether they were truly successful. This difficulty is due to the way NBU-TE does not display a distinguishable job name in the View Status dialog box, nor does NBU's Activity Monitor, nor does NBU's bplist. Plus, all errors regardless of severity (cc4-cc12) return the same condition code=1 indicating unsuccessful completion. These inadequacies require one to open each job individually to verify what script was being executed, which schemas were included, and whether the cc1 was due to a bypassed table (usually OK), a skipped database (maybe OK), or a total Teradata/client failure (never OK). If one has MANY different backup jobs to verify and they run on varied schedules, this process could be very laborious and time consuming . unless there are some tricks or efficiencies of which I am not aware. This is where you might can help.

Does anyone have suggestions as to how best to setup NBU-TE backup schedules and scripts to streamline the "after the fact" review/verification process of multitudes of backup jobs (e.g. without having to open each job individually to verify which script was being executed, which schemas were being archived, and whether Arcmain returned cc4, cc8, or cc12)? Also, any other advice concerning how best to setup and use NBU-TE that is not included in the meager NBU-TE Administration Guide will also be appreciated.

Thank you.

	<Prev	Next>		<<First	<Prev	Next>	Last>>