We have our backups set to run over CIFS shares that have the vscan disabled. We can backup at faster speed and the filer is still protected. We found it easiest to duplicate all of our root shares in this manner.
 
cifs shares -add <sharename> <path> -novscan or -novscanread
 
 

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Mike Sphar
Sent: Monday, July 26, 2004 11:54 PM
To: ''toasters@mathworks.com' '
Subject: RE: VSCAN and Backsups

I may stand corrected, but I don’t believe the part below is true.  I don’t believe the real-time settings on the Trend server have any bearing on which files are scanned.  From what I see, it appears to me that the Netapp decides whether a file should be scanned or not, and then sends a specific manual “Please scan this file” request to the Trend server.

 

The Netapp is supposed to “cache” which files have been scanned and verified as clean, I believe, so static files shouldn’t be slowing down the backup process once they’ve been scanned the first time, no?

 

--

Mike Sphar - Sr Systems Administrator - Remedy, a BMC Software Company

 

-----Original Message-----
From: Hill, Aaron [mailto:aaron.hill@cba.com.au]
Sent: Monday, July 26, 2004 6:30 PM
To: 'SKIP HOFMANN'; ''toasters@mathworks.com' '
Subject: RE: VSCAN and Backsups

 

 I think you said you were using trendmicro as the scanning server. If you are try setting your realtime scan to "incoming" only. I think this should improve your backup speed somewhat as the backup file read requests will no longer require a VSCAN before the file is handed over to the backup client. The problem here is that you need to be sure that all of the content currently on your filer is virus free. Because from now on, only incoming files will be scanned. Its not ideal. Would be nice if you could exclude your backup client from virus scans during file open requests. I don't know of trendmicro offering this.