Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 5 replies
  • Subscribers 13 subscribers
  • Views 2690 views
  • Users 0 members are here
Options
Suggested

Sophos blocking Veeam Agent on Windows 11

Tony Graham

I have a problem with Veeam backup agent with Sophos Endpoint Agent installed

If I uninstall Sophos Endpoint I am able to backup the PC. If Sophos is installed it is blocked.

I assume this is a matter of somehow unblocking the app or opening some ports but as I am a newcomer to Sophos Endpoint it is not clear to me how to accomplish this.

Interestingly I have another machine that I am backing up without issue. There is nothing in any logs Sophos Central or local Windows logs referencing the failing backup.

Thanks for any assistance.



Edit tags
[edited by: GlennSen at 1:23 PM (GMT -7) on 3 Oct 2024]
Parents
  • +1

      Well, I thought I would share this with the community as it's an odd one but these are the observations I had during this issue. I will start at the beginning. After a Veeam upgrade from 12.0 to 12.2 all communication with the remote agent in question stopped. I added the affected machine to a new Sophos Policy such that the Windows Firewall would be set to Allow All. This allowed Veeam to communicate and backup with the agent. When I went to investigate the solution of adding a process exclusion, the first thing I did was set the policy I created for that machine to 'Bypassed'. I then waited a day and let the overnight backup run again (I wanted to ensure the problem still existed). To my surprise, it worked. So I manually checked communication with the agent and I can still connect. So, with no other changes it has apparently repaired whatever was wrong when communication was first re-established. Perhaps an agent update was waiting that could not be applied while the firewall was enabled. I have since removed the machine from the special policy I created and deleted that policy.

Reply
  • +1

      Well, I thought I would share this with the community as it's an odd one but these are the observations I had during this issue. I will start at the beginning. After a Veeam upgrade from 12.0 to 12.2 all communication with the remote agent in question stopped. I added the affected machine to a new Sophos Policy such that the Windows Firewall would be set to Allow All. This allowed Veeam to communicate and backup with the agent. When I went to investigate the solution of adding a process exclusion, the first thing I did was set the policy I created for that machine to 'Bypassed'. I then waited a day and let the overnight backup run again (I wanted to ensure the problem still existed). To my surprise, it worked. So I manually checked communication with the agent and I can still connect. So, with no other changes it has apparently repaired whatever was wrong when communication was first re-established. Perhaps an agent update was waiting that could not be applied while the firewall was enabled. I have since removed the machine from the special policy I created and deleted that policy.

Children
Unfiltered HTML