Product guide

To deploy NetApp 2 X Y scanners, you must configure the NetApp scan thread count for each
scanner as (50 X (Z) threads.
**
** The value must be provided by the filer vendor based on how many outstanding scan
requests the filer’s operating system issues from the discrete filer IP address.
VirusScan Enterprise for Storage can be configured with a maximum of 800 threads. One
scanner can handle scan requests from a maximum of 16 filers.
In the production environment, if 40 or more threads are used consistently, it represents stress.
If the Stats_ICAP.log threads used + Stats_NetApp.log threads used is > = 40 threads
consistently, you can add scanners until relief is observed and the thread count remains below
40.
If only ICAP or NetApp filers are scanned by the scanner, you need to consider only the Stats
_ICAP.log or Stats_NetApp.log respectively.
How do I run an on-demand scan on my filers that are not scanned by VirusScan Enterprise
for Storage on-access scanning?
McAfee recommends using a dedicated node for VirusScan Enterprise on-demand scan tasks. If
you schedule an on-demand scan task on a VirusScan Enterprise for Storage on-access scanner
node, the scanner consumes more resources, which is not recommended.
If a VirusScan Enterprise on-demand scan task requires more time to scan complicated files, it
can lead to resource contention between VirusScan Enterprise and VirusScan Enterprise for
Storage on-access scan. Also, VirusScan Enterprise on-demand tasks do not time out until the
scanning is completed.
You can use the Active Directory logon script batch file to start. This logon script at each boot
establishes drive mappings for the system user that runs an on-demand scan for archive and
large files. The batch file contains:
@echo off
net use w: \\server\sharename1
net use w: \\server\sharename1
net use x: \\server\sharename2
net use y: \\server\sharename3
net use z: \\server\sharename4
Use one command for each map drive, where w, x, y, and z are drive letters and \\server
\sharename1‑4 are filer shares.
The drive mappings are displayed for all user accounts that log on to the node. For user sessions
other than System, the drive mappings are labeled as Disconnected network drive in
explorer.exe. This is because the user session running explorer.exe did not map the drives.
These drive mappings are still accessible to all user sessions with appropriate permissions to the
filer shares.
For more Frequently Asked Questions, see McAfee KnowledgeBase article KB78672.
Frequently asked questions
A
McAfee VirusScan Enterprise for Storage 1.1.0 Product Guide
33