Add or update trust
Adding or updating the trust between the source and target primary server is 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.
- Review the error message: (EXIT STATUS 5630: Failed to get version of remote master server.)
If the vnetd proxy service is down or connection to vnetd proxy failed on the source primary server, check the logs in the following order:
Check the connection to the vnetd proxy of the remote primary server.
To check the connection to the remote primary server's vnetd proxy, run the bptestbpcd -host remote_primary_server_name command.
Check the proxy logs:
Windows: C:\Program Files\Veritas\NetBackup\logs\nbpxyhelper\log_file
Unix: /usr/openv/logs/nbpxyhelper/log_file
- Review the error message: (EXIT STATUS 5616: The local master server is not reachable. The trust is unidirectional right now, the remote master server trusts the local master server, but the local master server doesn't trust the remote master. Please remove the trust)
If the bprd service is down on the source primary server, check the logs in the following order:
Check the bprd logs.
Windows: C:\Program Files\Veritas\NetBackup\logs\bprd\log_file
UNIX: /usr/openv/netbackup/logs/bprd/log_file
Check the proxy logs.
Windows: C:\Program Files\Veritas\NetBackup\logs\nbpxyhelper\log_file
UNIX: /usr/openv/logs/nbpxyhelper/log_file
Check the EMM database logs.
Windows: C:\Program Files\Veritas\NetBackup\logs\nbemm\log_file
UNIX: /usr/openv/logs/nbemm/log_file