New phenomenon. Avast is beating my cpu to death during an acronis backup (which necessarily is copying all files on the drive). Backups normally take 20-30 minutes but now run for 2+ days if I don’t intervene.
This is happening on 2015 version both Pro and Free versions. I have narrowed it to the “file system shield” which, if I turn off, all runs fine. Obviously that is not a solution.
I don’t know if it’s a “new phenomenon”. Avast’s job is to scan files. Period.
When you want to run Acronis, you can pull the ethernet cord, disable Avast shields, do your imaging, validate it, safely remove ext. drive, turn the shields back on, reconnect the internet and you’re good to go. That’s what I’ve been doing for years using ATI v9,10,11.
All this assumes, of course, you’re imaging/backing up a clean system. Copying files is not a time to scan’m. Has to be done before by a Scan or simply realtime protection.
I do a weekly drive image backup on this XP Pro system, at one time I used to run the drive image backup at a time when the computer was on but not very active.
Now I just start it and let it run in the background and I can still continue browsing whilst it is running and no CPU issues. Occasionally just before taking a break I fire up the weekly backup and by the time I come back its done.
I don’t know if this will help you or not, I have my drive images located in one folder and I add that to the Avast > Settings > General > Exclusions - File paths. I don’t exclude the folder but just the drive image file type, e.g. G:\Drive-Images*.v2i - this way you are being more restrictive when using the wildcard *
You could give this a try and see if it helps for you.
Seems extraordinary lengths to go to and there should be absolutely no need to do it.
I have several drives and do backups every night with TrueImage, and Avast never causes any problems - nor should it, as scanning files is everyday routine for Avast. However, I know Avast can get really tied up if presented with very big files (that’s a lot of data to scan!), and TrueImage’s backup files can be huge.
From cursory analysis, my version of TrueImage seems to close and re-open the backup files frequently, which I suspect means that Avast is triggered to rescan the file. If it’s rescanning a 500Gbyte file frequently it’s going to slow things down.
I’d echo DavidR’s advice to try adding an Avast exclusion for the TrueImage backup files either by excluding the specific TrueImage backup folders or excluding the backup files (in my case, *.tib files).
Another point I forgot to mention - I often have to open the .v2i image backup (that can be almost a 6GB compressed .v2i) using the Backup Image Browser. This is almost mounting the image to rummage for a file inside and it is very, very quick.