Troubleshooting for CDP
This error occurs when the IOFilter encounters a problem and enters into NOOP (Non-Operational) mode.
Possible reasons:
IOfilter encountered a problem with the datastore.
IOfilter encountered a problem while reading from vmdk on the ESXi server.
Workaround:
Remove the VTSTAP policy from all the disks of protected VMs and reattach.
This error occurs when the storage policy is not detached from all the virtual disks of the VM. The next backups fail with error code 156.
Workaround:
Remove the Veritas I/O filter-based storage (vtstap) policy from all the disks of the VM that CDP protected previously. You can do this operation on the vCenter.
You may get this error when trying to subscribe one or more VMs to the CDP protection plan. Occurs when the CIM server service on the ESXi server is non-responsive.
Workaround:
Restart the CIM server service on the ESXi server and retry the VM subscription to the CDP protection plan. You can find the CIM server service of the ESXi server, under Configure > Services section of the ESXi.
Possible reasons:
When you mount a read-only file system and provide its path in the CDP gateway configuration, the service is configured, but the gateway fails to start.
When you try to configure the gateway again, by giving a read/write path, the service still fails to start.
Workaround: Retry the operation after you remove the nbcct directory from:
<staginglocation>/nbcct
Possible reasons:
Currently, NetBackup supports only the vtstap policy as a storage policy for CDP. If you try to subscribe a VM using a hybrid storage policy (encryption + replication) it shows the error.
Workaround: Avoid using a hybrid storage policy (encryption + replication) for CDP-protected VMs.
Possible reasons:
The configured staging area is unmounted post reboot or has an unsupported file system. For example, if you configure the CDP gateway using a supported mount like /mnt/stage_area and do not configure auto-mount. After a system restart, this path points to root file system, which CDP does not support, hence the CDP service (nbcctd) cannot start.
Workaround: Ensure that the staging area or the relevant disk mounts are remounted properly, whenever there are changes in the system that is related to the unmount or the system reboot.
Possible reasons:
While removing CDP protection, if the protected VM is powered off the CDP gateway cannot get the required information of storage policies from VAIO. The CDP protection is removed from the VM. However, the I/O tapping policies are still attached to the vmdk of that VM and it continues to tap the I/O and affect performance.
Workaround: Always detach the storage policy of the VMs before you unsubscribe the VMs, irrespective of their powered on or off state.
Explanation
Occurs when you protect a NetBackup primary server, using the same primary server's protection plan.
Workaround: We do not recommend protecting a NetBackup primary server using a protection plan that was made using the same primary server. If this error occurs, detach the storage policy from the NetBackup primary server VM, and unsubscribe the VM from the protection plan.
Explanation:
CDP policy is not deleted after removing the entries in case of an unreachable host.
Workaround: The CDP protection plan subscription does not get removed, as NetBackup does not delete the CDP policy before it cleans up the CDP host. To delete the entries of the unreachable gateway, you must call the Delete policy API manually after calling the Delete CDP gateway API.
You can clean up an unreachable CDP gateway using the following API:
To DELETE CDP Gateway
URL : https://netbackup/config/cdp-gateway/force
HTTP Method : DELETE
Headers:
Authorisation: Bearer <Token>
Content-Type: application/vnd.netbackup+json;version=9.0;charset=UTF-8
To Delete Policy
URL : https://netbackup/config/policies/policy_name
HTTP Method : DELETE
Headers:
Authorisation: Bearer <Token>After you successfully run the APIs, the mapping for the policy and the VM is still visible in the web UI. If you try to remove the protection of that VM through web UI, you can see an error message saying: Subscription ID not found. This behavior is expected.
: The CDP gateway update operation tries to restart the service. If stopping the service takes longer time than usual, then the update operation shows an error, indicating that the CDP service (nbcctd) failed to restart.
: In this case, check if the nbcctd service is running on the gateway. If the service is running, wait for it to shut down. To manually stop the service, use the command: /usr/openv/netbackup/bin/nbcctd -terminate. When the service has stopped, start it using the command /usr/openv/netbackup/bin/nbcctd -X.
: While creating a CDP protection plan to use universal share, if you select a storage device that does not have universal share capability, you get this error.
: You must select a storage device that has universal share capability.
: While creating a CDP protection plan to use universal share, if you select a CDP gateway server earlier than NetBackup version 10.2, you get this error.
: To use a universal share, the CDP gateway version must be at NetBackup version 10.2 or higher.