Just stumpled upon something that trew me off today. We a have a series of Veeam backups of VMs running on Nutanix.
The jobs are all based on Categories from Nutanix. This works pretty well (have the API rate issue, but that's a different story).
One job contains a number af SQL servers and we have setup application aware processing and configured the proper permissions on the SQL instances. So far it looks to working perfectly.
Today I was asked to setup periodic SQL backups on this job. Ususally that's just a matter of changing the application proccessing for SQL instances, but in this case it doesn't work.
From the log files on the Veeam server it looks like it's not processing the category expansion?
is this a limitation of the Nutanix integration using categories?
Code: Select all
[14.11.2025 15:12:33.641] <17> Info (3) Building VMs for logs processing
[14.11.2025 15:12:33.689] <17> Info (3) New JWT token for platform [xxxxxxxx-ae1e-4eaf-86eb-8a9acc2670e2] has been issued [1769701778]
[14.11.2025 15:12:33.843] <17> Info (3) Platform service JWT created. Public JWT part: xxx
[14.11.2025 15:12:33.843] <17> Info (3) External platform client created. PlatformId: [xxxxxxxx-ae1e-4eaf-86eb-8a9acc2670e2].
[14.11.2025 15:12:33.904] <17> Info (3) External infrastructure api [post] request #1 https://xxsrv01:8543/api/v2/policies/e5498d0e-8d63-46fa-b85b-12555006e5bb/guestProcessing/resolveVms {"sourceObjects":[{"objectId":"Veeam Backup:SQL Services","objectTag":"d06f611d-b47a-428b-a008-ac6bf3717c80Veeam Backup:SQL Services","objectName":"","infrastructureId":"","objectType":2}]}
[14.11.2025 15:12:33.942] <17> Info (3) External infrastructure api [post] response #1 {"type":"https://tools.ietf.org/html/rfc9110#section-15.6.1","title":"An unexpected error occurred","status":500,"detail":"One or more errors occurred","instance":"/v2/policies/e5498d0e-8d63-46fa-b85b-12555006e5bb/guestProcessing/resolveVms","traceId":"3ec72dbe-7542-41da-b5b2-0a2451ec89be"}
[14.11.2025 15:12:33.953] <17> Error (3) Failed to resolve VMs for guest processing. URI: https://xxxxsrv01:8543/api/v2/policies/e5498d0e-8d63-46fa-b85b-12555006e5bb/guestProcessing/resolveVms. Body:{"type":"https://tools.ietf.org/html/rfc9110#section-15.6.1","title":"An unexpected error occurred","status":500,"detail":"One or more errors occurred","instance":"/v2/policies/e5498d0e-8d63-46fa-b85b-12555006e5bb/guestProcessing/resolveVms","traceId":"3ec72dbe-7542-41da-b5b2-0a2451ec89be"}
[14.11.2025 15:12:33.953] <17> Error (3) An unexpected error occurred
[14.11.2025 15:12:33.953] <17> Error (3) One or more errors occurred
[14.11.2025 15:12:33.953] <17> Error (3) (Veeam.Backup.Interaction.PlatformService.CInvalidCodeFromPlatformServiceException)
[14.11.2025 15:12:33.953] <17> Error (3) at Veeam.Backup.Interaction.PlatformService.CExternalApiHttpClient.EnsureSuccessStatusCode(HttpResponseMessage response)
[14.11.2025 15:12:33.953] <17> Error (3) at Veeam.Backup.Interaction.PlatformService.CExternalApiHttpClient.Post[T](Uri requestUri, T resource, TimeSpan timeout, Boolean reloginOnUnauthorized, String& responseBody)
[14.11.2025 15:12:33.953] <17> Error (3) at Veeam.Backup.Interaction.PlatformService.CExternalApiHttpClient.Post
[14.11.2025 15:12:33.961] <17> Error (3) Failed to resolve VMs for guest processing. An unexpected error occurred
[14.11.2025 15:12:33.961] <17> Error (3) One or more errors occurred
/mikkel