This content has been marked as final. Show 7 replies
If you add the actual Backup Exec process name into the On Access Low Risk Policy excusion list that should do trick.
thx, but which process of Backup Exec 12.0?
knows someone the name of this process?
The next time you perform a backup on the server, go to the machine, log in and see what windows process is taking up all the resources.
If I remember right (we last used Backup Exec in the v7 days) it was something like bkupexec or something like that.
It seems to be:
Should I exclude on read or write?
I would exclude both of them on reads only (as they are only backing up the server, not writing to them). You should see some improvement next time you run a backup job.
Anyone know if not excluding on writes means it will try and scan the tape I/O Writes ? I think it still impacts performance and we've excluded both.
ALso you may need to exclude the backup software catalogue/database files/folders from general read/write scanning as well or they may become your bottlnecks.
Yes it normal to exclude the BackUpExec folders and databases from being scanned, also helpful to do the same for Exchange folders, McAfee used to tie Exchange servers in knots due to persistent scanning.