Video Screencast Help

port and process

Created: 12 Aug 2012 • Updated: 12 Aug 2012 | 6 comments
This issue has been solved. See solution.






The acsd (Automated Cartridge System) daemon runs on the NetBackup media server and communicates mount and unmount requests to the host that controls the ACS robotics.



The NetBackup ACS storage server interface (SSI) event logger acssel logs events.



The NetBackup ACS storage server interface (SSI) acsssi communicates with the ACS library software host. acsssi processes all RPC communications from acsd or from the ACS robotic test utility that are intended for the ACS library software.



The Automatic Volume Recognition process handles automatic volume recognition and label scans. The process allows NetBackup to read labeled tapes and assign the associated removable media requests to drives.



The process for the NetBackup Bare Metal Restore Master Server daemon.



The NetBackup Client daemon, this process issues requests to and from the master server and the media server to start programs on remote hosts.

On UNIX clients, bpcd can only be run in stand-alone mode.

On Windows, bpcd always runs under the supervision of bpinetd.exe. NetBackup has a specific configuration parameter for bpcd: if the port number is changed within the NetBackup configuration, the software updates the port number in the services file as well.

What is the relation between port and process? bpce is a port or a process or daemon/services.I am very confused in this. Really !!!!sad

Comments 6 CommentsJump to latest comment

revarooo's picture

Process is the running program. The port is a way for other systems/process to communicate to that particular process. There's not always a need for a program to be listening on a port.

For example bpbrm on a media server has to request bpbkar to start, so it connects to bpcd on 13782 (via PBX 1556) then bpcd starts bpbkar.

bpcd is a program that when running has a process associated to it and it also listens on a port for incoming communications.

mph999's picture

A process is a 'program' that runs on your server.

Multiple process make up NetBackup.

Consider two servers - a media server and a client server:

Perhaps the media servr wishes to communicat to the client via PBX.

On the client the PBX process is waiting for 'something' to contact it, but it is waitin behind a little front door, and on this door is number 1556.

So you can consider ports as 'little doors'.

Before you ask, you can consider services (windows thing), daemons and processes as the same thing.

Technically, you could probably say a daemon is something that is always running (eg.bprd), whereas a process is something that is started when needed, eg, bptm.


Regards,  Martin
Setting Logs in NetBackup:
Marianne's picture

Where did you find the info in your opening post? Info seems to be O-L-D and longer applicable to NBU 7.x.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

NIKHIL2346565959's picture

@Marianne:Above is not  applicable to NBU 7.x?

Marianne's picture

Please always include the document name or URL that you are quoting from? That way we are all on the same page... wink 
We are really happy that you started reading, but please ensure that you are reading current documentation (the other day you were quoting from a 5.0 manual).

The port numbers in your opening post are correct, but NBU 7.x processes do not connect directly to those port numbers.

For example - bpcd. From the TechNotes that we have shared previously with you (e.g. ) we know that 6.0 up to 7.0 connect to bpcd (13782) via vnetd (13724). As per Martin's excellent explanation - see vnetd as the 'door' that is used for connection.
As from NBU 7.0.1, connection to bpcd (13782) will use PBX (1556) as the 'door'.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

NIKHIL2346565959's picture

so in NBU 6.5,WE HAVE bpinetd for windows and inetd,xinetd for unix.

in NBU 7.1,we have these services as standalone

These standalone services is both in case of windows and unix?