Dave,

One possible cause for this can be name resolving issues.

I can't locate the item, but it was mentioned in a posting to the Veritas
Netbackup Newsgroup quite a while ago.

Make sure you can ping the FQDN of the netbackup server from the client.


HTH,

Brian Briscoe
European OA Support
Visteon Technical Centre, 28/803,
Dunton, England,
Tel  (8738)6214 Ext 01268 406214
Fax (8738)4367 Ext 01268 404367
Email: bbriscoe AT visteon DOT com



> -----Original Message-----
> From: Dave Clark [mailto:dclark AT springboardhosting DOT com]
> Sent: 01 August 2002 14:05
> 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
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>