Unsere Copy Jobs (neues V12 Format) werden in PRTG alle mit "Never started" angezeigt. Der Job wird zwar gefunden, aber im Log steht dann folgendes:
2023-06-12 14:30:21.060446 DEBG TId 7296 Result of Sensor 6720> Get Job Sessions for Immediate Backup Copy with filter 'JobUid=="3ee889fe-a7a3-4326-aaef-d750963b7a71"' 2023-06-12 14:30:21.076066 DEBG TId 7296 Result of Sensor 6720> Retrieved /api/query?type=BackupJobSession&format=Entities&pageSize=1&page=1&sortDesc=CreationTime&filter=JobUid%3D%3D%223ee889fe-a7a3-4326-aaef-d750963b7a71%22: 200 OK body: {"Refs":null,"Entities":{"Jobs":null,"FailoverPlans":null,"Backups":null,"Replicas":null,"Repositories":null,"RestorePoints":null,"VmRestorePoints":null,"VAppRestorePoints":null,"VmReplicaPoints":null,"BackupJobSessions":{"BackupJobSessions":[]},"ReplicaJobSessions":null,"ReplicaTaskSessions":null,"RestoreSessions":null,"HierarchyRoots":null,"BackupTaskSessions":null,"BackupServers":null,"ManagedServers":null,"EnterpiseRoles":null,"EnterpiseAccounts":null,"WanAccelerators":null,"CloudGateways":null,"CloudTenants":null,"CloudReplicas":null,"VCloudOrganizationConfigs":null,"BackupFiles":null,"VSphereSelfServiceConfigs":null,"CloudPublicIps":null,"CloudHardwarePlans":null,"CloudVmReplicaPoints":null,"AgentRestorePoints":null,"AgentBackupJob":null,"CloudGatewayPools":null,"CloudFailoverPlans":null,"ExternalRepositories":null,"VlanConfigurations":null,"CloudFailoverSessions":null,"AgentProtectionGroups":null,"DiscoveredComputers":null,"FileServers":null,"NASJobs":null,"CdpReplicas":null,"CdpReplicaVms":null,"CdpPolicies":null,"CdpReplicaSessions":null,"CdpReplicaTaskSessions":null,"VAppReplicaPoints":null,"VmCdpReplicas":null,"VAppCdpReplicas":null,"VAppCdpReplicaVms":null,"SystemSessions":null},"Resources":null,"Links":null,"PagingInfo":null} 2023-06-12 14:30:21.076066 DEBG TId 7296 Result of Sensor 6720> Job session array is empty. Job has not been run yet. 2023-06-12 14:30:21.076066 DEBG TId 7296 Result of Sensor 6720> Response Message is: #:error.no_sessions[]
Der Backup Job hat aber ausführungen in den letzten 2 Stunden. Es scheint als ob die JobSessions der neuen V12 Backup Copy Jobs nicht mehr in /api/query?type=BackupJobSession aufgelistet wird. Finde dazu aber nichts in der API Dokumentation.
Oder gibt es vielleicht einen Fehler im Sensor?
Danke
Add comment