No.  We haven't been concerned about the total number bytes transferred.  Our
focus has been on the time it takes to complete the backup and whether the
backup is successful.  The compression algo used by SQLBactrack seems to be much
more efficient than standard compression used by the ADSM client.  We can
backup/restore a 25Gb Oracle database in less than 1 1/2 hours over a 16Mb Token
Ring network.  Not bad in my book.

Kenton




Richard Cowen <richard.cowen AT VTMEDNET DOT ORG> on 02/24/2000 03:08:41 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Kent Maguire/allianzlife)
Subject:  Re: SQL Backtrack



>We've implemented a simple ksh script that is invoked by the ADSM scheduler.
>The script calls the SQLBacktrack backup job, checks the return code, and takes
any appropriate actions (e-mail, page, etc ...).  Error output and job log data
is appended to the $ERR and $LOG variables for historical reference.  This
solution works well for us and took little time to implement.  Example:
>


Does it report total bytes transferred ?
--
Richard
Richard