Troubleshooting CloudPoint and NetBackup integration issues
For troubleshooting also consider the limitations. See About NetBackup and CloudPoint integration for snapshot management.
Policy validation fails with error 130, due to one of following reasons:
Certificate mismatch on client.
Workaround
Remove the CloudPoint CA certificate from the following location and validate the policy again.
install_location/var/global/cloudpointCloud point server is not accessible.
This error is encountered if the following options are not configured:
In the Snapshot Client and Replication Director dialog box, select the option.
In the Schedules tab, select Snapshots only option.
Policy validation fails with error 4201, due to one of following reasons:
The source disk is not associated with configured CloudPoint server.
Workaround
Check if you have configured the CloudPoint plug-in associated with a particular disk asset.
CloudPoint server takes additional time to discover.
Workaround
Wait for sometime so that all the devices from array are discovered.
CloudPoint server is not accessible from Master or Client.
Or
Certificate mismatch on client.
Or
CloudPoint certificate has been expired.
Workaround
Refresh the CloudPoint certificates on client.
Certificate location:
/usr/openv/var/global/cloudpoint/<CloudPoint server name>.pemHP3 par is loaded and there are multiple WS API operations are running.
Workaround
Try snapshot creation after sometime.
VSO policy validation fails with the following error:
CVSOPlugin::selectSnapshots : getAssetDetails failed with status: [error], Error:[Asset no_vso_device not found]
Workaround
When you encounter this error, run the lsscsi command to verify if the device selected in the backup selection is available on the client.
If the device is not listed, verify the connectivity issue between the array and host or get in touch with your system administrator.
Backup fails with the following error:
PFI rotation error: 13
The errors occurs because the operation takes longer to complete due to network connectivity, causing jobs to time out and fail.
Workaround
Increase the REQUEST_DELIVERY_TIMEOUT configuration option from the default of 300 (5 minutes) to more than 3600 seconds (more than 60 minutes).
This option does not appear in the NetBackup Administration Console host properties. See the NetBackup Commands Reference Guide for information about using the bpgetconfig and the bpsetconfig commands to change the configuration option in the bp.conf file (UNIX) or the registry (Windows).
If there is any clone snapshot or physical copy associated with source device, snapshot restore fails.
Workaround
Break the clone relationship or delete the clone snapshot.