A Veeam Backup may fail with the below error:
04/12/2018 18:27:54 :: Processing <Server_Name> Error: Cannot start service. Machine: [<Server_Name>]. Service: [VeeamVssSupport]. Cannot start service. Win32 error:The service did not respond to the start or control request in a timely fashion. Code: 1053
This is by design as Sophos Lockdown blocks actions performed by Veeam unless explicitly allowed.
The following sections are covered:
Applies to the following Sophos products and versions Central Server Lockdown 7.1.1
Veeam has published an article containing various antivirus exclusions to help prevent antivirus software from interrupting Veeam Backup & Replication communications.
The next backup should be successful.
Note: This KBA is only applicable if a Veeam Backup is failing due to Sophos Lockdown. If the backup is failing on an Unlocked server, contact Sophos Support.
If you've spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article. This is invaluable to us to ensure that we continually strive to give our customers the best information possible.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.