NetBackup™ Troubleshooting Guide
- 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
- 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
- About the NetBackup Smart Diagnosis (nbsmartdiag) utility
- 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
- Options to recover the NetBackup catalog
- Prerequisites for recovering the NetBackup catalog or NetBackup catalog image files
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup databases
Troubleshoot adding or updating the trust
This topic describes how to troubleshoot the issue when an operation fails to add or update the trust between the source and the target primary server.
Adding or updating the trust between the source and target primary server has failed.
The issue can occur because of the following reasons:
Cause 1 - Enrollment of source primary server to target primary server failed.
Cause 2 - Failed to add the target primary server in the trusted primary server database and in the configuration file as TRUSTED_MASTER.
See Troubleshooting Windows certificate store issues.
To troubleshooting adding or updating the trust
- Review the error message:
EXIT STATUS 5630: Failed to get version of remote primary server.
If the vnetd proxy service is down or the connection to the vnetd proxy has failed on the source primary server, review the logs in the following order:
Review the connection to the vnetd proxy of the remote primary server.
To review the connection to the remote primary server's vnetd proxy, run the bptestbpcd -host remote_primary_server_name command.
Review the proxy logs:
Windows: C:\Program Files\Veritas\NetBackup\logs\nbpxyhelper\log_file
Linux: /usr/openv/logs/nbpxyhelper/log_file
- Review the error message:
EXIT STATUS 5616: The local primary server is not reachable. The trust is unidirectional right now, the remote primary server trusts the local primary server, but the local primary server doesn't trust the remote master. Please remove the trust
If the bprd service is down on the source primary server, review the logs in the following order:
Review the bprd logs.
Windows: C:\Program Files\Veritas\NetBackup\logs\bprd\log_file
UNIX: /usr/openv/netbackup/logs/bprd/log_file
Review the proxy logs.
Windows: C:\Program Files\Veritas\NetBackup\logs\nbpxyhelper\log_file
Linux: /usr/openv/logs/nbpxyhelper/log_file
Review the EMM database logs.
Windows: C:\Program Files\Veritas\NetBackup\logs\nbemm\log_file
Linux: /usr/openv/logs/nbemm/log_file