Tips for accessing the NetBackup web UI
When NetBackup is properly configured, you can access the master server at the following URL:
https://masterserver/webui/login
If the web UI on a master server does not display, follow these steps to troubleshoot the issue.
Table: Solutions when the web user interface does not display
Step | Action | Description |
|---|---|---|
Step 1 | Check your network connection. | |
Step 2 | Verify that the firewall is open for port 443. | Refer to the following article: |
Step 3 | If port 443 is in use, configure another port for the web UI. | Refer to the following article: |
Step 4 | Verify that the nbwebservice is up. | Check the nbwebservice logs for more details. |
Step 5 | Verify that the vnetd -http_api_tunnel is running. | Verify that the vnetd -http_api_tunnel service is running. For more details, check the vnetd -http_api_tunnel logs with OID 491. |
Step 6 | Ensure that the third-party certificate is accessible and has not expired. | Use the java keytools command to validate the Check whether the nbwebgroup has a permission to access the Contact Veritas Technical Support. |
Restart the vnetd service.
Try carrying out all steps from Table: Solutions when the web user interface does not display.
The certificate warning is displayed if the NetBackup web server is using a certificate issued by a CA that is not trusted by the web browser. The default NetBackup web server certificate is issued by the NetBackup CA that is not trusted by web browsers.
To resolve a certificate warning from the browser when you access the web UI
- Configure the third-party certificate on the NetBackup web server.
For more details, refer to the NetBackup Security and Encryption Guide.
- If the problem persists, contact Veritas Technical Support.
To resolve a certificate warning from the browser when you access the web UI
- Run the configureTPCerts command on all cluster nodes.
For more details, refer to the NetBackup Security and Encryption Guide.
- After you run the configureTPCerts command, be sure to restart the nbwmc and vnetd services.