jackouille Posted September 27, 2017 Report Share Posted September 27, 2017 I have installed one week ago Immunet (6.0.4) on a Veeam Server running on Windows 2008R2 (in addition with AVAST). Since then CPU usage was increasing and I received some connection failure) and backups were always lasting longer. I was obliged to remove Immunet despite I added an exclusing for all files from Veeam. Link to comment Share on other sites More sharing options...
jackouille Posted September 27, 2017 Author Report Share Posted September 27, 2017 Last Incremental backup from yesterday was lasting 42 minutes, today within the same job it took only 2 minutes. Link to comment Share on other sites More sharing options...
ritchie58 Posted September 27, 2017 Report Share Posted September 27, 2017 Did you create an Exclusion rule for Avast!'s Program Files folder with Immunet and create a similar exclusion/exception/allow rule for Immunet's Program Files folder with Avast! as well? Doing so can really eliminate a lot of possible conflicts. Please note: Immunet is not free for any "for profit" endeavor. If you're not a multiple-endpoint non-profit charitable, educational organization or do not have your own private intranet no more support will be forth coming. This info is in the EULA when you first installed Immunet. Regards, Ritchie... Link to comment Share on other sites More sharing options...
jackouille Posted September 27, 2017 Author Report Share Posted September 27, 2017 Yes the Exclusion rule for Avast was already present. Not in the beginning but yesterday I add the Exclusion in order to see if could improve performance but this morning I receive more backups warning so I was obliged to remove it. Because it's a dedicated server for Backups, risks for contamination is very low (but of course not null). Link to comment Share on other sites More sharing options...
ritchie58 Posted September 27, 2017 Report Share Posted September 27, 2017 It sounds like you may have to exclude additional file paths associated with your backup program with Immunet. That's something you could look into. Link to comment Share on other sites More sharing options...
ritchie58 Posted September 27, 2017 Report Share Posted September 27, 2017 Yeah, Immunet will scan files as they are being created so I could see where that could cause the increased CPU/system resources being used. Link to comment Share on other sites More sharing options...
jackouille Posted September 27, 2017 Author Report Share Posted September 27, 2017 I also reinstall Immunet and add the following folders in my Exclusing list: - Veeam Programm - Full disk used for backups I restart the backup from 8:00 and now it took 8 minutes (instead of 2) but better as 42 minutes wihtout defining the backup folder within Exclusion list. Link to comment Share on other sites More sharing options...
ritchie58 Posted September 27, 2017 Report Share Posted September 27, 2017 That does sound better to me too. Adding the Program Files folder for Veeam as an Exclusion was a great idea jackouille! Link to comment Share on other sites More sharing options...
jackouille Posted September 27, 2017 Author Report Share Posted September 27, 2017 You are right, I either add the folder within ProgramData\Veeam and now it worked again in 2 minutes. I also remove Veeam Program from Exlusion and now only the the remaining entries: - Backup folder (where all backups are stored) - ProgramData\Veam This could be helpfull for other Immunet/Veeam users. Thanks Ritchie for your great help solving that issue. Greatings from Switzerland Link to comment Share on other sites More sharing options...
ritchie58 Posted September 27, 2017 Report Share Posted September 27, 2017 Your welcome jackouille, always glad to help out when I can. Cheers, Ritchie... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.