You might want to consider using a product like SQL Backup (Red-Gate), or
LiteSpeed (Quest), that do compressed database dumps to disk, and then
backing up these compressed dumps as regular files. Your repository can be
on a remote server. Combining full, differential and incremental dumps, you
get terrific coverage with little additional load on the SQL servers.

-Neil


On 1/26/10 7:58 PM, "David Stanaway" <david AT stanaway DOT net> wrote:

> We have a MSSQL server with ~200 very small databases. This takes a very
> long time to backup as each DB spawns a new job that needs to get qued
> then start up the media session etc.
> 
> We used to back it up with Legato pretty quickly, but now the lag is
> quite noticeable and it eats into our maintenance window.
> 
> Is there anything we can do to decrease the lost time between backup
> jobs for a SQL policy with the $ALLDATABASES target with this many
> databases?
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

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