Error during the RHV virtual machines discovery phase
The following table describes the problem that might occur when you try to discover RHV virtual machines.
Table: Error run into during the RHV virtual machines discovery phase
Error message or cause | Explanation and recommended action |
|---|---|
The RHV assets are not discovered after the correct RHV manager credentials are added. The VM discovery operation fails. | The maximum allowed length of the RHV manager name is 255 characters, however, if the characters exceed 95, the asset discovery fails. Workaround:
|
The discovery job fails with error 200. (Scheduler found no backups or clients to deploy NetBackup) | Ensure that the query specified in the policy or intelligent VM group is correct. The VMs that need protection are added recently to RHV manager or the VM configuration has changed and the autodiscovery or discover now was not triggered.
|
The GET asset API does not work when you use the tolower and toupper functions. | NetBackup Web UI: For the filter in the intelligent Groups, NetBackup WebUI might not display accurate list of the RHV VMs that match the filter if the VM or the RHV server has non-English characters. However, during the backup, correct VMs are selected even though its attributes are non-English. This behavior is only in viewing the VMs in NetBackup Web UI. GET assets API of asset service: The GET Assets API does not give the desired result if the tolower or toupper functions are used together for the assets that have non-English characters. |
There is a delay in the API response. | For a large number if RHV assets, if you add large and random offsets to an API request, there is an increase in the processing time that leads to a delay in the API response. |