Dave,
Did you create a DSN named veritas?  
Did you log onto the server where the SQL agent is installed using the
account that the NB client & SQL agent is using for logon?

After logging on you must enter the command: dbbackup -mssql (if you are
using NT authentication in SQL).  If you are using SQL authentication I
believe you must add one or two more parameters to the dbbackup  command.  
Once you enter the dbbackup -mssql  command, you will get two popup
messages.  Click 'Ok' on both of them.  After clicking 'Ok' on the second
you, you should get a NB window for SQL save & restores.

I am not sure that the $all will work for the DB names but it might.  The
MAXTRANSFERSIZE  and BLOCKSIZE probably shouldn't be 0 as you will not get
the best performance.  I use 4 & 6 respectively and I run SAN & TCP/IP SQL
backups......

Rick Morris
IGT - SAP Basis Administrator
775-448-7293


-----Original Message-----
From: Dave Clark [mailto:dclark AT springboardhosting DOT com]
Sent: Thursday, August 01, 2002 06:05 AM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] Sql client script


I have installed the Veritas Sql client on a win2k Sql server and have the
license installed for the Sql agent on the backup server.
The customer created this script:

OPERATION BACKUP
OBJECTTYPE DATABASE
DATABASE $ALL
MAXTRANSFERSIZE 0
BLOCKSIZE 0
DBMS MSSQL
DSN veritas
ENDOPER TRUE

The backup system reported this error:

Status = none of the requested files were backed up.

File list
---------
veritas_sql.bch

Any Ideas?

Thanks,

DClark