Please enter search query.
Search <book_title>...
Veritas NetBackup™ Troubleshooting Guide
Last Published:
2019-07-01
Product(s):
NetBackup (8.2)
- Introduction
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- About troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Resolving PBX problems
The Enterprise Media Manager (EMM) services and other services of NetBackup require a common services framework that is called Private Branch Exchange (PBX). Like vnetd, PBX helps limit the number of TCP/IP ports that the CORBA services of NetBackup use.
To resolve PBX problems
- Check that the PBX is properly installed. If PBX is not installed, NetBackup is unresponsive. Refer to the following procedure:
- Check that PBX is running, and initiate PBX if necessary by using the following procedure:
- Check that PBX is correctly configured. If PBX is incorrectly configured, NetBackup is unresponsive. Refer to the following procedure:
- Access and check the PBX logs by using the following procedure:
- Check the PBX security and correct any problem by using the following procedure:
- Check that the required NetBackup daemon or service is running. If necessary, start the needed daemon or service by using the following procedure: