Cant backup hyper-v 2016 host

[witwicki]

Hi, I am having an issue where I can not back up any guest on a hyper-v cluster 2016

Is any one able to help?

Thanks

Code: Select all

[11.07.2017 09:48:49] <01> Info     Waiting for backup infrastructure resources availability
[11.07.2017 09:48:54] <01> Error    Failed to dispatch pending task. SessId: [9c6de295-9d8f-4711-a560-d156f056e361], Task: [xxx-MH-MGMT7 from job "xxx-MH-MGMT7_2017-07-11T094832 (Active Full)" (task id:2d0622b9-21ed-459c-a174-7f37e9408f6b, task sess id:1d9063db-7aa2-4379-9041-b0185ca3af8a, job sess id:9c6de295-9d8f-4711-a560-d156f056e361)] (System.Exception)
[11.07.2017 09:48:54] <01> Error    Failed to analyze snapshot availability for task '2d0622b9-21ed-459c-a174-7f37e9408f6b' (System.Exception)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CHvSnapResDispatcher.CanAcquireResource(CResDispatchIterationContext dispatchContext, CResourceTask task, IResourceRequest resourceRequest, Boolean sessionLogEnabled, IResourceResponse[] acquiredResources)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CResourceTaskScheduler.IsAllResourcesAvaliable(CResDispatchIterationContext dispatchContext, CResourceTask task)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CResourceTaskScheduler.DispatchPendingTask(CResDispatchIterationContext dispContext, CResourceTask task)
[11.07.2017 09:48:54] <01> Error    Failed to fetch vm info. VM name: 'xxx-MH-MGMT7'. VmRef: '393c8c22-1cfa-4971-b84d-048674b4ccfa' (System.Exception)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.LoadDelayedData(IHvVmCache vmCache, CHvClusterNodesCache clusterNodesCache)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CHvSnapResDispatcher.CanAcquireResource(CResDispatchIterationContext dispatchContext, CResourceTask task, IResourceRequest resourceRequest, Boolean sessionLogEnabled, IResourceResponse[] acquiredResources)
[11.07.2017 09:48:54] <01> Error    Unable to find Hyper-V hosts where VM '393c8c22-1cfa-4971-b84d-048674b4ccfa' is registered (Veeam.Backup.Common.CAppException)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvResourceDispatcherCache.GetVm(Guid vmId, IHvHost hostOrCluster, CHvDbHost& ownerHost)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.IsNeedReloadDelayedData(IHvVmCache cache, CHvDbHost& currVmHost)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.LoadDelayedData(IHvVmCache vmCache, CHvClusterNodesCache clusterNodesCache)
[11.07.2017 09:48:54] <01> Info     [CHvSnapshotHolder] Task failed in resource scheduler. Closing shared snapshot for task '2d0622b9-21ed-459c-a174-7f37e9408f6b'
[11.07.2017 09:48:54] <01> Info     [CHvSnapshotHolder] Task completed. Closing shared snapshot for task '2d0622b9-21ed-459c-a174-7f37e9408f6b'
[11.07.2017 09:48:54] <01> Error    Unable to allocate processing resources.
[11.07.2017 09:48:54] <01> Error    Failed to dispatch pending task. SessId: [9c6de295-9d8f-4711-a560-d156f056e361], Task: [xxx-MH-MGMT7 from job "xxx-MH-MGMT7_2017-07-11T094832 (Active Full)" (task id:2d0622b9-21ed-459c-a174-7f37e9408f6b, task sess id:1d9063db-7aa2-4379-9041-b0185ca3af8a, job sess id:9c6de295-9d8f-4711-a560-d156f056e361)] (System.Exception)
[11.07.2017 09:48:54] <01> Error    Failed to analyze snapshot availability for task '2d0622b9-21ed-459c-a174-7f37e9408f6b' (System.Exception)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CHvSnapResDispatcher.CanAcquireResource(CResDispatchIterationContext dispatchContext, CResourceTask task, IResourceRequest resourceRequest, Boolean sessionLogEnabled, IResourceResponse[] acquiredResources)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CResourceTaskScheduler.IsAllResourcesAvaliable(CResDispatchIterationContext dispatchContext, CResourceTask task)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CResourceTaskScheduler.DispatchPendingTask(CResDispatchIterationContext dispContext, CResourceTask task)
[11.07.2017 09:48:54] <01> Error    Failed to fetch vm info. VM name: 'xxx-MH-MGMT7'. VmRef: '393c8c22-1cfa-4971-b84d-048674b4ccfa' (System.Exception)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.LoadDelayedData(IHvVmCache vmCache, CHvClusterNodesCache clusterNodesCache)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CHvSnapResDispatcher.CanAcquireResource(CResDispatchIterationContext dispatchContext, CResourceTask task, IResourceRequest resourceRequest, Boolean sessionLogEnabled, IResourceResponse[] acquiredResources)
[11.07.2017 09:48:54] <01> Error    Unable to find Hyper-V hosts where VM '393c8c22-1cfa-4971-b84d-048674b4ccfa' is registered (Veeam.Backup.Common.CAppException)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvResourceDispatcherCache.GetVm(Guid vmId, IHvHost hostOrCluster, CHvDbHost& ownerHost)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.IsNeedReloadDelayedData(IHvVmCache cache, CHvDbHost& currVmHost)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.LoadDelayedData(IHvVmCache vmCache, CHvClusterNodesCache clusterNodesCache)
[11.07.2017 09:48:54] <01> Error    Failed to dispatch pending task. SessId: [9c6de295-9d8f-4711-a560-d156f056e361], Task: [xxx-MH-MGMT7 from job "xxx-MH-MGMT7_2017-07-11T094832 (Active Full)" (task id:2d0622b9-21ed-459c-a174-7f37e9408f6b, task sess id:1d9063db-7aa2-4379-9041-b0185ca3af8a, job sess id:9c6de295-9d8f-4711-a560-d156f056e361)] (System.Exception)
[11.07.2017 09:48:54] <01> Error    Failed to analyze snapshot availability for task '2d0622b9-21ed-459c-a174-7f37e9408f6b' (System.Exception)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CHvSnapResDispatcher.CanAcquireResource(CResDispatchIterationContext dispatchContext, CResourceTask task, IResourceRequest resourceRequest, Boolean sessionLogEnabled, IResourceResponse[] acquiredResources)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CResourceTaskScheduler.IsAllResourcesAvaliable(CResDispatchIterationContext dispatchContext, CResourceTask task)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CResourceTaskScheduler.DispatchPendingTask(CResDispatchIterationContext dispContext, CResourceTask task)
[11.07.2017 09:48:54] <01> Error    Failed to fetch vm info. VM name: 'xxx-MH-MGMT7'. VmRef: '393c8c22-1cfa-4971-b84d-048674b4ccfa' (System.Exception)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.LoadDelayedData(IHvVmCache vmCache, CHvClusterNodesCache clusterNodesCache)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.ResourceScheduler.CHvSnapResDispatcher.CanAcquireResource(CResDispatchIterationContext dispatchContext, CResourceTask task, IResourceRequest resourceRequest, Boolean sessionLogEnabled, IResourceResponse[] acquiredResources)
[11.07.2017 09:48:54] <01> Error    Unable to find Hyper-V hosts where VM '393c8c22-1cfa-4971-b84d-048674b4ccfa' is registered (Veeam.Backup.Common.CAppException)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvResourceDispatcherCache.GetVm(Guid vmId, IHvHost hostOrCluster, CHvDbHost& ownerHost)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.IsNeedReloadDelayedData(IHvVmCache cache, CHvDbHost& currVmHost)
[11.07.2017 09:48:54] <01> Error       at Veeam.Backup.Core.ResourceScheduler.CHvVmSnapshotResDataCommon.LoadDelayedData(IHvVmCache vmCache, CHvClusterNodesCache clusterNodesCache)
[11.07.2017 09:48:54] <01> Info     Task session '1d9063db-7aa2-4379-9041-b0185ca3af8a' has been completed, status: 'Failed', '0' of '0' bytes, '0' of '0' objects, details: ''
[11.07.2017 09:48:55] <01> Info     All VMs have been queued for processing
[11.07.2017 09:49:00] <01> Info     Completing storages in full mode
[11.07.2017 09:49:00] <01> Info     Retrieving space info for repository : Id [00000000-0000-0000-0000-000000000000]
[11.07.2017 09:49:00] <01> Info     [OIS-MH-Veeam1] Identity for impersonation is not specified.
[11.07.2017 09:49:00] <72> Info     Invoker strategy: DefaultStrategy
[11.07.2017 09:49:00] <01> Info     [OIS-MH-Veeam1] Creating File Commander.
[11.07.2017 09:49:00] <01> Info     Physical host volume was not found for path 'D:\VeeamBackups\xxx-CLUSTER-A' on host 'xxx-MH-Veeam1'.
[11.07.2017 09:49:00] <01> Info     [OIS-MH-Veeam1] [FC] Checking whether folder D:\VeeamBackups\xxx-CLUSTER-A exists.
[11.07.2017 09:49:00] <01> Info     [OIS-MH-Veeam1] [FC] Getting disk free space: path: 'D:\VeeamBackups\xxx-CLUSTER-A'

