For more information, review the topics in the Index and Table of Contents to the left. If they are hidden, click <--Show Navigation Pane.
Your antivirus configuration can affect file-access performance when using the system. This section describes how to optimize your antivirus setup for use with WAFS/CDP.
Choose from the following antivirus configurations based on your particular needs:
Antivirus at each end-user's workstation - If each of your end-users' workstations are protected, the possibility of an infected file is eliminated and there is no need to run antivirus on the computer running an Agent. This is the most effective level.
Protection at Server - All files move through the Server. You can, therefore, run antivirus software on the Server and scan the Server's root before propagating files to the Agents.
Protection at the server running the Agent - Instead of managing antivirus software on each user's workstation, some IT managers prefer to run antivirus software on the servers that run the Agent. When not done properly, this can affect the performance of user file access. Refer to Recommendations for Directories, Drives, and Processes to Exclude in Your AntiVirus Software below for important exclusion setup notes.
Running antivirus software on an Agent can degrade the performance if not properly configured. The performance hit is caused by the antivirus software thinking that multiple copies of a file are opening. It may scan the same file up to 3 times when a user opens the file once. It may also perform background scans that appear as regular CPU cycles (Norton, E-Trust, NOD32, etc), as well as process scans of the application. If the file is in a linked folder, then the antivirus software scans the file from the original location upon open, AND from inside the replicate drive (e.g., F:\_MySrv\MyVol). Finally, the file is seen internal to the engine (e.g., C:\WINDOWS\AVMF or D:\AVMF), and scanned again.
In addition to on-the-fly scan when a file is changed, some antivirus software includes a daily scan. In this case, if it is necessary to do this daily scan, it might be useful to do it when the Agent is offline. For example, you can schedule the Agent so that it is online 22 hours a day, and offline for two hours during times when users are less likely to use the Agent. During that time, the computer running the Agent can do backups, virus scans, and so on.
Antivirus applications typically allow directories to be excluded from the antivirus scan (often called "exclusions"). When available, you should exclude directories AVM0 and AVMF. All data mirrored on the C drive will be in C:\Windows\AVMF and all data on any other drive will be in <drive_Letter>:\AVMF (e.g., D:\AVMF). Exclude the entire Vault Data drive (e.g., F:\_MyServer). If your antivirus scans processes (especially E Trust, Innoculan, Symantec Tamper Protection, Trend Micro OfficeScan/Server protect), always exclude AvlAgt.exe.
Below is a list of files and locations, and exclusion suggestions for firewalls:
<Drive(s) with AVMF>:\AVMF
<Drive with AVM0>:\AVM0
Availl drive letter
C:\AVCStuff\ACLMgr.exe
C:\AVCStuff\AvlAgt.exe
C:\Program Files\Availl
C:\Program Files\Availl\Availl Server\ASRV.exe
Exclude any ports / additional channels that the Server and Agents use
Exclude the IP address of the Server and Agents from monitoring / stateful packet inspection
Some local server antivirus applications
in corporate environments, like McAfee, are controlled by a central
monitor service run by your IT at headquarters. Exclusions must
be specified at that central console; the console then pushes
them out. The exclude list you see at each remote site is ignored
in these hierarchical topologies. |