# /usr/openv/netbackup/bin/bpps -x
On Netbackup Master Server:
http://support.veritas.com/docs/281789
The following is a listing of the services that need to be running on a NetBackup 6.0 master server:
- Adaptive Server Anywhere - VERITAS_NB - ASA Database service (NB_dbsrv)
- Netbackup Client Service (bpcd)
- NetBackup Compatibility Service (bpcompatd)
- NetBackup Database Manager (bpdbm)
- NetBackup Device Manager (ltid)
- Netbackup Enterprise Media Manager (nbemm)
- NetBackup Job Manager (nbjm)
- NetBackup Notification Service (nbnos)
- Netbackup Policy Execution Manager (nbpem)
- Netbackup Request Manager (bprd)
- NetBackup Resource Broker (nbrb)
- NetBackup Service Layer (nbsl)
- NetBackup Service Monitor (nbsvcmon)
- Netbackup Volume Manager (vmd)
- Veritas Private Branch Exchange (pbx_exchange)
On Netbackup Media Server:
http://support.veritas.com/docs/282159
The following is a listing of the services / daemons which should be running by default on a NetBackup 6.0 media server:
- Netbackup Client Service (bpcd)
- NetBackup Compatibility Service (bpcompatd)
- NetBackup Device Manager (ltid)
- NetBackup Notification Service (nbnos)
- NetBackup Service Layer (nbsl)
- NetBackup Service Monitor (nbsvcmon)
- Netbackup Volume Manager (vmd)
- Veritas Private Branch Exchange (pbx_exchange)
On Netbackup Client:
http://support.veritas.com/docs/282162
There are no additional daemons or services that run on a NetBackup 6.0 client. Checking to see if the client software is running is similar to NetBackup 5.x and earlier versions. It is only necessary to check for the existence of the NetBackup Client Service (bpcd).
The NetBackup client software registers itself with inetd or xinetd on UNIX or Linux clients. The "netstat -a" command can be used to verify these daemons are in LISTEN status, indicating they are listening for incoming connections.
# netstat -a | grep bpcd
# netstat -a | grep bpjava-msvc
# netstat -a | grep vnetd
# netstat -a | grep vopied
沒有留言:
張貼留言