Rtvscan.exe takes about 8 hours to complete a scheduled scan
Updated: 22 May 2010 | 8 comments
we have one client server where the scan is taking about 8 hours to complete and during that time uses all of the CPU...I am not too concerned with the amount of CPU being used I understand it takes what it can, but why does the scan take so long. I just deleted 8 GB of data yesterday thinking that would speed it up and it is still taking a long to complete.
Any thoughts?
discussion Filed Under:
Comments
Some info ..
What is the
Thanks :)
Kedar Mohile http://kedarmohile.blogspot.com
try to visit this site hope
try to visit this site hope it will help you
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/ec1422e07c11c714882574b0005ade87?OpenDocument
:-)
Total Used Space is 26.8
Total Used Space is 26.8 GB of 37.2 GB, but what is also weird is the scan log says it scanned over 5 million files, but I don't have 5 million files on the server unless it counts other things as files.
the system is Windows 2003 Standard, with 1.8 GHz CPU and 1 GB RAM
Do you have a lot of
Do you have a lot of compressed files on the machine? ISO'S? Zips? Also are you scanning network/mapped drives? If so, these things can cause long scan times.
I m also facing same problem.
I m also facing same problem. cpu core2duo 1gb ram.8 gb data and takes 4 to 5 hours to scan
i m using sep 11 mr4
i m using sep 11 mr4
Not too many compressed
Not too many compressed files...there are about 70 zip/compressed files and no ISOs. Also no network drives are mapped...I guess symantec counts up the files inside the zip and when I counted the files, I only counted the one file, but I can't imagine there are 5 million files in the the 70 zip files. Does symantc log detail of the scan as to what files are being scanned?
Also another note...I see a
Also another note...I see a bunch of these warnings in the event logs and I wondering if this could one of the reasons the scan could be taking a long time,
Could not scan 221 files inside C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps\public\WEB-INF\patches\4-0-499\agentPatch.jar due to extraction errors encountered by the Decomposer Engines.
We have a lot .jar files on the server and they are some kind of compressed file so if this the case we have more the 70 compressed files, but I am wondering if it is also able to get into some of the .jar files and this is why it is scanning so many files...
I will try one night without scanning the compressed files and see if the number goes down.
Would you like to reply?
Login or Register to post your comment.