Dell PowerStore 1200T Using the Common Event Enabler 8.x on Windows Platforms - Page 41

Steps 1. Enable the third-party realtime scanning feature from the AV machine. The third-party application documentation provides more information. 2. Start the EMC CAVA service. Start, stop, and restart CAVA provides more information. 3. Include the AV machines from the list of servers providing virus-checking capability to VNX or Unity. Define AV machine IP addresses in viruschecker.conf provides more information. Instructions for retrieving the configuration file on Unity systems are described in Virus-checking continuation. Manage CAVA thread usage CAVA uses four types of threads to handle virus checking: ● Normal Data Mover or storage processor (SP) CIFS threads - Serve CIFS requests from any CIFS client. ● Reserved Data Mover or SP CIFS threads - Serve CIFS requests from the external AV machines only. ● Data Mover viruschk threads - (VNX systems only) Issue antivirus check requests to CAVA threads on the external AV machines. ● CAVA threads on each external antivirus (AV) machine - (VNX systems only) Service the requests issued by viruschk threads on the Data Movers. By default, 20 threads run on each external AV machine. The default number of CIFS threads that run on a Data Mover or SP depends on Data Mover or SP memory. By default, three CIFS threads are reserved for AV activities (these are the reserved Data Mover or SP CIFS threads). For VNX systems, each Data Mover runs 10 viruschk threads by default. In general, you should set the number of reserved threads for the VC client equal to the number of AV checking machines. However, this number should not be set higher than half the number of CIFS threads. ● Adjust the maxVCThreads parameter provides information on setting the maxVCThreads parameter for VNX systems. Managing a Multiprotocol Environment on VNX provides more information on setting the number of normal CIFS threads on a Data Mover. ● For Unity systems, use the svc_nas command to modify the maxVCThreads parameter, and then reboot the SPs. Unity Service Commands Technical Notes provides more information on the svc_nas command. For VNX systems, you can set the number of viruschk threads by using the server_setup command. VNX Command Line Interface Reference for File describes how to set viruschk threads by using server_setup. Managing the Registry and AV Drivers describes how to change the default number of CAVA threads. If virus checking is enabled, a file usually must be scanned for viruses before the file can be accessed. Occasionally, if the VC client runs out of threads, file access requests cannot progress because VC threads are not available for virus scanning. In effect, a deadlock occurs between file access requests and virus-checking requests. For these situations, the VC client has special threads reserved for breaking deadlocks. The maxVCThreads parameter specifies the number of special threads reserved for the VC client. Generally, the default setting for maxVCThreads is appropriate for most networks. However, you can modify this value if necessary: ● For VNX systems, modify the maxVCThreads parameter in the /nas/site/slot_param, or the /nas/server/ slot_/param files. ● For Unity systems, use the svc_nas command to modify the maxVCThreads parameter, and then reboot the SPs. Adjust the maxVCThreads parameter About this task NOTE: For Unity systems, use the svc_nas command to modify the maxVCThreads parameter, and then reboot the SPs. Unity Service Commands Technical Notes provides more information on the svc_nas command. For VNX systems only, use the following procedure to adjust the maximum number of threads reserved for breaking deadlocks: NOTE: Do not change other lines in the parameter file without a thorough knowledge of the potential effects on the system. Contact Customer Support for more information. Managing CAVA 41