Forum Discussion

noazara's avatar
noazara
Level 6
11 years ago

netbackup bpcd

Hi Folks,

I am reading the NBU admin guide both windows and unix and process flow.

 

However it is not clear regarding the process happening on clients.

1.We have 6.5 client.When bpbrm process on media server contact the client.Then what happens on client side for windows client?

My observation as per reading manuals :When bpbrm process on media server contact the client, it check the client services file.According to the services file entries, it tries to connect to vnetd process.(vnetd port shud be open).Then vnetd process hands over the connection to NBU client service which starts the bpcd process.

Is my above observation correct?

2. vnetd process on client opens the vnetd port or vnetd port starts the vnetd process????

3.Where we have bpcd port usage above?

 

NBU Client version is 6.5

windows client 2000.

7.1.x and Earlier
Backup and Recovery
NetBackup
Solaris

8 Replies

Sort By
Replies have been turned off for this discussion
  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    Yep vnetd on client connects to bpcd port which then initiates bpbkar (or bpfis first - depending on type of backup). On 7.1 onwards PBX does this instead of vnetd.

    Process flow for 7.x - note that vnetd -> bpbkar on client side does not show bpcd in the middle of that process flow in this diagram

    http://www-secure.symantec.com/connect/sites/default/files/users/user-2271551/process%20flow_0.jpg

     

    This is also very good

    https://www-secure.symantec.com/connect/sites/default/files/NBU%207.x%20process%20flow%20QRC_1.pdf

  • noazara's avatar
    noazara
    Level 6
    11 years ago

    Thanks Revaroo,

     

    1..What is this NBU client service  use in backup process on windows?

     

    2. vnetd process on client opens the vnetd port or vnetd port starts the vnetd process????

    3.Where we have bpcd port usage above?

  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    I've already been through this with you on private message under your other alias.

  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    Its all in those links. vnetd runs as a port service from in 6.5 in 7.x it becomes a standalone process that listens on a port. That's all you need to know.

    netstat -a | grep 13724   will tell you if it's running on unix

    netstat -a | findstr 13724   will tell you if it's running in Windows.

     

    Here's the port guide too:

    http://www.symantec.com/business/support/index?page=content&id=TECH136090

     

  • noazara's avatar
    noazara
    Level 6
    11 years ago

    Hi Sir,

     

    If you can reply on below query of 1,2,3,4,5,6, ,That will be very helpful.

     

    First NBU 6.X:

    1....On windows:bpbrm from media server contacts clients bpcd process.For this what exactly happens on client.?

    2.....Bpbrm process from media server contacts vnetd process first?for this first vnetd port is contacted or vnetd process?vnetd process is contacted first or vnetd port?

    3....Then vnetd process transfers it to NBU Client service and that service starts BPCD process.Am i correct?

    4....Here in 6.X how bpinetd .exe was called NBU client service?

    Now NBU 7.X,

    5....bpcd process runs all the time.bpbrm contacts pbx port first or pbx process?

    6.....what is NBU CLIENT SERVICE here?

  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    Those questions should be in a new thread

    1) Client receives a request from bpbrm through bpcd (via vnetd on 6.x and pbx from 7.1), bpcd then deals with that request, so it starts a bpbkar process on the client (or a bpfis process if it needs to snapshot)

    2) All communication is done using ports. if vnetd is running as standalone (a process) on 7.1 or higher, it still listens on the port 13724

    3) Pretty much yes.

    4) Yes bpinetd is NBU Client Service - have a read of this :

    http://www.symantec.com/business/support/index?page=content&id=TECH136790

    5) bpcd process from 7.1 (or it may be 7.0.1 - I forget) always runs as a process, prior to this it's configured as a port.

    6) see point 4