Error VSSControl: -2147467259 Backup job failed. Error at .Freeze(Boolean createPersistentVssSnapshot, IGuestIndexerHelper helper) at .Freeze(Guid jobId, String jobName, Boolean useVssCopyOnlyOption, Boolean isSnapshotWillBeUsed4Index, String diskSpec)

Error VSS asynchronous operation is not completed. Error Cannot create a shadow copy of the volumes containing writer's data. My recommendation to anyone with the same issue as mine is to create a gpo that restarts both services at least once per day.Ĭode: Select all Error VSSControl: -2147467259 Backup job failed. But there is no solution on Veeam's side because the agent is not causing the problem. A workaround for the problem was to restart the COM+ Event System and Volume Shadow Copy services on the clients as described in the Microsoft Support link. If it doesn't, then it's worth to re-check possible MS recommendations on this matter.Ī system reboot on its own didn't help in the long run in my case, because a couple of clients have to be kept turned on if an employee needs it. Usually, a simple system reboot with initial Windows update installation helps. In our case, we aren't able to get vssadmin output properly even manually outside Veeam Agent. If something goes wrong there, then Veeam Agent won't be able to collect it too. Veeam Agent relies completely on Windows VSS components >. Warning Timed out waiting for GatherWriterMetadata() to complete in GetHostInformation(). Warning Cannot initialize VSS subsystem. Veeam Agent for Windows triggers basically the same mechanisms via a backup: I guess that it's the main root cause which we should fix for now. I tested it on another machine that has not any issues with VAW and got a result immediately.' The shell seems to be stuck and doesn’t return any output. 'I’ve already done the 'vssadmin list writers' command last week without a result.

Timed screenshot windows 10