[Dima P.]

Hello Adam,

Please elaborate are you referring to Veeam Agent for Windows installed on guest level or Veeam Backup and Replication installed on host level? Thanks.

[witwicki]

Veeam Backup and Replication installed on host level

[Mike Resseler]

Adam,

Please create a support call and post the case ID here. I am also going to move this topic under Veeam Backup & Replication > Hyper-V as this is about VBR and not about Veeam agent for windows.

After talking and working with our engineers, please post the follow-up here also.

Many thanks
Mike

[witwicki]

Case ID# 02218968

Thanks

[spukljak]

Hi, what was resolution to the problem from Veeam support? We have similar problem, but on retry backup is completed with no error, through at first try, it always fail with same errors as your. Thanks in advance.

[Mike Resseler]

Sebastian,

First: Welcome to the forums

I checked the OP's case but that got closed with no response. I suggest that you also create a case (post the case ID here) and then follow-up after the investigation with the engineers

Thanks
Mike

[KVT]

What was the solution in this case?
Ive got the same problem.

[wishr]

What was the solution in this case?
Ive got the same problem.

Hi KVT,

The original request has been closed due to no response, thus I'll definitely recommend reaching out our support team, especially keeping in mind the root cause may vary from case to case. Please post your case ID (and the solution) here once you get it.

Thanks,
Fedor