Forum Discussion
- skillmaster44Level 3
Hello, If you haven't tried them already, here are a few troubleshooting ideas that may work.
Verify Cloud Storage Configuration - Ensure that your customized Amazon cloud provider is correctly configured under Cloud Storage Servers in NetBackup and double-check that the endpoint URL, access key, and secret key are correctly set.
Check Network Connectivity - The error "cannot connect to socket" suggests a network issue. Verify that the NetBackup media server can reach the custom endpoint (e.g., try telnet <endpoint> 443 or use curl/wget). Ensure that necessary firewall rules and security groups allow traffic to the endpoint.
Validate Cloud Credentials - Ensure that the credentials used for the custom Amazon provider have the necessary permissions to list and create buckets.
Review NetBackup Logs - Check bpdm, nblog, or cloudprovider logs for more specific errors. Logs are usually found under /usr/openv/logs (Linux) or C:\Program Files\Veritas\NetBackup\logs (Windows).
Try Manually Creating a Bucket - If the NetBackup wizard is failing, try creating a bucket using AWS CLI or another method to see if the issue is specific to NetBackup.
Restart NetBackup Services - Restart all NetBackup services to ensure there are no stuck processes. Command: Linux: bp.kill_all && bp.start_all Windows: Restart the NetBackup Device Manager and related services.
Check License & Feature Support - Ensure that the license supports third-party cloud storage if using a custom provider.
Related Content
- 10 years ago
- 7 years ago
- 5 years ago
- 11 years ago