jduvillard 0 Posted June 13, 2015 Share Posted June 13, 2015 Hello, This is a follow up on this thread: https://forum.eset.com/topic/753-eset-file-security-backup-processes/ Our backup is slowed down to a point where people start arriving in the office before the backup is finished. The only solution I have found to work is by setting: Real-time file system protection > Scan On > File Open to disabled I would rather have exclusions in place, but excluding the Symantec programs path: E:\Program Files\Symantec\Backup Exec\ didn't work Has anyone found a solution for this? Many thanks Jean-Philippe P.S.: Our system is running ERA Agent 6.1.444.0 and File Security 6.0.12035.0 on Windows Server SBS 2008 SP2 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,257 Posted June 13, 2015 Administrators Share Posted June 13, 2015 Please generate a Process monitor log with operations captured during 2-3 minutes of performing a backup. When done, compress the log, upload it to a safe location and pm me the download link. Link to comment Share on other sites More sharing options...
jduvillard 0 Posted June 23, 2015 Author Share Posted June 23, 2015 Update, in case someone has some new ideas: So far I have corrected the exclusions, which were incorrect: from C:\Program Files\Symantec\Backup Exec\ to C:\Program Files\Symantec\Backup Exec\*.* This didn't make any difference I have also tried: C:\Program Files\Symantec\Backup Exec\* Same result I have added all the Backup exe programs manually: C:\Program Files\Symantec\Backup Exec\beremote.exe , C:\Program Files\Symantec\Backup Exec\beserver.exe , etc... This didn't make any difference either The only thing that still makes a difference is by disabling the Scan on File Open Any thoughts? Link to comment Share on other sites More sharing options...
Mitsol 0 Posted June 24, 2015 Share Posted June 24, 2015 Update, in case someone has some new ideas: So far I have corrected the exclusions, which were incorrect: from C:\Program Files\Symantec\Backup Exec\ to C:\Program Files\Symantec\Backup Exec\*.* This didn't make any difference I have also tried: C:\Program Files\Symantec\Backup Exec\* Same result I have added all the Backup exe programs manually: C:\Program Files\Symantec\Backup Exec\beremote.exe , C:\Program Files\Symantec\Backup Exec\beserver.exe , etc... This didn't make any difference either The only thing that still makes a difference is by disabling the Scan on File Open Any thoughts? I'm assuming the slowdown is caused by Eset scanning each and every file that is "opened" by Backup Exec as it is backing them up, which is why excluding the Backup Exec processes/folders isn't making a difference. Weird though as i would have thought Backup Exec was just copying the files, which i wouldn't have thought counted as opening them. Have you tried excluding the backup destination in case it is scanning files as they get created there? Also is it perhaps possible to use Eshell (as someone suggested in the other thread) to somehow disable "Scan on File Open" and then scheduling it to toggle off for the backup? Link to comment Share on other sites More sharing options...
Administrators Solution Marcos 5,257 Posted June 24, 2015 Administrators Solution Share Posted June 24, 2015 Process exclusions will be supported as of EFSW 6.2 that is going to be released later this year. Excluding the backup sw process should solve performance issues with backups. In the mean time, excluding the location where backup is created should work too. Link to comment Share on other sites More sharing options...
jduvillard 0 Posted June 24, 2015 Author Share Posted June 24, 2015 Thank you Marcos and Mitsol for the replies. Our backup is done on tape so I have now disabled the option "Real Time FS protection>Media to Scan>Removable media". I will keep you posted, whether this works or not. JP Link to comment Share on other sites More sharing options...
jduvillard 0 Posted July 5, 2015 Author Share Posted July 5, 2015 Quick update. Nothing has so far worked apart from disabling File Open. So I will wait for EFSW 6.2 to be released. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,257 Posted July 7, 2015 Administrators Share Posted July 7, 2015 I could check a Process Monitor log as well as your ESET's configuration and logs (collected as per the instructions at hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3466). If you decide troubleshoot the issue and create the logs, upload them to a safe location and pm me the download link. Link to comment Share on other sites More sharing options...
Recommended Posts