Important Update: Cohesity Products Knowledge Base Articles
All Cohesity Knowledge Base Articles are now managed via the Cohesity Support Portal: https://support.cohesity.com/. The Knowledge Base articles available here will not reflect the latest information or may no longer be accessible.
Problem
The NetBackup security certificate could not be deployed on the master server during installation.Cause
This issue is caused by one of the following:- The Security web application has not started or it took a long time to start that caused the NetBackup installer to time out while deploying certificates.
- Some of the NetBackup core services have not started.
- The web service certificate that is used for communication with Certificate Authority (CA) is not deployed.
- Certificate Authority (CA) was unable to sign the NetBackup security certificate.
Solution
To resolve the issue, review the following, possible, causes:Cause 1 – The Security web application has not started or it took a long time to start, causing the NetBackup installer to time-out while deploying certificates.
Complete the following procedure to manually deploy the certificate on the master server:
- Check whether the security web service in the NetBackup Web Management Console (nbwmc) is up and running using the following command:
<Install_Path>/bptestnetconn -wnbwmc/security -T 5 -e 2 -H <master_server_name>
On Windows: VERITAS\NetBackup\bin
On Unix: /usr/openv/netbackup/bin
For example:
- If the security web app status is SUCCESS, proceed to Step 2.
- If the status is FAIL, restart the NetBackup Web Management Console service (nbwmc).
On Windows:
C:\Program Files\Veritas\NetBackup\bin\bpup -e "NetBackup Web Management Console" -f -v
On UNIX:
<Install_Path>/netbackup/bin/nbwmc -terminate
<Install_Path>/netbackup/bin/nbwmc
For example:
/usr/openv/netbackup/bin/nbwmc -terminate
/usr/openv/netbackup/bin/nbwmc
- Run the following commands to deploy the CA certificate and the host certificate:
- nbcertcmd -getCACertificate
- nbcertcmd -getCertificate
Note: For more details on security certificates in NetBackup, refer to the following :
NetBackup Security and Encryption Guide.
If the problem persists, contact the Veritas Technical Support team.
Cause 2 – Some of the NetBackup core services have not started.
Carry out the following procedure to resolve the issue:
- Check the status of the following services by running the bpps command from the NetBackup/bin directory:
- nbsl
- nbatd
- NB_dbsrv (on UNIX) or the dbsrv16 (on Windows)
Note: For more details on NetBackup commands, refer to the NetBackup Commands Reference Guide
- Start the nbsl and nbatd services, if they are not running.
- Start the NB_dbsrv (on Unix) service or the dbsrv16 (on Windows) service, if it is not running.
On Windows:
<Install_Path>\bin\bpdown -e "NetBackup Service Layer" -f -v
<Install_Path>\bin\bpup -e "NetBackup Service Layer" -f -v
<Install_Path>\bin\bpdown -e "NetBackup Authentication" -f -v
<Install_Path>\bin\bpup -e "NetBackup Authentication" -f -v
<Install_Path>\bin\bpdown -e "SQLANYs_VERITAS_NB" -f -v
<Install_Path>\bin\bpup -e "SQLANYs_VERITAS_NB" -f -v
Alternatively, you may use the Service Control Manager to restart the NetBackup Service Layer (NBSL), NetBackup Authentication (AT) services, and and SQLANYs_VERITAS_NB services .
For example:
C:\Program Files\Veritas\NetBackup\bin\bpdown -e "NetBackup Service Layer" -f -v
C:\Program Files\Veritas\NetBackup\bin\bpup -e "NetBackup Service Layer" -f -v
C:\Program Files\Veritas\NetBackup\bin\bpdown -e "NetBackup Authentication" -f -v
C:\Program Files\Veritas\NetBackup\bin\bpup -e "NetBackup Authentication" -f -v
C:\Program Files\Veritas\NetBackup\bin\bpdown -e "SQLANYs_VERITAS_NB" -f -v
C:\Program Files\Veritas\NetBackup\bin\bpup -e "SQLANYs_VERITAS_NB" -f -v
On Unix:
<Install_Path>/netbackup/bin/nbsl -terminate
<Install_Path>/netbackup/bin/nbsl
To stop nbatd and NB_dbsrv, use the term signal as shown in the example:
To start nbatd and NB_dbsrv, run the following commands:
<install_path>/netbackup/bin/nbatd
<install_path>/db/bin/NB_dbsrv
For example:
/usr/openv/netbackup/bin/nbsl -terminate
/usr/openv/netbackup/bin/nbsl
# ps -fed |grep nbatd
root 16018 1 4 08:47:35 ? 0:01 ./nbatd
root 16019 16011 0 08:47:39 pts/2 0:00 grep nbatd
# kill 16018
# ps -fed |grep NB_dbsrv
root 11959 1 4 08:47:35 ? 0:01 ./NB_dbsrv
root 16174 16011 0 08:47:39 pts/2 0:00 grep ./NB_dbsrv
# kill 11959
/usr/openv/netbackup/bin/nbatd
/usr/openv/db/bin/NB_dbsrv
- Run the following commands to get the CA certificate and the host certificate:
Note: For more details on security certificates in NetBackup, refer to the NetBackup Security and Encryption Guide.
- nbcertcmd -getCACertificate
- nbcertcmd -getCertificate
Cause 3 – The web service certificate that is used for communication with Certificate Authority (CA) is not deployed.
Carry out the following procedure to resolve the issue:- Check the web service user certificate at the following location:
On UNIX: /usr/openv/var/global/vxss/nbcertservice
If the default web service user ‘nbwebsvc’ is used, the directory structure is as follows:
nbwebsvc/certstore
- If the path is not available, run the nbcertconfig command to generate the certificate:
<Install_Path>/admincmd/nbcertconfig -u
On Windows - VERITAS\NetBackup\bin\admincmd\nbcertconfig -u
On UNIX - /usr/openv/netbackup/bin/admincmd/nbcertconfig -u
- Restart the NetBackup services.
- Run the following commands to get the CA certificate and the host certificate:
- nbcertcmd -getCACertificate
- nbcertcmd -getCertificate
If the problem persists, contact the Veritas Technical Support team.
Cause 4 – Certificate Authority (CA) was unable to sign the NetBackup security certificate.
You can confirm the error details as follows:- Run the following command:
The following error occurs on the command-line interface:
EXIT STATUS 5904: Internal error
- Go to the following log file location:
- Check for the following error message:
Once the NetBackup installation is complete, carry out the following procedure to resolve the issue:
- Run the following command:
- Check the security certificate deployment level using following command:
- If the security certificate deployment level is Very High, run the following command to logon:
- Create a token using the following command:
<token_name> must start with alphanumeric and can include the following characters: spaces, - (hyphen), _ (underscore).
- Create a file and add the token in that file.
- Deploy the host ID-based certificate by running the following command:
<Install_path>/netbackup/bin/nbcertcmd -getCertificate -file <token_file_path>
The ‘-file’ parameter should be used only when the security certificate deployment level is Very High. Provide the exact path of the file here.
Example:
- <Install_Path>/netbackup/bin/admincmd/nbcertconfig -u
- <Install_Path>/netbackup/bin/nbcertcmd -getSecConfig -CertDeployLevel
- <Install_Path>/netbackup/bin/bpnbat -login -loginType WEB
- Run the following command to create a token:
- Run the following command:
- <Install_Path>/netbackup/bin/nbcertcmd -getCertificate -file tokenFile.txt
Note: For more details on security certificates in NetBackup, refer to the NetBackup Security and Encryption Guide
If the problem persists, contact the Veritas Technical Support team.