> Situation: Win2k3 SP2 Master and Mutliple SAN Media Servers.
> I have many VM Machines that are doing backups via the lan at this
> stage. VMCB will be looked into later this year.
> 
> Problem I am seeing: In particular, 2 clients have 500 SQL DB's on
> them and the behaviour of NetBackup seems to be:
> 
> 1) A Schedule kicks off for SQL
> 2) Another job kicks in for the Default Application Backup and it
> backs up each single DB

You do realize, right, that the full/incr schedule doesn't actually
back anything up--it just tells the client to run the client script
specified in the selection list?

And that the file should be SQL Server backup commands that are
executed on the client (and can be initiated just as easily from the
client by any other means that suit your needs)?

And that the client initiates a user backup request to the master
which validates the client against allowed/applicable user backup
schedules--_that_ is what initiates the D_A_B job(s)?

So the fix you seek is at the client end.  Break out a Microsoft SQL
Server book and an editor, the Veritas NetBackup for Microsoft SQL
Server Administraotr's Guide (or use the too-simple-to-screw-up
NetBackup client GUI) and change or add a script that does what you
want:  stripes, multi-streaming, blocksize, shared buffers, ...  

Assuming you set the client and policy job limits per the
Administrator's Guide, of course.

> Or is this behaviour I am seeing normal.

It's normal if the script uses the default installation values.  A
backup or SQLServer admin who knows his stuff can make SQL Server
backups rock if the box is capable of it.  As I see others have
said, open the admin guide.


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu