Recently, we migrated our physical servers to virtual hosts. That prompted us to upgrade the backup procedures to match best practices for virtual systems. We also needed to create an offsite, cloud based data repository.

**I originally posted this in the Sophos forums but I'm feeling this community may be a better fit for the topic.**

Hello all,

I had a 2 hour consult with Sophos last Thursday where we installed the Enterprise Console 4 and started progressing towards migrating to the endpoint security suite. Ever since that day when Backup Exec (v 10d/10.1 rev 5629) runs the server crashes, the locked windows disappears and I can do nothing. I had made no other changes to the server that day.

I've got nothing in Quarrantine on the server and on the backup The Sophos program folder and the sec_40 and sec31 folders are excluded from the backup. Does anyone have a clue as to why Sophos would crash my server? Are there folders I need to not backup? Thanks in advance for the help.

The only thing I can think of... is that it's a simple race-condition. Backup Exec has a long history (at least for me) of conflicting with anti-virus software. The only thing I can suggest... is to stop the AV while the backup is running... then resume when finished. This probably isn't the most ideal solution... but should work.

3 Replies

The only thing I can think of... is that it's a simple race-condition. Backup Exec has a long history (at least for me) of conflicting with anti-virus software. The only thing I can suggest... is to stop the AV while the backup is running... then resume when finished. This probably isn't the most ideal solution... but should work.

On a side note... depending on how the scheduler works... (I will try & double-check this later)... you might be able to make the scheduled task stop the av... backup... then restart the av after it's finished...

i.e. a batch file with:

net stop "Sophos Antivirus"

backupexec.exe /someswitches backupjob

net start "Sophos Antivirus"

Despite how much I love how well Sophos works... sometimes it's a bit too aggressive with file locking. The flip side to that coin... is that it will stop a virus from running before windows has a chance to do something stupid with it.

I ran into a similar circumstance when installing SP3 on XP. We have MS Games blocked... and SP3 tries to re-install the MS Games with SP3... (no clue why...) The end result was that Sophos was preventing SP3 from writing "sol.exe" and others... so SP3 would fail & roll back.

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.