Troubleshooting SaaS workload issues
Check the following locations for logs of the SaaS workload:
PiSaaS
Windows: install_path\NetBackup\logs\ncfnbcs
UNIX: /usr/openv/netbackup/logs/ncfnbcs
bpVMUtil
Windows: install_path\NetBackup\logs\bpVMutil
UNIX: /usr/openv/netbackup/logs/bpVMutil
APIs/nbWebServices
Windows: install_path\NetBackup\logs\nbwebservice
UNIX: /usr/openv/logs/nbwebservice
Use the following information to troubleshoot issues.
Table: Troubleshooting issues in SaaS Workload
Problems | Recommended actions |
|---|---|
Failed to add a Hub due to incorrect Hub name or invalid user credentials. | Enter appropriate Hub name and valid credentials. |
Failed to add a Hub due to issue in credential validation. | Check if the credentials are not expired. Also check if the credentials are valid. |
Failed to add a Hub due to limited permissions. | Assign appropriate permissions to the user on the SaaS workload. See Role permissions. |
Failed to delete a Hub due to limited permissions. | Assign appropriate permissions to the user on the SaaS workload. See Role permissions. |
Failed to perform discovery on the Hub due to limited permissions. | Assign appropriate permissions to the user on the SaaS workload. See Role permissions. |
The services are not deleted from NetBackup after deleted the associated Connector from NetBackup SaaS Protection. | The services get removed from NetBackup after 30 days from Connector deletion. |
Failed to launch the NetBackup SaaS Protection web UI using the Launch NSP option. Credentials are required while launching the NetBackup SaaS Protection web UI. | Check if SSO is configured correctly. If SSO is configured correctly, check if the user has appropriate permissions to access the NetBackup SaaS Protection web UI. |
Connecting to the proxy host X.X.X.X on port 3128 with type SOCKS5 | Configure proxy settings on the primary server using the bpsetconfig utility. |