Does anyone know what happens with KAV for Exchange when you enable background scanning of information stores?

There is an option to schedule (but only allows once a day) or to re-scan every time AV database is updated.

Ideally we would like to scan before work, at lunch and after work.

We currently have it set to scan at every update but given the fact that our updates run every 20 minutes and the number of new variants around on the internet these days is it ever going to get completely scanned or will it be re-starting every 20 minutes or so.

The issues we have are:

1) It kicks hell out of our disk drives on the server when scanning is enabled - files are on a different disk to the Exchange IS but all part of a RAID array and it is noticeable the difference in file access (also when using tools to show read/write speeds) - is there anything that can be done about this?

2) Is there a way of changing the schedule so we can run 3 times a day?

Thanks

What version of KAV for Exchange do you use?

KAV for Echange 5.5 (5.5.1185.0)

Background scan is on-demand scanning process of all objects in store and it's an additional feature of av protection. On-access av scan is enabled by default. So you don't need to scan all objects after each update.
Background scan uses then protection was temporary disabled or once then you install av software on existent server.

Please find more details in user doc.

You may want to rethink this whole thing.

It makes much more sense to scan e-mail as it comes in through the mail gateway. Since that's the only way viruses can get into the information store, and you're using the same virus deffinitions, if you scan everything coming in you can not possibly have a virus inside the information store.

My solution would be to use a virus scanning gateway and then scan the store once a day at most, late at night when it's not in use. You eliminate all of the issues with slowing down the mail server and the real time protection on both the server and all of your clients is still checking every e-mail each time it's opened.

Thanks for your thoughts, however the reason we want to do a mailbox scan is that a couple of weeks ago we did get a virus through though fortunately the user who received it was alert enough to realise it was something naughty and didn't open it.

We like the mailbox scan because assuming users don't open email as soon as it comes in (some do, but most don't) it gives an extra level of protection in that their mailbox may have been scanned before they get to see the email.

We have also tried the client side scanning, but found this to be extremely slow with 'Attempting to download data from <Exchange Server>' messages appearing all the time.