Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 10 subscribers
  • Views 18615 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

problems with Veeam Backup after Sophos Server Protection installed?

Alphatec

Hi there,

after installing Sophos Server Protection on a Server (Win2012R2 VM on ESXi 6.0) with activated lockdown. In the nigt the Server can't get backuped with Veeam. All other Server's without Sophos Server Protection had no problem to be backed up.

 

Veeam Log:

Failed to prepare guest for hot backup. Error: Unable to register and start service. Attempt 10 of 10 Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [RDP.FIRMA-gmbh.local]. Service name: [VeeamVssSupport]. Service binary path: [C:\Windows\VeeamVssSupport\VeeamGuestHelper.exe]. Service account: []. Cannot create service. Win32 error:Der angegebene Dienst wurde zum Löschen markiert. Code: 1072
Error: Failed to prepare VM for processing: Unable to register and start service. Attempt 10 of 10 Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [RDP.FIRMA-gmbh.local]. Service name: [VeeamVssSupport]. Service binary path: [C:\Windows\VeeamVssSupport\VeeamGuestHelper.exe]. Service account: []. Cannot create service. Win32 error:Der angegebene Dienst wurde zum Löschen markiert. Code: 1072

 

Thanks for help :)



This thread was automatically locked due to age.
Parents
  • +1

    Hello,

    We are aware of an issue that can affect backups when running the Sophos Central endpoint and server agents on certain Windows operating systems. The issue affects the Volume Shadow Copy Service (VSS) within Windows and therefore may be experienced, intermittently, when using the built-in Windows backup tool or third-party backup software.
     
    Following investigations, working with Microsoft and third-party backup vendors, we have established that the way in which the Sophos Health Service (part of the Sophos agent) writes to the Windows registry as part of a transaction, has uncovered a behaviour that can, intermittently, result in a backup failure.
     
    Microsoft has confirmed that the Sophos product is using their APIs correctly (it is therefore possible that other non-Sophos products could also fall foul of this behaviour), and they are expecting to release a fix into their RS5 builds imminently, and back-port the fix to Windows Server 2016. 

    Sophos have also created a configuration that will fix this; this is currently being tested and should be released to all customers in the next 4-6 weeks. 
     
    You can confirm if this is the issue you are experiencing by disabling the Sophos Health Service prior to the backup being run.

    Regards,

    Stephen 

  • 0 in reply to StephenMcKay

    Hi Stephen,

     

    thanks for the usefull and fast answer. So the fix that will come in 4 - 6 weeks will be automaticly rolled out or what must I do?

     

    Thanks

     

  • 0 in reply to Alphatec

    Hi,

    The fix will be part of a release that we will roll out automatically, but the application of the fix needs to be done manually. There will be a KBA at release with details of how to apply the fix for this issue.

    Regards,

    Stephen

Reply Children
Unfiltered HTML