This was a little tricky when we did it here some months back.  The following 
is an email I sent to my coworker after we got it working:

FYI the following is what I did in NetBackup for backing up client atuprw01.  
The same has been done for clients dswadns1 and dswadns2 substituting those 
names.

     Open Netbackup Java GUI (WindowsXP desktop to the NB Master server)
     Go to Host Properties
     Go to Master Servers
     Double click on atubks01 (NB master server)
     In Master Server Properties box go to Client Attributes
     Click Add
     Type in name of client (atuprw01) and hit enter to add it to list.
     Select (highlight) the client from list
     Under BPCD Connect Back click the VNETD Port radio button
     Click OK.
     Exit and you're done with the GUI.
     After that at command line on master run "bprdreq  -rereadconfig".      
(Note - this worked but manual and Datalink indicated bouncing daemons is the 
only SURE way to do it - Datalink said it works "sometimes".)

Also for above to work Network Admin must open the following ports on the 
internal firewall:
Media >> Client
13782 ?(bpcd)

Client >> Media
13724 ?(vnetd)

Media being the media server (atubks01 in this case).

What threw me off until help from this list was that there is another place in 
the GUI that talks about firewall that has absolutely nothing to do with the 
above.

A final note.  One my clients was still at 3.4 when we did this and we found 
that this only works for 4.5 and above so had to update that client.

Hope this helps.

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces 
at mailman.eng.auburn.edu] On Behalf Of Clooney, David
Sent: Friday, August 25, 2006 7:07 AM
To: ida3248b at post.cybercity.dk; Dave Lowenstein; veritas-bu at 
mailman.eng.auburn.edu
Cc: veritas-bu-bounces at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] vnetd question

 was under the impression that all comms from client > media uses vnetd
13724  when being utilised .

It's the whole point of it I think.

Regards

Dave


-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of
ida3248b at post.cybercity.dk
Sent: 25 August 2006 11:40
To: Dave Lowenstein; veritas-bu at mailman.eng.auburn.edu
Cc: veritas-bu-bounces at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] vnetd question

Hello Dave

You will need to open for 13724 (data port) media to client if you want
to do restores.

But looks like the client isn't using vnetd

Regards
Michael

On Thu, 24 Aug 2006 15:58:08 -0700, Dave Lowenstein wrote
> I'm trying to make sure that netbackup 5.1 will work through a 
> firewall with minimal ports being opened.
> 
> What ports need to be open on the firewall if filtering by destination

> port:
> 
> Media >> Client
> 13782  (bpcd)
> 
> Client >> Media
> 13724  (vnetd)
> 
> If the client needs to run user backups/restores, then the following 
> port will also need to be opened:
> Client >> Master
> 13720  (bprd)
> 
> Right? So I'm testing this out between two hosts with some more 
> liberal firewall rules than above. Backups are working fine, restores 
> are working fine.
> 
> I believe I have all the vnetd stuff set correctly, although every 
> piece of documentation I find shows a slightly different gui interface

> than what I'm seeing.
> 
> Why am I still seeing it talking back and forth between media server 
> and client with randomly selected destination ports (like 852 and 
> 811)? There's also a fair amount of icmp going on back and forth 
> between the two, which I'd like to be able to close down.
> 
> client -> server        TCP D=13724 S=852 Ack=392120625 
> Seq=931198138 Len=0 Win=49680 client -> server        TCP D=13724 
> S=852 Push Ack=392120625 Seq=931198138 Len=2 Win=49680       server -
> > client          TCP D=852 S=13724 Ack=931198140 Seq=392120625 
> Len=0 Win=33118       server -> client          TCP D=852 S=13724 
> Push Ack=931198140 Seq=392120625 Len=2 Win=33120         client -> 
> server        TCP D=13724 S=852 Ack=392120627 Seq=931198140 Len=0
Win=49680
>          client -> server        TCP D=13724 S=852 Push 
> Ack=392120627 Seq=931198140 Len=2 Win=49680       server -> client   
>        TCP D=852 S=13724 Ack=931198142 Seq=392120627 Len=0 Win=33120 
>         client -> server        TCP D=13724 S=852 Push Ack=392120627 
> Seq=931198142 Len=21 Win=49680       server -> client          TCP 
> D=852 S=13724 Push Ack=931198163 Seq=392120627 Len=33 Win=33120      
>    client -> server        TCP D=13724 S=852 Ack=392120660 
> Seq=931198163 Len=0 Win=49680         client -> server        TCP 
> D=811 S=13782 Push Ack=1618165286 Seq=912667687 Len=2 Win=49680      
>  server -> client          TCP D=13782 S=811 Ack=912667689 
> Seq=1618165286 Len=0 Win=34500
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


--
Cybercity Webhosting (http://www.cybercity.dk)

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



Notice to recipient:
The information in this internet e-mail and any attachments is confidential and 
may be privileged. It is intended solely for the addressee. If you are not the 
intended addressee please notify the sender immediately by telephone. If you 
are not the intended recipient, any disclosure, copying, distribution or any 
action taken or omitted to be taken in reliance on it, is prohibited and may be 
unlawful.

When addressed to external clients any opinions or advice contained in this 
internet e-mail are subject to the terms and conditions expressed in any 
applicable governing terms of business or client engagement letter issued by 
the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., 
London Branch and Banc of America Securities Limited are authorised and 
regulated by the Financial Services Authority.


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