Somehow, when playing with 9.5U4 and repo configuration on a test box, I managed to break the whole backup job by setting
"Limit maximum concurrent tasks" for the backup repository to a number
lower than the number of VMs that are being processed in a backup job that is using that repository, while that job had
"Allow processing of multiple VMs with a single volume snapshot" enabled.
This reliably causes the backup job to fail. Say, you have concurrent tasks set to 2 and there are 3 VMs included in the job. The backup for the first two VMs fails like this:
Code: Select all
Failed to finalize guest processing. Error: Failed to call RPC function 'Vss.WaitForBackupDocsToBeFlushed': The remote procedure call was cancelled. RPC function call failed. Function name: [DoRpc].
After two first 2 VMs failed, the backup continues with the third machine, and there the job just hangs indefinitely, doing nothing, job cannot be stopped either, the Veeam Backup Service fails to stop as well and needs to be killed via task manager. The checkpoint for the third VM if left behind and needs to be merged manually via PS - "Get-VMSnapshot <VM> | Remove-VMSnapshot"
The issue immediately goes away when "Allow processing of multiple VMs with a single volume snapshot" in unchecked from the job, the VMs get processed in batches corresponding to the concurrent tasks limit and everything finishes just fine.
Somehow I'd say users should be prevented from creating invalid configuration that completely breaks the backup.

Someone else able to reproduce this?
