Determining if the PBX daemon or service is available
If NetBackup does not work as configured, a required NetBackup service may have stopped. For example, backups may not be scheduled or may be scheduled but are not running. The type of problem depends on which process is not running.
When a NetBackup service is not running and another process tries to connect to it, messages similar to the following appear in /opt/VRTSpbx/log (UNIX) or install_path\VxPBX\log(Windows). The unified logging originator for PBX is 103 and the product ID is 50936.
05/17/10 9:00:47.79 [Info] PBX_Manager:: handle_input with fd = 4 05/17/10 9:00:47.79 [Info] PBX_Client_Proxy::parse_line, line = ack=1 05/17/10 9:00:47.79 [Info] PBX_Client_Proxy::parse_line, line = extension=EMM 05/17/10 9:00:47.80 [Info] hand_off looking for proxy for = EMM 05/17/10 9:00:47.80 [Error] No proxy found. 05/17/10 9:00:47.80 [Info] PBX_Client_Proxy::handle_close
To determine if the PBX daemon or service is available
- Start the needed service. In this example, the missing NetBackup service is EMM. To start this service, do the following:
(UNIX/Linux) Enter the nbemm command.
(Windows) Start the NetBackup Enterprise Media Manager service (Start > Run, then enter services.msc).
If necessary, stop and restart all NetBackup services.
On Windows:
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup
On UNIX:
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all