Veritas NetBackup™ Troubleshooting Guide
- 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
- 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
About SERVER entries in the bp.conf file
On UNIX and Linux computers, every SERVER entry in a client bp.conf file must be a NetBackup master or media server. That is, each computer that is listed as a SERVER must have either NetBackup master or media server software installed. The client service on some clients cannot be started if the client name is incorrectly listed as a server.
bp.conf SERVER entry specifies a NetBackup client-only computer, SAN client backups or restores over Fibre Channel may fail to start. In this case, determine if the nbftclnt process is running on the client. If it is not running, check the nbftclnt unified logging file (OID 200) for errors. You may see the following in the nbftclnt log:
The license is expired or this is not a NBU server. Please check your configuration. Note: unless NBU server, the host name can't be listed as server in NBU configuration.
Remove or correct the SERVER entry in the
bp.conf file, restart nbftclnt on the client, and retry the operation.
The nbftclnt process on the client must be running before you start a SAN client backup or restore over Fibre Channel.