Here's my "paper" (quick version):

Pros:
* Saves disk space.  Backups up right to tape.
* Faster. One step, write to tape.
* Calls the same APIs the SQL backup does when it goes
to file.

Cons:
* Cost Money
* Funky interface/setup
   * jobs show up twice for every one job.  There is a
job that kicks off another job that communicates back
to the server (dbbackex I believe is the binary).

--- "Hindle, Greg" <Greg.Hindle AT constellation DOT com>
wrote:
> My boss wants me to write up a paper with the pro's
> and cons of using
> the Netbackup SQL agent. Has anyone out there done
> this? Any help or
> suggestions would be very helpful. We currently have
> SQL dump to a flat
> file and we then back this up to tape but he wants
> to know if this is
> better or should we be using the SQL backup agent
> instead....
>  
>  
> Greg
>  
> 
> 
> 
> >>> The information contained in this e-mail
> transmission is privileged and/or confidential
> intended solely for the exclusive use of the
> individual addressee. If you are not the intended
> addressee you are hereby notified that any
> retention, disclosure or other use is strictly
> prohibited. If you have received this notification
> in error, please immediately contact the sender and
> delete the material.
> 
> 


        
                
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail