Only issue I've ever had was involving tha firewall moreso than vnetd.

Once vnetd was turned on, and appropriate ports were opened on the
firewall, everything worked fine.
However, we had a considerable number of clients with a LOT of data
behind the firewall (staging/development network) and the firewall was a
Enterprise 250, with 100Mb/s interfaces, and the backup traffic killed
it.....the firewall was upgraded, and everything since has been
great.....So regardless of the backbone size, and the connection speed
of the servers you're backing up, you're restricted by the bottleneck of
the firewall.

Are you intenting to add a few clients that will backup through a
firewall using vnetd? Or all of your clients?? <shudder> or just running
the admin console using vnetd???

Cheers,
Paul

> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu 
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of M S
> Sent: March 2, 2005 4:50 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] vnetd - any special requirements or problems
> 
> 
> Hi I am switching Netbackup environment to use vnetd.
> 
> Any negative experience or some special 
> installation/activation requirements 
> that somebody had with veritas network daemon
> 
> Will summarize
> 
> Thanks
> 
> Milan
> 
> _________________________________________________________________
> Scan and help eliminate destructive viruses from your inbound 
> and outbound 
> e-mail and attachments. 
> http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&;
> DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines 
>   Start enjoying all the benefits of MSN(r) Premium right now 
> and get the 
> first two months FREE*.
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
>