Enable debug logging.  There are two ways to do that, either from the Data Mover or from the scan engine.  Ideally, you want to watch the interaction between the Data Mover and the scan engine while it is taking place.  This KB article discusses the steps here in detail, and also discusses how to enable debug logging on the scan engine which I won't go into here, but to enable it on the Data Mover, enter the following:  $ server_param server_X -f viruschk -m Traces -v 0xC0000004  Once debug logging is enabled, all interactions between the Data Mover and the scan engines will be logged to the server log.  To watch it in real time, enter the following:  $ server_log server_X -s -f &  Notice that I sent the command to the background so that you can continue to work.  You could also add something to stream it to a log instead of the screen, like this:  $ server_log server_X -s -f > slog2.out &  To kill the log streaming, enter:  $ kill -9 %1  To disable verbose logging, enter the following:  $ server_param server_X -f viruschk -m Traces -v 0
I frequently receive low water mark and high water mark error messages from our datamovers.  Mar 21 07:39:22 2014 DART:VC:ERROR:2 Slot 2: 1395409154: Vnode  high water mark reached.  Is there a way to observe the file scanning activity in real-time or view historical statistics? I'd like to use this information to establish a more accurate AV exclusion file for the datamovers. Thanks!  Environment Overview masks=*.* excl=*.ldb:*.mad:*.maf:*.mam:*.maq:*.mar:*.mat:*.mda:*.mdb:*.mde:*.mdn:*.mdw:*.mdz excl=*.inp:*.orc:*.sc:*.sqc:*.sql:*.sqr excl=*.edb:*.ost:*.pst:*.stm excl=*.db:*.dbf:*.gdb:*.fmt:*.fmb:*.fmx:*.frm:*.ora excl=*.bz:*.gz:*.rar:*.tgz:*.tar:*.zip:*.Z excl=*.adl:*.gdbtable:*.gdbindexes:*.gdbtablx:*.lock:*.prj:*.sbn:*.sbx:*.shp:*.shx excl=*.index:*.db-journal:*.log:*.nsf:*.tmp:*.vmdk:>>>>>>>>:~$*.*:*.dbx-journal
Celerra AV File Scanning Visibility?