replication job remains stuck until I restart veeam services

[frigomiam]

veeam R&B v7
vsphere 5.5

1 replication task for 1 VM is stuck,
it affects running of other jobs,
to fix I have to restart veeam services,

the issue is intermittent ( once a month )

last example :

job is started around 26.12.2014 18:37:29
was still running, and set itself as stopping later on 26th
still stuck on stopping and I restart the veeam service on 29th around 14:51

veeam logs for this VM :

Code: Select all

[26.12.2014 18:37:51] <15> Info     [SnapReplicaVm] '1' restore points found
....
[26.12.2014 18:41:43] <71> Info     [AgentMngr] Checking whether agent '91ad109d-f7d0-4606-ae21-30584c5414f2' is alive on host '....'.
......
last action are :
[26.12.2014 18:43:13] <88> Info     [TransferRetryLogic] Operation started.
[26.12.2014 18:43:13] <88> Info     [TransferRetryLogic] Trying to execute retryable operation.
[26.12.2014 18:43:13] <88> Info     [AP] (2540) command: 'srcReplicateVddkDiskContentIncremental\nvddk:
........
[26.12.2014 23:00:10] <15> Info     Stop signal has been received
[26.12.2014 23:00:10] <15> Info     [Session] Id '8679c6fc-8fe8-4e58-88f0-872a47f1b053', State 'Stopping'
[26.12.2014 23:00:10] <15> Info     Session '8679c6fc-8fe8-4e58-88f0-872a47f1b053', state 'Stopping'
[28.12.2014 23:07:31] <17> Info           [AP] (2540) output: --asyncNtf:--wn:Hot add is not supported for this disk, failing over to network mode...\n
[28.12.2014 23:07:31] <17> Info           [AP] (2540) warning: Hot add is not supported for this disk, failing over to network mode (Hard disk 2)
.......
[28.12.2014 23:07:31] <33> Info           [AP] (918d) output: --asyncNtf:******************* Opening disk using VDDK\n
[28.12.2014 23:07:31] <45> Info           [AP] (9399) output: --asyncNtf:******************* Opening disk using VDDK\n
[29.12.2014 14:51:40] <76> Info           [AP] (b13f) output: --asyncNtf:Received external stop signal.\n
[29.12.2014 14:51:40] <20> Info           [AP] (17f7) output: --asyncNtf:Received external stop signal.\n
[29.12.2014 14:51:40] <44> Info           [AP] (b13f) state: closed
[29.12.2014 14:51:40] <76> Info           [AP] (17f7) state: closed

=> 2 days after the job started, the logs says that hod add is not supported for this disk.
=> no specific logs when the task is stuck.

on ESX vmkernel I don't see any storage related issue,
on same jobs occured in the past with multiple different VMs ( long duration the task is stuck and fails )
it also happened with different proxy VMs.

after restart of veeam services, all start working fine again for the same VMs.

I've checked http://www.veeam.com/kb1054
today I upgraded the VM hardware version to 10. ( but unsure about this resolution as I had same issue with multiple VMs hw version 7 and 8 )

is there any other logs I can check for this type of issue ?
any idea what to check when the issue occurs ?

[veremin]

Have you ever opened a support ticket regarding this behaviour? I'm asking since the team behind this community is not involved in the deep log investigation and cannot assist you effectively with the issue via forum correspondence. Thanks.

[frigomiam]

ok I understand, will do. thanks

[veremin]

Thank you for understanding. We wish you a Happy New Year!

[dellock6]

Just one check, have you installed at least patch2 for VBR 7? This is the minimum version needed to support vSphere 5.5. Probably you already did, but better ask anyway.